|
|
|
|
The Container Properties tab allows adjusting the most general settings of a Virtuozzo Container:
Choose the SLM mode you prefer for the Container under creation in the drop-down menu. You can select one of the three options:
At this moment, Virtuozzo SLM manages memory resources, that is the promises of administrators about the amount of memory available to Containers. UBC is another resource managing mechanism implemented in Parallels Virtuozzo Containers for Linux versions. In comparison to UBC, SLM is a lot easier to adopt and understand, has less parameters, uses conventional terms and concepts, makes the configuration parameters intuitively clear and close to the notion of RAM size on a stand-alone computer and is more application-friendly in terms of how applications are signalled about memory restrictions and their chances to continue to operate with reduced memory usage or exit gracefully. The Container memory usage computation for SLM uses the same accounting mechanisms as in prior Parallels Virtuozzo Containers versions, but combines all types of memory into a single value. The SLM memory limit (slmmemorylimit) parameter fully substitutes the UBC parameters and includes oomguarpages, kmemsize, lockedpages and socket buffer space (tcpsndbuf, tcprcvbuf, othersockbuf).
Note: Detailed information on the Container resource management can be found in the Parallels Virtuozzo Containers Management of System Resources Administrator's Guide (for the old-style UBC parameters administration) and Overview of SLM in Parallels Virtuozzo Containers 3.0 for Linux (on the new SLM resources management).
Select the OS template (the OS the Container will run) from the OS template drop-down menu.
Only for Virtuozzo Container hosting plans: You can check the Name based hosting box to provide name-based Container.
Define the availability of root access for the Container (check the Root Access box to allow). This option is only available for IP-based Containers (if the Name based hosting box is unchecked).
Note: Name-based Containers cannot be used for Plesk Virtual Node type of hosting plans since the Container with Plesk server inside must have an external static IP address.