14.3. Managing OS Templates in Physical Server Context

Virtuozzo Automator allows you to list OS templates installed on a particular physical server. They may be already used or not used by certain virtual environments. All OS templates installed on the physical server are listed on the Container Software > OS Templates page of any physical server in the following table:

Column Description
Name The name of the OS template.
Type Denotes if it is an EZ Virtuozzo template. EZ templates have only information about the necessary packages, and the packages themselves are downloaded from a central repository. EZ templates don’t have versions.
Description The description of the OS template.
OS Denotes the operating system the template is intended for.
Architecture The microprocessor architecture.
Cached If the value is “No”, this means that to base virtual environments on this template you need to cache it first.

To show or hide columns, click Select Columns and set or clear the respective checkboxes.

By default, 20 templates are displayed on a page. To change the number of templates shown per page, click the appropriate link below the table. You can also filter the templates shown in the Templates table. To do that, click Show Search, enter search patterns in the search fields, and click Search. To change what search fields are displayed, click Customize. To view all OS templates installed on the physical server, click Reset Results.

With the help of the toolbar located above the table you can perform the following operations on OS templates:

  • install an OS template present as a file on the local computer to physical servers registered in Virtuozzo Automator by clicking New App/OS Template;

  • install an OS template present on this physical server to other physical servers registered in Virtuozzo Automator by clicking Install to HNs;

  • prepare an OS template for creating virtual environments on its basis by selecting it and clicking Cache;

  • delete those OS templates that are not needed any more from the physical server. To do this, select the check boxes opposite the OS templates you wish to delete and click Uninstall.

    Note

    If any virtual environment on the physical server is based on the OS template you wish to delete, the OS template deletion will fail.

  • update an OS template with new packages from the update repository by selecting it and clicking Update.

Clicking an OS template name opens the screen where you can cache the template packages and view detailed information on them.

14.3.1. Viewing OS Template Properties in Physical Server Context

The description of the selected OS template is given at the top of the page, after which the Summary section provides additional details on the template:

Field Description
Type Denotes if it is an EZ Virtuozzo template. EZ templates have only information about the necessary packages, and the packages themselves are downloaded from a central repository. EZ templates don’t have versions.
Cached If the template is cached on a particular physical server, new virtual environments can be created on its basis on this physical server.
Architecture The microprocessor architecture.
Platform Denotes the operating system the template is intended for.
Supported technologies Lists the technologies that the physical server must support for the template to work correctly.

The Added to Containers table at the bottom of the page enumerates those virtual environments that were created on the basis of the current OS template.

If you are going to cache the template, remember that, first, packages “included” in an EZ template are, actually, meta data pointing to what real packages and from what repository can be downloaded to the physical server to make the template work. Second, to be used for creating virtual environments on its basis, any OS template has to be cached. Caching an OS template is preparing it for creating virtual environments on its basis. When you cache an OS template, you:

  1. Download the packages its meta data refer to from the download repository to your physical server.
  2. Install them on the physical server.
  3. Compress them into a gzipped archive for further usage.

If the template has already been cached, clicking the Cache icon launches updating the cached templates.

If, before doing anything, you want to see what packages the OS template includes, open the Included Packages tab.