The vzup2date utility allows you to specify what particular Virtuozzo updates should be searched for on the update server, download the found updates, and install them on the Hardware Node. This can be done by using special update filters or by explicitly specifying the update IDs. You can also combine both methods to get the right updates for your Virtuozzo Containers installation.
The filters that can be used with vzup2date can be divided in two groups:
Name |
Description |
|
Selects the latest major update for your current Virtuozzo Containers installation. For example, with the current Virtuozzo version of 4.0, this will be the latest major update for Virtuozzo 3.0, 2.6.2, 2.6.1, and earlier Virtuozzo releases. To see what latest update is available, you can use the Bear in mind that the major Virtuozzo release you are updating to might also already have available minor updates (i.e. updates for the Virtuozzo core and tools). However, they will not be applied during the major Virtuozzo update. So, in order to install the latest Virtuozzo version and then to apply minor updates for it, you will need to launch the utility twice. |
|
Selects updates available for your current Virtuozzo core. While working with the Virtuozzo core updates, please keep in mind the following:
|
|
Selects updates available for your current Virtuozzo utilities. While working with the Virtuozzo tools updates, please keep in mind the following:
|
Name |
Description |
|
Selects updates for all OS templates installed on the Hardware Node. |
|
Selects all OS templates available on the Virtuozzo update server. |
|
Selects updates for all application templates included in the OS template(s) specified. |
|
Selects updates for all application templates on the Hardware Node. |
|
Selects all application templates available on the update server for the OS template(s) specified. |
|
Selects all application templates for all OS templates installed on the Hardware Node. |
|
Selects updates for all OS and application templates installed on the Hardware Node. |
OS_list denotes a list of OS templates for which the application templates are to be updated. You can specify several OS templates and separate them by commas. You can enter the OS template name in one of the following forms:
redhat-el5-x86). In this case application templates for the latest version of the OS template will be taken into account. For example, you can issue the following command to list:fedora-core-8-x86 OS EZ template:# vzup2date -z -m batch list --all-app-for=fedora-core-8-x86-ez
Getting templates information. Please wait...done
The following application templates were selected:
For fedora-core-8-x86-ez
[asterisk-fedora-core-8-x86-ez/4.0.0] Asterisk...
[devel-fedora-core-8-x86-ez/4.0.0] Devel...
[jre-fedora-core-8-x86-ez/4.0.0] Jre...
[jsdk-fedora-core-8-x86-ez/4.0.0] Jsdk...
...
redhat-9 OS standard template:# vzup2date -t -m batch list --all-app-for=redhat-9
Getting templates information. Please, wait...done
The following application templates were selected:
For redhat-9/20060116
[ColdFusion-rh9/20060119] Macromedia ColdFusion MX Ser...
[EveryAuction-rh9/20060121] EveryAuction - the Freewar...
[HelixServer-rh9/20060127] Helix from RealNetworks is ...
[PostNuke-rh9/20060325] PostNuke is an open source, op...
[analog-rh9/20060115] Web statistic analyzer p5
[autoresponder-majordomo-rh9/20061120] Autoresponder/m...
...
redhat-9/20060411). In this case application templates for the OS template version specified will be taken into account. For example:Note: Since OS EZ templates do not have versions, this operation can be performed in respect of standard OS templates only.
# vzup2date -t -m batch list --all-app-for=redhat-9/20060411
Getting templates information. Please, wait...done
The following application templates were selected:
For redhat-9/20060411
[ColdFusion-rh9/20060119] Macromedia ColdFusion MX Ser...
[EveryAuction-rh9/20060123] EveryAuction - the Freewar...
[HelixServer-rh9/20060207] Helix from RealNetworks is ...
[PostNuke-rh9/20060323] PostNuke is an open source, op...
...
You can also use the so-called update IDs to choose particular Virtuozzo template updates to be checked and, if necessary, downloaded from the update server and installed on the Hardware Node. An update ID can be specified in one of the following ways:
redhat-9). In this case the latest update for the corresponding OS template will be checked for and, if necessary, downloaded and installed on the Node. For example, the following command will update:redhat-9 OS standard template to the latest version:# vzup2date -t -m batch install redhat-9
fedora-core-8-x86 OS EZ template to the latest version:# vzup2date -z -m batch install fedora-core-8-x86-ez
PostNuke@redhat-9). In this case the application template available for the latest version of the OS template specified will be checked for and, if necessary, downloaded and installed on the Node. For example, to install the PostNuke application template shipped with the latest version of the redhat-9 OS template, you can execute the following command:Note: This operation has no effect in respect of application EZ templates since all application EZ templates do already incorporates the names of the corresponding OS templates (e.g. mysql-centos-5-x86-ez or asterisk-fedora-core-8-x86-ez).
# vzup2date -t -m batch install PostNuke@redhat-9
PostNuke@redhat-9/20060116). In this case the application template for the OS template version specified will be checked for and, if necessary, downloaded and installed on the Node. For example, to download and install the PostNuke application template for the redhat-9 OS template having the version of 20060116, you can issue the following command:# vzup2date -t -m batch install PostNuke@redhat-9/20060116
Note: Since OS EZ templates do not have versions and all application EZ templates already incorporate the names of the corresponding OS templates, you can specify such update IDs to update standard OS templates only.