Overview of OpenVZ
1. OS Virtualization -
From the point of view of applications and Virtual Environment users,
each VE is an independent system. This independency is provided by a
virtualization layer in the kernel of the host OS. Note that only a
negligible part of the CPU resources is spent on virtualization (around
1-2%).
2. Network virtualization - The OpenVZ network virtualization layer is designed to isolate VEs from each other and from the physical network
3. Resource Management - OpenVZ resource management controls the amount of resources available for Virtual Environments. The controlled resources include such parameters as CPU power, disk space, a set of memory-related parameters, etc.
4. Two-Level Disk Quota - Host system (OpenVZ) owner (root) can set up a per-VE disk quotas, in terms of disk blocks and i-nodes (roughly number of files). This is the first level of disk quota. In addition to that, a VE owner (root) can use usual quota tools inside own VE to set standard UNIX per-user and per-group disk quotas.
5. Fair CPU scheduler - CPU scheduler in OpenVZ is a two-level implementation of fair-share scheduling strategy.
6. User Beancounters - User beancounters is a set of per-VE counters, limits, and guarantees. There is a set of about 20 parameters which are carefully chosen to cover all the aspects of VE operation, so no single VE can abuse any resource which is limited for the whole node and thus do harm to another VEs.
2. Network virtualization - The OpenVZ network virtualization layer is designed to isolate VEs from each other and from the physical network
3. Resource Management - OpenVZ resource management controls the amount of resources available for Virtual Environments. The controlled resources include such parameters as CPU power, disk space, a set of memory-related parameters, etc.
4. Two-Level Disk Quota - Host system (OpenVZ) owner (root) can set up a per-VE disk quotas, in terms of disk blocks and i-nodes (roughly number of files). This is the first level of disk quota. In addition to that, a VE owner (root) can use usual quota tools inside own VE to set standard UNIX per-user and per-group disk quotas.
5. Fair CPU scheduler - CPU scheduler in OpenVZ is a two-level implementation of fair-share scheduling strategy.
6. User Beancounters - User beancounters is a set of per-VE counters, limits, and guarantees. There is a set of about 20 parameters which are carefully chosen to cover all the aspects of VE operation, so no single VE can abuse any resource which is limited for the whole node and thus do harm to another VEs.
Comments
Post a Comment