Installation guide

Templates Overview

EZ Template Lifecycle

An EZ template has the following development stages:

1 Any EZ template should be first installed on the Hardware Node. The vzpkg install

template command enables you to install OS and application EZ templates on the Node.

2 The EZ template should be cached by using the vzpkg create cache command. This step

is required for OS EZ templates only. As a result of the vzpkg create cache execution, the

necessary packages included in the OS EZ template are downloaded from the network

repository, installed in the /vz/template/<os_name>/<os_version> directory on the

Hardware Node, and a gzipped tarball for the OS EZ template is created and put to the

/vz/template/cache directory.

3 Either a new Container is created on the basis of the cached OS EZ template with the vzctl

create command or an application EZ template is added to any number of Containers by

using the vzpkg install command. In the latter case, the necessary application files are first

downloaded from the network repository and installed on the Hardware Node and then the

VZFS links to the installed files are created and added to the Container private area.

4 An obsolete EZ template applied to the corresponding Container can be updated by using the

vzpkg update command.

5 Any EZ template excluding OS EZ templates can be removed from the Container with the

vzpkg remove command.

6 An EZ template that is not used by any Container may be completely removed from the

Hardware Node with the vzpkg remove template command.

All these steps can be performed either through the Parallels Virtuozzo Containers command-line

utilities indicated above, with the help of Parallels Virtual Automation, or using Parallels

Management Console.