![](/r/images/1.gif) |
What is Virtual Environment (VE)?
VE behaves exactly like an isolated stand-alone server |
![](/r/images/1.gif) |
![Yes](/r/upload/red_ok.gif) |
Appears to have its own processes, users, files and provides full root access |
![Yes](/r/upload/red_ok.gif) |
Each has its own IP addresses, port numbers, tables, filtering and routing rules |
![Yes](/r/upload/red_ok.gif) |
Each could have its own configuration files for the system and app software |
![Yes](/r/upload/red_ok.gif) |
Each could have its own versions of system libraries or modify existing ones |
![Yes](/r/upload/red_ok.gif) |
Each could delete, add, modify any file, including files in /root, and install its own application software or custom configure/modify root application software |
![Yes](/r/upload/red_ok.gif) |
Example: In Linux case multiple ?distributions? can be ran on the single box. |
Quality of Service to provide dedicated SLAs for each VE
|
|
![](/r/images/1.gif) |
![Yes](/r/upload/red_ok.gif) |
Standard: Includes CPU, disk space and network guarantees
|
|
![Yes](/r/upload/red_ok.gif) |
Unique: Guarantees on memory - user and kernel, physical and virtual
|
|
![Yes](/r/upload/red_ok.gif) |
Unique: Guarantees on disk I/O and many other critical resources (over 20).
|
|
VE runs off-the-shelf software without any changes
|
|
![VE runs off-the-shelf software without any changes](/r/upload/ve-illustration.gif) |
|