In addition to that, a container owner (root) can use usual quota tools inside own container to set standard UNIX per-user and per-group disk quotas. Host system (OpenVZ) owner (root) can set up a per-container disk quotas, in terms of disk blocks and i-nodes. Say, if there is a need to give a container less memory, one just change the appropriate parameters on the fly. Please note that all those resources can be changed while container is running, there is no need to reboot. OpenVZ resource management consists of three components: two-level disk quota, fair CPU scheduler, and user beancounters. Really, each container should stay within its boundaries and not affect other containers in any way - and this is what resource management does. IPC objects Shared memory, semaphores, messages.Īs all the containers are using the same kernel, resource management is of paramount importance. #Openvz beancounter scripts serialPlus, if needed, any container can be granted access to real devices like network interfaces, serial ports, disk partitions, etc. Devices A lot of devices are virtualized. Network Virtual network device, which allows a container to have its own IP addresses, as well as a set of netfilter (iptables) and routing rules. PIDs are virtualized, so that the init PID is 1 as it should be. Process tree A container only sees its own processes (starting from init). Users and groups Each container has its own root users, as well as other users and groups. So each has its own Files System libraries, applications, virtualized /proc and /sys, virtualized locks etc. OpenVZ kernel adds provides virtualization/isolation, resource management, and checkpointing.Įach container is a separate entity, and from the point of view of its owner it looks like a real physical server.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |