Editing Virtuozzo 7 Technical Preview - Containers

Jump to: navigation, search

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:
[[Virtuozzo]] is a Linux distribution based on opensource OpenVZ components.
+
We are pleased to announce the official release of Virtuozzo 7.0 Beta 1. This is our first public release.
  
This is an early technology preview of Virtuozzo 7. We have made some good progress, but this is just the beginning. Much more still needs to be done. In the preview we replaced the containers engine and made our tools work with the new kernel technologies. We consider this beta a major milestone on the road to the official Virtuozzo 7 release and want to share the progress with the community.
+
More than ten years ago we released Virtuozzo containers. At that moment Linux kernel lacked isolation technologies and we had to implement it as a custom kernel patch. Since then we worked closely with the community to bring these technologies to upstream. Today it is part of most modern Linux kernels and there is no value in continue using proprietary technologies. So we made a
 +
decision to switch to upstream technologies as a strong foundation for the future of our product. 
  
== Key Changes ==
+
This is an early technology preview for Virtuozzo 7. We have made some good progress, but this is just a beginning. We still have a lot more to be done. At this point of time you won't see new cool features. We replaced an engine for containers and made our tools work with the new kernel technologies. We consider this delivery as major milestone on the road to official Virtuozzo 7 release and want to share the progress with our customers. In the future we'll be sharing our development progress continuously. The next step is introducing new virtual machines based on KVM. And then more features are coming.
* Virtuozzo 7 is based on RHEL7 and [[Download/kernel/rhel7-testing|Kernel 3.10+]]
 
* Containers are using kernel features cgroups and namespaces that limit, account for, and isolate resource usage as isolated namespaces of a collection of processes. The beancounters interface remains in place for backward compatibility. At the same time it acts as a proxy for actual cgroups and namespaces implementation.
 
* UUID instead of VEID for container identification. You can use UUID or name to identify a container. By default vzctl will treat the former VEID parameter as name.
 
* [[VCMMD|VCMM 4th generation of memory manager]]. We switched to memcg. By balancing and configuring memcg limits we will get the exact overcommit, shadow gangs, swap, page cache overuse Virtuozzo parameters. This will be done by a userspace daemon.
 
  
== Coming Soon ==
+
== Features ==
* Support of KVM-based virtual machines
 
* Containers online migration between Virtuozzo 7 nodes using the [http://criu.org/Main_Page CRIU project]
 
* Migration from Virtuozzo 6
 
  
== Dropped functionality==
+
[[Virtuozzo]] 7.0 Beta 1 provides significant improvements, including new features, in nearly all areas of the system:
* VZFS
 
* [[UBC|User bean counters]]
 
  
== Known Issues ==
+
* Virtuozzo 7 is based on [[Download/kernel/rhel7-testing|RHEL7 kernel]];
* Cannot boot Virtuozzo 7 TP with EFI. (#PSBM-34786)
+
* Containers are using kernel features cgroups and namespaces that limits, accounts for and isolates the resource usage as isolate namespaces of a collection of processes. Bean Counters interface remains in place for backward compatibility. At the same time it acts as a proxy for actual cgroups and namespace implementation;
* Autopartitioning for standard partitions in the Virtuozzo 7 TP installer does not work.For details, see [https://bugzilla.redhat.com/show_bug.cgi?id=1172441 RHEL bug #1172441]. (#PSBM-34787)
+
* UUID instead of VEID for container identification. You can use UUID or name to identify a container. By default vzctl will treat former VEID parameter as name;
 +
* [[VCMMD|VCMM 4th generation of memory manager]]. We switched to memcg. By balancing and configuring memcg limits we will get the exact overcommit, shadow gangs, swap, page cache overuse Virtuozzo parameters. This will be done by user-space daemon.
 +
 
 +
== Known issues ==
 +
 
 +
* Cannot boot Virtuozzo 7 Beta 1 with EFI. (#PSBM-34786)
 +
* Autopartitioning for standard partitions in the Virtuozzo 7 Beta 1 installer does not work. (#PSBM-34787)
 
* Installation may stop due to a Red Hat Enterprise Linux 7 bug. In this case, restart installation. For details, see [https://bugzilla.redhat.com/show_bug.cgi?id=1167948 RHEL bug #1167948]. (#PSBM-34797)
 
* Installation may stop due to a Red Hat Enterprise Linux 7 bug. In this case, restart installation. For details, see [https://bugzilla.redhat.com/show_bug.cgi?id=1167948 RHEL bug #1167948]. (#PSBM-34797)
 
* netconsole cannot be used along with bridged containers. (#PSBM-34959)
 
* netconsole cannot be used along with bridged containers. (#PSBM-34959)
* Container console does not work in OpenStack
+
* Container console does not work in Openstack
* Simfs is not working
 
* Delayed /vz mounting
 
  
 
== Download ==
 
== Download ==
* [https://download.openvz.org/virtuozzo/releases/7.0-beta1/x86_64/iso/ Installation ISO images]
+
 
 +
* [http://download.openvz.org/virtuozzo/releases/7.0/x86_64/iso/ Installation ISO images]
  
 
== Feedback ==
 
== Feedback ==
 +
 
* [[Mailing lists]]
 
* [[Mailing lists]]
* [https://bugzilla.openvz.org/enter_bug.cgi?product=OpenVZ Submit a bug] (choose "Virtuozzo 7" version)
+
 
 +
== See also ==
 +
 
 +
* [[Roadmap|Virtuozzo roadmap]]
 +
* [[Releases|Virtuozzo releases]]
 +
* [[History|OpenVZ history]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)