Editing User Guide/OpenVZ Philosophy
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 73: | Line 73: | ||
In this section we will try to let you form a more or less precise idea of the way the OpenVZ software operates on your computer. Please see the figure. | In this section we will try to let you form a more or less precise idea of the way the OpenVZ software operates on your computer. Please see the figure. | ||
− | [[Image:OpenVZ technology.png | + | [[Image:OpenVZ technology.png]] |
This figure presumes that you have a number of physical servers united into a network. In fact, you may have only one dedicated server to effectively use the OpenVZ software for the needs of your network. If you have more than one OpenVZ-based physical server, each one of the servers will have a similar architecture. In OpenVZ terminology, such servers are called ''Hardware Nodes'' (or just ''Nodes''), because they represent hardware units within a network. | This figure presumes that you have a number of physical servers united into a network. In fact, you may have only one dedicated server to effectively use the OpenVZ software for the needs of your network. If you have more than one OpenVZ-based physical server, each one of the servers will have a similar architecture. In OpenVZ terminology, such servers are called ''Hardware Nodes'' (or just ''Nodes''), because they represent hardware units within a network. |