Parallels Virtuozzo Containers 4.7 for Linux Templates Management Guide Copyright © 1999-2012 Parallels IP Holdings GmbH and its affiliates. All rights reserved.
Parallels IP Holdings GmbH. Vordergasse 59 CH8200 Schaffhausen Switzerland Tel: + 41 526320 411 Fax: + 41 52672 2010 www.parallels.com Copyright © 1999-2012 Parallels IP Holdings GmbH and its affiliates. All rights reserved. This product is protected by United States and international copyright laws. The product’s underlying technology, patents, and trademarks are listed at http://www.parallels.com/trademarks.
Contents Introduction ............................................................................................................... 5 About Parallels Virtuozzo Containers 4.7 .......................................................................... 6 About This Guide ............................................................................................................ 7 Organization of This Guide .......................................................................................................
Contents Preparing OS EZ Templates for Creating Containers ...................................................... 43 Installing Application EZ Templates ................................................................................ 44 Downloading and Installing EZ Templates with vzup2date .............................................. 44 Uploading and Installing EZ Templates in Parallels Management Console ....................... 48 Listing EZ Templates ...................................................
CHAPTER 1 Introduction This chapter provides basic information about Parallels Virtuozzo Containers 4.7 and this guide. In This Chapter About Parallels Virtuozzo Containers 4.7 ................................................................. 6 About This Guide ................................................................................................... 7 Getting Help ........................................................................................................... 9 Feedback ..............
Introduction About Parallels Virtuozzo Containers 4.7 Parallels Virtuozzo Containers 4.7 is a patented OS virtualization solution. It creates isolated partitions or Containers on a single physical server and OS instance to utilize hardware, software, data center and management effort with maximum efficiency. The basic Parallels Virtuozzo Containers capabilities are: • Intelligent Partitioning—Division of a server into as many as hundreds of Containers with full server functionality.
Introduction The Parallels Virtuozzo Containers OS virtualization model is streamlined for the best performance, management, and efficiency. At the base resides a standard Host operating system which can be either Windows or Linux. Next is the virtualization layer with a proprietary file system and a kernel service abstraction layer that ensure the isolation and security of resources between different Containers. The virtualization layer makes each Container appear as a standalone server.
Introduction Documentation Conventions Before you start using this guide, it is important to understand the documentation conventions used in it. The table below presents the existing formatting conventions. Formatting convention Special Bold Type of Information Example Items you must select, such as Go to the Resources tab. menu options, command buttons, or items in a list. Titles of chapters, sections, and subsections. Read the Basic Administration chapter.
Introduction Getting Help In addition to this guide, there are a number of other resources available for Parallels Virtuozzo Containers which can help you use the product more effectively. These resources include: • Parallels Virtuozzo Containers 4.7 Installation Guide. This guide provides detailed information on installing Parallels Virtuozzo Containers on your server, including the pre-requisites and the stages you shall pass. • Getting Started With Parallels Virtuozzo Containers 4.7.
CHAPTER 2 Templates Overview This chapter outlines the basics of EZ templates. In This Chapter Parallels Virtuozzo Containers Templates Overview ................................................. 11 EZ Templates Overview .......................................................................................... 12 EZ Templates Basics .............................................................................................. 13 EZ Template Directory Structure ..............................................
Templates Overview Parallels Virtuozzo Containers Templates Overview A template in Parallels Virtuozzo Containers is a set of application files and registry settings installed on the Host operating system in such a way as to be usable by any Container by mounting over Virtuozzo File System. The Parallels Virtuozzo Containers software provides tools for creating templates, installing and removing them on/from the Hardware Node, adding them to a Container, and so on.
Templates Overview EZ Templates Overview EZ templates are part and parcel of the Parallels Virtuozzo Containers philosophy because they provide a way of sharing resources among lots of Containers, thus enabling huge savings in terms of disk space and memory. For example, when you install and cache an OS template on the Hardware Node, Parallels Virtuozzo Containers creates the /vz/template/ directory containing all the OS files that can be shared among Containers.
Templates Overview EZ Templates Basics All OS and application EZ templates are defined by the following features: • EZ templates do not carry any package files. They contain only information about what packages to install on the Hardware Node to make the templates fully operational and from what network repository to download these packages.
Templates Overview Non-base OS EZ template sets should have their own names and are created by appending a random identifier to the base OS EZ template name. For example, if you wish your Container to run Red Hat Enterprise Linux 5 and to function as a Linux-based server only, you can create the redhat-el5-x86-server OS EZ template set and include only those packages in it that are needed for performing main server tasks.
Templates Overview EZ Template Directory Structure All EZ templates and the software packages included in them and installed on the Hardware Node are located in the so-called template area the path to which is set as the value of the TEMPLATE variable in the /etc/vz/vz.conf file. By default, the /vz/template directory is used.
Templates Overview • is the package name • denotes the package epoch • indicates the package version • is the package release • denotes the microprocessor architecture where the package is to be used Examples of the installed software packages are the zlib-1.2.3-14.fc138.i386.rpm or glib-1.2.10-28.fc13.i386.rpm packages that can be found in the packages area on the Hardware Node after installing and caching the Fedora 13 OS EZ template.
Templates Overview • Scripts: • pre-cache: this script is executed before installing the packages included in the EZ template on the Hardware Node. • post-cache: this script is executed after installing the packages included in the EZ template on the Hardware Node. • pre-install: this script is executed before adding the EZ template to or installing the package inside the Container. • post-install: this script is executed after adding the EZ template to or installing the package inside the Container.
Templates Overview Differences Between OS and Application EZ Templates Actually, there are four major differences between OS EZ templates and application templates: • OS templates are used to create new Containers, whereas application templates provide additional software for already created Containers. • OS templates may and usually do use action scripts, whereas application templates cannot use action scripts in the current version of Parallels Virtuozzo Containers.
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.
CHAPTER 3 Managing EZ Templates This chapter describes how to create and manage EZ OS and application templates in Parallels Virtuozzo Containers. In This Chapter Creating an EZ Template ........................................................................................ 20 Setting Up Repositories and Proxy Servers for EZ Templates .................................. 27 Preparing OS EZ Templates for Creating Containers ...............................................
Managing EZ Templates Creating a Template from Official Templates The easiest way to create a template is to base it on one of the official templates shipped by Parallels and adjust its configuration to meet your demands: 1 Install the template you want to use as the basis for your new template (e.g., using the vzup2date -z command). 2 Create a copy of the directory containing the template configuration files.
Managing EZ Templates Installing vztt-build The first step in creating a template from scratch is to install the vztt-build package on your Node. This package contains • template metafile samples. You use metafile samples as the basis for creating a metafile for your own template. • the vzmktmpl utility. You use the vzmktmpl utility to create the template on the basis of your metafile.
Managing EZ Templates c %osarch. Provide the information about the microprocessor architecture where the OS EZ template is to be run: %osarch x86_64 You can set the value of the %osarch parameter to one of the following: * x86: specify if you plan to run the template on x86 platforms. * x86_64: specify if you plan to use the template on x86-64 platforms. As the template being created is intended for use on x86-64-bit platforms, the %osarch parameter is set to x86_64. d %packages.
Managing EZ Templates • Add the %appname parameter to the file to specify a name for the application template, for example: %appname php-customized • Do not include the %package_manager, %upgradable_versions, and %distribution parameters in the file. These parameters are allowed for OS templates only. • Make sure that the value of the %osname parameter corresponds to the name of the directory of the Linux distribution under which the application template is to be run.
Managing EZ Templates • rpm44x64: Red Hat Enterprise Linux 5 and CentOS 5 • rpm43x64: Red Hat Enterprise Linux 3 and 4, CentOS 3 and 4 • rpmzypp44x64: SUSE Linux Enterprise Server 11 with Service Pack 2 • rpm41x64: SUSE Linux Enterprise Server 10 and SUSE Linux 10.x • rpm41s9x64: SUSE Linux Enterprise Server 9 • rpmzypp49x64: openSUSE 12.1 • dpkgx64: Debian and Ubuntu Creating the Template with vzmktmpl In the last step, you use the vzmktmpl utility to create the template.
Managing EZ Templates # ls -l /vz/template/centos/5/x86_64/config/os/default ... -rwxr-xr-x 1 root root 453 Aug 13 22:12 post-cache -rwxr-xr-x 1 root root 3399 Aug 13 22:12 post-install -rwxr-xr-x 1 root root 610 Aug 13 22:12 pre-cache -rwxr-xr-x 1 root root 943 Aug 13 22:12 pre-upgrade ... For the full list of scripts, see the vzmktmpl section in the Parallels Virtuozzo Containers 4.7 Command Line Reference Guide.
Managing EZ Templates Setting Up Repositories and Proxy Servers for EZ Templates If you are going to use OS and application EZ templates in Containers, you first need to have one or more repositories with software packages prepared for these EZ templates. Package repositories are required for the EZ templates functioning due to the fact that these templates do not carry all the necessary package files inside themselves.
Managing EZ Templates Managing Default Repositories When you install an OS EZ template on the Node, it is preconfigured to use one or several package repositories storing Linux OS vendor's file sources. The path to the repositories for most OS EZ templates and their application EZ templates is automatically set during the EZ template installation in the mirrorlist or repositories files located in the /vz/template////config/os/default directory.
Managing EZ Templates Notes: 1. You can use the vzpkg info OS_template_name mirrorlist repositories command to view the mirrors and repositories for specific OS templates. 2. Commercial Linux distributions (e.g., Red Hat Enterprise Linux) do not have official repositories. You need to manually set up software repositories for such distributions before you can start using them. For more information, see to Setting Up Repositories with vzcreaterepo.
Managing EZ Templates Creating a Local Repository Along with using pre-configured repositories, you can create local repositories and configure for handling packages for your EZ templates. Organizing your own local repositories results in less bandwidth consumption and rapid software updates to Containers. You may also want to build a local repository if OS vendors or third-party software developers set up repositories that are not compatible with the vzpkg tool.
Managing EZ Templates • Container 101 is started. It has the IP address of 123.145.145.123 and can be accessed from other networks. • The apache web server is running inside Container 101 and the default document root for apache is /var/www/html, i.e. the apache web server stores its sites in the /vz/root/101/var/www/html directory on the Node. • The apache user and group inside Container 101 are apache.
Managing EZ Templates 8 Create the mirror list files and set the path to your local repository. For example, you can do this as follows: • For the Fedora 16 base RPM packages: # echo 'http://123.145.145.123/download/fedora/16/i386/os/' >> download/mirrors/fedoracore-16 • For the updated versions of the Fedora 16 RPM packages: # echo 'http://123.145.145.
Managing EZ Templates • To create the /vz/template/fedora/16/x86/config/os/default/repositories file on the Node and to make it point to the updated versions of the Fedora 16 RPM packages from your local repository: # echo 'file:///vz/root/101/var/www/html/download/fedora/updates/16/i386' >> /vz/template/fedora/16/x86/config/os/default/repositories 33
Managing EZ Templates Managing Repositories for Commercial Linux Distributions Commercial Linux distributions (e.g., Red Hat Enterprise Linux and SUS Linux Enterprise Server) do not have official repositories. So if you are going to run a commercial Linux distribution inside your Containers, you should create a special repository which will store the software packages of this distribution and enable you to update the packages inside your Containers.
Managing EZ Templates 4 Inside Container 111, create a directory where the RPM packages for Red Hat Enterprise Linux 4 will be stored: # mkdir -p /vz/root/111/var/www/html/download/redhat/as4/i386/os/ \ RedHat/RPMS 5 Copy the RPM packages from the RHEL 4 distribution disks to the /vz/root/111/var/www/html/download/redhat/as4/i386/os/RedHat/RPMS directory by executing the following command for each of the RHEL 4 CDs: # cp /media/cdrom/RedHat/RPMS*.
Managing EZ Templates 3 Create the /vz/root/111/var/www/html/download/mirrors/updates-releasedas4 mirror list file and make it point to the repository inside Container 111 where the updated versions of the RHEL 4 packages are stored: # echo "http://144.134.134.144/download/redhat/updates/as4/i386/" > \ /vz/root/111/var/www/html/download/mirrors/updates-released-as4 This command makes the /vz/root/111/var/www/html/download/mirrors/updates-released-as4 file on the Node and adds the http://144.134.134.
Managing EZ Templates Setting Up a Proxy Server for EZ Templates You can set up special caching proxy servers and use them to efficiently manage your OS and application EZ templates.
Managing EZ Templates Setting up a proxy server for managing EZ templates has the following advantages: 1 Your Internet bandwidth consumption is greatly reduced because all packages are downloaded to the proxy server only once and can then be used by any Node on your network. 2 You can more rapidly apply software updates to Containers since the proxy server where the downloaded packages are stored resides in the local network.
Managing EZ Templates Once you edit the /etc/httpd/conf.d/vzproxy.conf file, you need to tell the vzpkg tool to use the packages from the local repository on the proxy server while handling EZ templates. To do this, edit the /etc/vztt/vztt.conf file on the Node and specify the following parameters: • The URL of the proxy server, the port number where the httpd daemon is listening, and the path to the directory where the EZ templates local repository is located as the value of the VZTT_PROXY parameter.
Managing EZ Templates Setting Up an RHN Proxy Server for RHEL OS EZ Templates If you plan to run Red Hat Enterprise Linux 4 (RHEL 4) or 5 (RHEL 5) in Containers, you can create a special caching proxy server—RHN (Red Hat Network) Proxy Server. Using the RHN proxy server, you can greatly reduce your Internet bandwidth consumption and more rapidly apply software updates to Containers. RHN Proxy Servers can be created using the vzrhnproxy utility shipped with Parallels Virtuozzo Containers.
Managing EZ Templates • Create a pseudo-repository containing the repodata generated on the basis of the downloaded headers. • Grant the server with the IP address of 192.168.0.125 (i.e. our Node) access to the Proxy Server. 4 On the Node: • Open the /vz/template/conf/vztt/url.map file for editing (e.g. using vi) and change the value of the $RH_SERVER parameter as follows: $RH_SERVER http://192.168.10.10/rhn • Save the file. From this moment on: • If the Node with the IP address of 192.168.0.
Managing EZ Templates As you can see, three system profiles are currently registered with RHN: two for servers running the x86-64-bit version of RHEL 5 and one for the server running the 32-bit version of RHEL 5. For each of these profiles, the corresponding pseudo-repository containing the RHEL 5 package repodata exists on the Proxy Server. After some time, the repodata (and, consequently, the cache on the Proxy Server) may become obsolete.
Managing EZ Templates Preparing OS EZ Templates for Creating Containers OS EZ templates are used to create Containers on their basis. However, before you can use an OS EZ template for creating a Container, you need to do the following: 1 Install the OS EZ template on the Node. 2 Cache the installed OS EZ template. To install a new OS EZ template on the Node, you can use the vzpkg install template command.
Managing EZ Templates Installing Application EZ Templates The same way as you use an OS EZ template in a Parallels Virtuozzo Containers system to create any number of Containers on its basis and share its resources, you can use application EZ templates to share application files among any number of Containers. To install a new application EZ template on the Node, you can use the vzpkg install template command.
Managing EZ Templates Click Next to connect to the Parallels repository that stores EZ templates. If the connection is successful, the EZ Templates Selection window is displayed listing all EZ templates that you can install on your Node.
Managing EZ Templates In this window, do one of the following: • To download and install all available EZ templates for a certain Linux distribution, select this distribution by placing the cursor beside it and pressing the space bar on your keyboard; then click Next. • To download and install only certain EZ templates of the corresponding Linux distribution, place the cursor beside this distribution and press F2 on your keyboard.
Managing EZ Templates Once the EZ templates have been successfully downloaded to the Hardware Node, the Installing EZ templates window is displayed. In this window, you can view the templates ready to be installed on your Node. If you are installing a new OS EZ template, you can select the Run 'vzpkg cache' after installation check box to cache the OS EZ template right after its installation on the Node. Clicking Next starts installing the EZ templates on the Hardware Node.
Managing EZ Templates Uploading and Installing EZ Templates in Parallels Management Console If you have one or more new EZ templates that you would like to upload and install on the Hardware Node, you should first to have these templates accessible from the workstation where Parallels Management Console is installed (e.g.
Managing EZ Templates In this window, choose the EZ templates you want to deploy. To do this, click the Add button, and provide the path to the templates you would like to install on the Node. Click Next. The next screen will prompt you to define target Hardware Nodes where you wish to add new EZ templates. Parallels Management Console can upload and install the specified templates to any registered Hardware Node.
Managing EZ Templates The last page of the wizard allows you to review the settings made in the previous steps of the wizard. It summarizes the information provided by you in the previous steps, namely, which templates to install and where to install them. If you are satisfied with the settings, click the Finish button. This will launch the upload and installation process. Otherwise, click Back to make the necessary changes to the information entered.
Managing EZ Templates Listing EZ Templates The vzpkg list command allows you to list the EZ templates installed on the Node: # vzpkg list redhat-el5-x86 fedora-core-13-x86 2010-07-24 15:45:15 As you see, the redhat-el5-x86 and fedora-core-13-x86 EZ templates are available on the Node. The numerals next to the fedora-core-13-x86 EZ template inform you of the date and time when software packages included in the template were updated for the last time.
Managing EZ Templates The information on templates is presented in the table having the following columns: Column Name Descriptions Name The name of the EZ template. Version The template version. EZ templates do not have versions; so this column always displays n/a. Generation The type of the template: 'standard' or 'EZ'. All EZ templates have the EZ legend in this column. Description The description of the EZ template. Platform The platform where the EZ template can be used.
Managing EZ Templates Adding Application EZ Templates to Containers To add an application EZ template to an existing Container, you can use the vzpkg install command. To successfully add an application EZ template to a Container, this Container must be running.
Managing EZ Templates 2 In the Parallels Management Console right pane, right-click the application EZ template to add to the Container, and choose Install Into Containers. 3 Select the check boxes of the Containers where the application EZ template is to be added, and click Next. You can use the Select All/Deselect All buttons to select/deselect all Containers listed in the Choose Target Containers window.
Managing EZ Templates If you are adding an EZ template to only one Container, you can as well do the following: 1 Open the list of Containers in the Parallels Management Console main window by selecting the Parallels Virtuozzo Containers item in the Hardware Node tree. 2 Double-click the name of the Container where you want to add the EZ template.
Managing EZ Templates Updating Templates with vzup2date The vzup2date utility allows you to update any of the EZ templates installed on the Node. This utility can also be used to download new EZ templates to the Node and install them there. vzup2date can be launched in two modes: • graphical mode • command line mode Updating EZ templates in the graphical mode takes place if you have executed the vzup2date utility with the -z option.
Managing EZ Templates As soon as you press Next in the Welcome window, the utility will try to connect to the EZ templates repository (either the Parallels default repository or your own one) and, if the connection is successful, display the EZ Templates Selection window listing all EZ templates that have one or more updates available or that are not installed on your Node at all.
Managing EZ Templates This window allows you do one of the following: • If you wish to download and install all available EZ templates/template updates for a certain Linux distribution, select this distribution by placing the cursor beside it and pressing the space bar on your keyboard; then click Next. • If you wish only certain EZ templates of the corresponding Linux distribution to be installed/updated on the Node, place the cursor beside this distribution and press F2 on your keyboard.
Managing EZ Templates After the EZ templates/template updates have been successfully downloaded to the Node, the Installing EZ template window is displayed. In this window you can view the templates/template updates ready to be installed on your Node. If you are installing a new OS EZ template/template update, you can make use of the Run vzpkg cache after installation check box to cache the corresponding OS EZ template/template update right after its installation on the Node.
Managing EZ Templates Updating Templates With vzpkg update template Another way of updating your EZ templates installed on the Node is to use the vzpkg update template utility. This utility allows you to update OS or application EZ templates from the corresponding local RPM packages. For example, you can execute the following command to update the CentOS 5 OS EZ template installed on the Node from the centos-5-x86-ez4.7.0-3.noarch.
Managing EZ Templates Updating Templates in Parallels Management Console Parallels Management Console provides you with the Templates Update wizard allowing you to update any of EZ templates installed on your Hardware Node. You can also use this wizard to download new EZ templates to the Hardware Node and install them there. To invoke the Templates Update wizard, right-click the Templates item under the corresponding Hardware Node name, and choose Check for Template Updates.
Managing EZ Templates In this window, you can do one of the following: • To download and install all available EZ templates/template updates for a certain Linux distribution, click the Next button to go to the next step of the wizard. • To download and install only certain EZ templates of a Linux distribution, click on the plus sign next to the corresponding Linux distribution to display the list of application templates available for this distribution.
Managing EZ Templates Updating OS EZ Template Caches With the release of new updates for the corresponding Linux distribution, the created OS EZ template cache can become obsolete. So, Parallels Virtuozzo Containers provides the vzpkg update cache command allowing you to quickly update any of the OS EZ template caches available on the Hardware Node. Note: If you are going to update the cache of a commercial OS EZ template (e.g.
Managing EZ Templates 64
Managing EZ Templates Updating EZ Templates Packages In Containers Parallels Virtuozzo Containers allows you to update software packages of the OS EZ template a Container is based on and of any application EZ templates applied to the Container. You can do this by using the vzpkg update utility. Assuming that Container 101 is based on the redhatel5-x86 OS EZ template, you can run the following command to update all packages included in this template: # vzpkg update 101 redhat-el5-x86 ...
Managing EZ Templates 2 Double-click the name of the Container where you want to add an EZ template. The Container Manager opens. 3 Click the Templates item in the main tree of the Container Manager. 4 In the Container Manager right pane, click the OS Templates or Application Templates tab depending on what EZ template you wish to update. 5 Right-click the corresponding EZ template, and choose Update Installed Packages.
Managing EZ Templates On this screen, you can also select the Force templates installation check box to force the EZ template installation inside the Container. In this case no dependencies and no available versions of the application EZ template will be checked during its installation, which may cause the application EZ template to malfunction.
Managing EZ Templates Creating Historical Mirrors for Backed Up Containers If you have one or several Containers that are based on OS EZ templates and that were backed up long time ago, you may come across problems when trying to restore them on a destination server other than the source server (i.e. the Node where the Containers were hosted during their backing up).
Managing EZ Templates # mkdir fed13mirror The fed13mirror subdirectory will store an archive of the Fedora 10 repository. 2 Change to the fed10mirror subdirectory # cd fed13mirror and execute the following command: # rsync -av http://ftp.rhd.ru/pub/fedora/linux/releases/13/Everything/i386/os This command will make a copy of the entire Fedora 13 repository located at http://ftp.rhd.ru/pub/fedora/linux/releases/13/Everything/i386/os.
Managing EZ Templates Copying EZ Templates to Another Hardware Node Parallels Virtuozzo Containers allows you to copy the installed OS and application EZ templates from one Hardware Node to another using the vzmtemplate utility. For example, you can copy the fedora-core-13-x86 OS template installed on the Source Node to the Destination Node with the IP address of 192.168.0.9 by executing the following command: # vzmtemplate -z root@192.168.0.9 fedora-core-13-x86 root@192.168.0.
Managing EZ Templates In the displayed window, you can view the list of Hardware Nodes currently registered in Parallels Management Console. You can copy the template to any of the listed Nodes provided it is compatible with the Host OS installed on this Node. To do this, select the check box next to the template name, and click the Copy button to the right of the table.
Managing EZ Templates Removing Application EZ Templates From Containers The vzpkg remove command allows you to remove one or several application EZ templates from a Container.
Managing EZ Templates Removing EZ Templates From the Hardware Node The vzpkg remove template command allows you to remove from the Hardware Node those EZ OS and application templates that you do need any more. The process of removing an EZ template includes deleting all the RPM packages comprizing this template and all the caches available for this template (for EZ OS templates only). Keep in mind that the template to be removed must not be used by any Container; otherwise, the template deletion will fail.
Managing EZ Templates 2 In the right pane of the Parallels Management Console main window, do one of the following: • If you want to remove an EZ OS template from the Hardware Node, go to the OS Templates tab, right-click the EZ OS you wish to remove, and choose Delete. • If you want to remove an EZ application template from the Hardware Node, go to the Application Templates tab, right-click the EZ application template you wish to remove, and choose Delete.
Managing EZ Templates Converting Containers Based on Standard Templates You can use the vzveconvert utility to convert your existing Containers based on standard OS templates (and possibly having a number of standard application templates applied to them) to the EZ template-based ones.
Managing EZ Templates 5 The packages installed in the /vz/template/fedora-core/4/x86 directory on the Hardware Node (i.e.
Index Index A About Parallels Virtuozzo Containers 4.
Index Managing EZ Templates - 20 Managing Repositories for Commercial Linux Distributions - 34 O Organization of This Guide - 7 P Parallels Virtuozzo Containers Templates Overview - 11 Pool - 18 Preparing OS EZ Templates for Creating Containers - 43 R Removing Application EZ Templates From Containers - 72 Removing EZ Templates From the Hardware Node - 73 Repository default - 27, 28 for commercial Linux distributions - 27, 28, 34 local - 27, 30 S Scripts - 18 Setting Up a Proxy Server for EZ Templates 37
