Editing WP/What are containers
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
+ | = OpenVZ Linux Containers technology whitepaper = | ||
+ | <s><big><big><b>{{PDFlink|[[Media:What are containers.pdf|Download in PDF]]}}</b></big></big></s> | ||
+ | |||
OpenVZ is an open source virtualization technology for Linux that enables the partitioning of a single physical Linux machine into multiple smaller independent units called containers. | OpenVZ is an open source virtualization technology for Linux that enables the partitioning of a single physical Linux machine into multiple smaller independent units called containers. | ||
Line 94: | Line 97: | ||
* '''Disk I/O priority'''. Containers compete for I/O operations, and can affect each other if they use the same disk drive. OpenVZ introduces a per-container I/O priority, which can be used to e.g. decrease the "bad guy" I/O rate in order to not trash the other containers. | * '''Disk I/O priority'''. Containers compete for I/O operations, and can affect each other if they use the same disk drive. OpenVZ introduces a per-container I/O priority, which can be used to e.g. decrease the "bad guy" I/O rate in order to not trash the other containers. | ||
− | * '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container. | + | * '''Disk I/O bandwidth'''. I/O bandwidth (in bytes per second) can be limited per-container (currently only available in commercial Parallels Virtuozzo Containers). |
=== Memory === | === Memory === | ||
Line 167: | Line 170: | ||
* '''DHCP''' and dynamic IP addresses are possible | * '''DHCP''' and dynamic IP addresses are possible | ||
* Broadcasting have negative performance impact (it is delivered separately to each CT) | * Broadcasting have negative performance impact (it is delivered separately to each CT) | ||
+ | * | ||
==== Real network device in a container ==== | ==== Real network device in a container ==== | ||
Line 178: | Line 182: | ||
=== Performance and density === | === Performance and density === | ||
− | * | + | * {{FIXME|need to add data}} |
− | |||
=== Limitations === | === Limitations === |