Integrating OpenVZ (containers) functionality in Ubuntu Hardy Heron

Registered by Kir Kolyshkin

OpenVZ patch adds an ability to have multiple isolated, secure containers on top of one single Linux kernel, enabling better hardware utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; containers can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files. OpenVZ is in development for more than 5 years, it is mature, stable and featureful.

From the user's standpoint this is pretty much like Xen or KVM virtualization, the only differences are (1) performance is native, almost-zero overhead and (2) this is Linux-only, i.e. no other OSs.

OpenVZ team is committed to bringing this functionality in the mainstream Linux kernel; as of 2.6.24 good progress has been achieved (PID namespace, IPC namespace; utsname namespace; user memory controller are already merged; network namespace and kernel memory controller are in progress).

The idea is to have OpenVZ functionality in Ubuntu Hardy Heron. OpenVZ team is committed to porting OpenVZ to Hardy Heron's kernel, testing, supporting and fixing this kernel.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.