User`s guide

Managing Resources 118
Managing Container Resources
Configuration
Any Container is configured by means of its own configuration file. You can manage your
Container configurations in a number of ways:
1 Using configuration sample files shipped with Parallels Server Bare Metal. These files are
used when a new Container is being created (for details, see the Creating and Configuring
New Container section). Currently, the following configuration sample files are provided:
 basic – to be used for creating standard Containers.
 confixx – to be used for creating Containers that are to use the Confixx control panel.
 slm.plesk - to be used for creating Containers with the Plesk control panel.
 slm.256MB - to be used for creating Containers with 256 MB of main memory.
 slm.512Mb - to be used for creating Containers with 512 MB of main memory.
 slm.1024Mb - to be used for creating Containers with 1024 MB of main memory.
 slm.2048Mb - to be used for creating Containers with 2048 MB of main memory.
Note: Configuration sample files cannot contain spaces in their names.
Any sample configuration file may also be applied to a Container after it has been created.
You would do this if, for example, you want to upgrade or downgrade the overall resources
configuration of a particular Container:
# pctl set 101 --applyconfig basic --save
This command applies all the parameters from the ve-basic.conf-sample file to the
given Container.
When you install Parallels Server Bare Metal on your server, the default Container samples
having the ve-<name>.conf-sample names are put to the /etc/vz/conf directory.
In this connection you should keep in mind the following when working with Container
samples:
 When you create a Container using the pctl create command utility and base it on
some Container sample, this sample is taken from the /etc/vz/conf directory.
 If you modify an existing Container sample or create a new sample using specific
command line utilities (e.g. vzsplit, vzcfgscale), the changes are made to the
corresponding file in the /etc/vz/conf directory or the resulting Container sample is
put to this directory.
2 Using specific utilities for preparing configuration files in their entirety. The tasks these
utilities perform are described in the following subsections of this section.
3 The direct creating and editing of the corresponding Container configuration file
(/etc/vz/conf/<CT_ID>.conf). This can be performed with the help of any text
editor. The instructions on how to edit Container configuration files directly are provided in
the four preceding sections. In this case you have to edit all the configuration parameters
separately, one by one.