All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
OpenVZ 7.0
Just got the following email. What are your thoughts?
I’m pleased to announce the release of OpenVZ 7.0. The new release focuses on
merging OpenVZ and Virtuozzo source codebase, replacing our own hypervisor with
KVM.Key changes in comparison to the last stable OpenVZ release:
OpenVZ 7.0 becomes a complete Linux distribution based on our own VzLinux.
The main difference between the Virtuozzo (commercial) and OpenVZ (free)
versions are the EULA, packages with paid features, and Anaconda installer.The user documentation is publicly available [1].
EZ templates can be used instead of tarballs with template caches.
Additional features (see below)
This OpenVZ 7.0 release provides the following major improvements:
RHEL7 (3.10+) kernel.
KVM/QEMU hypervisor.
Guest tools for virtual machines that currently allow the following: to
execute commands in VMs from the host, to set user passwords, to set and obtain
network settings, to change SIDs, to enter VMs.Unified management of containers and KVM virtual machines with the prlctl tool
and SDK. You get a single universal toolset for all your CT/VM management needs.UUIDs are used to identify both virtual machines and containers. With
containers, prlctl treats the former VEID parameter as name.Virtual machine HDD images are stored in the QCOW2 format.
Ability to manage containers and VMs with libvirt and virt-manager or virsh
via a single driver for containers and virtual machines. Libvirt is an
open-source API, daemon, and management tool for managing virtualization
platforms. The API is widely used in the orchestration layer of hypervisors for
cloud-based solutions. OpenVZ considers libvirt as the standard API for managing
both virtual machines and containers. Libvirt provides storage management on the
physical host through storage pools and volumes which can be used in OpenVZ
containers.Memory guarantees. A memory guarantee is a percentage of container's or
virtual machine's RAM that said container or VM is guaranteed to have.Memory hotplugging for containers and VMs that allows both increasing and
reducing CT/VM memory size on the fly, without the need to reboot. Your
customers can now scale their workloads without any downtime. This feature also
enables you to make PAYG offerings, allowing customers to change VM resources
depending on workload and potentially pay less.Kernel same-page merging. To optimize memory usage by virtual machines, OpenVZ
uses a Linux feature called Kernel Same-Page Merging (KSM). The KSM daemon ksmd
periodically scans memory for pages with identical content and merges those into
a single page.VCMMD, the fourth-generation unified memory manager, and vcmmd, a single
daemon for managing memory of both virtual machines and containers. OpenVZ 7
uses memcg. Balancing and configuring memcg limits enables getting the exact
OpenVZ parameters like overcommit, shadow gangs, swap, page cache overuse.Container live migration via CRIU and P.Haul. In the previous versions of
OpenVZ, most operations performed during migration were done in the kernel
space. As a result, the migration process imposed a lot of restrictions. To
improve upon migration, Virtuozzo launched the CRIU project aiming to move most
of the migration code to the user space, make the migration process reliable,
and remove excessive restrictions.Containers use 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 and, at the
same time, acts as a proxy for actual cgroups and namespaces implementation.SimFS remains in OpenVZ 7.0, however, the support is limited and we don't have
plans to improve it in future.Known Issues
OpenVZ 7 includes vzctl from the commercial version. This means there is no
backward compatibility for the previous version of vzctl from OpenVZ.vzctl will be obsoleted in next version of OpenVZ, consider switching to
prlctl or virsh.The full list of known issues and limitations is provided in the documentation [1].
Download
All binary components as well as installation ISO images are freely available at
the OpenVZ download server [2] and mirrors [3]. The source code of each
component is available in the public repository [4].FAQ
Q: Can we use the binaries of OpenVZ/Virtuozzo 7.0 distribution in production?
A: Yes.Q: Is it possible to upgrade OpenVZ based on 2.6.32/2.6.18 to the OpenVZ/Virtuozzo 7?
A: Yes! Please follow the instructions in the OpenVZ 7 Upgrade Guide [1].Feedback
Our switching to the open development process is an attempt to work more closely
with the OpenVZ community. You can help us by sending your feedback to the
users@ mail list or submitting a bug in case of a serious issue [5].Links
[1] https://docs.openvz.org/
[2] https://download.openvz.org/virtuozzo/releases/7.0/x86_64/iso/
[3] https://mirrors.openvz.org/
[4] https://src.openvz.org/projects/OVZ
[5] https://bugs.openvz.org/Sincerely,
Sergey
Comments
So SIMFS exists, but is PLOOP gone in replacement for QCOW2?
Unless virtual machine really means KVM's and containers, which would make sense.
Francisco
would be nice if it had better docker integration.
Kinda sad that Virtuozzo is still being held back by stupid per VM licensing. They could have led the light weight container wave years earlier but instead are dead in the water as real hardware is cheaper than Virtuzzo as VMs get smaller.
Their target market is not LET.
So, how many providers are migrating all their Ovz nodes over to 7 tonight ?
I would hold off on it right now as it has no automation built into it yet. This is according to the tech i talked with. Said they have a version in beta but it would not be in this release.
Where did the email come from? I checked their mailing list and don't see anything.
It's in the announce mailing list, https://lists.openvz.org/pipermail/announce/2016-July/000664.html
https://lists.openvz.org/pipermail/announce/2016-July/000664.html
Thanks, guess i didn't think to check that one
What do you mean, "no automation"?
I'm surprised but happy at the same time to read it, I was waiting for it from such long.
Will it work properly with SolusVM and Virtualizort? Will the upgrade cause any issue on the management?
I think all providers should live migrate at least one node tonight.
Ploop will still be supported apparently.
Does it support XFS?
It's about damn time
Now Need wait for SolusVM update and other panels.
Ps this will delay SolusVM 2 for another 10 Yrs+
Interesting
We will be launching our version for OpenVZ 7 pretty soon.
For the pure drama value ;-)?
I did read a while back that openvz would be tied in to qemu in some way in future releases and memory guarantees would be transparent to end users, I suppose this is it.
tl;dr thin provisioned disk images backed by qemu, we will probably see 3 bits of info for ram on offers soon, total ram, guaranteed ram, vswap.
Who knows, should be interesting, I don't think I will be migrating any time soon, just running both in parallel and phasing the old out over time.
Looks interesting :-)
If i am not wrong WiredTree still uses Virtuozzo ? I remember using it when i had a VPS and a Hybrid with WiredTree back in 2010-2012
I expect that it will take quite some time before OVZ 7 will become popular. Especially with solusvm being slow with development, there will be a lack of decent control panels supporting OVZ 7.
On top of that LXC is also gaining popularity, and will probably become a good alternative to OVZ 7. Especially when popular control panels like solusvm will support it (which I doubt at this development stage though....).
We'll stick with OVZ 6 for now :-)
Yeah they do one reason I left them
I left them because they said good bye to me thanks to the ddos attacks on my VPS every month. When i was ready to leave they offered me a $500/month ddos protection
Leaving WiredTree was one of the best decision i ever made lol otherwise i was never going to get in LET market and realize i can get same stuff at less thn half price and learn some other tricks by managing my own VPS and Servers. The only positive of WiredTree was their quick support but well we were paying extra money for that support so that wasn't a bonus from them
If that means they will no longer maintain it for legacy then it will makes things interesting.
I think whatever provider launches ovz 7 first will see MASSIVE PROFITS.
I'm prepared to spend up to $1.50. Should I open a thread asking for providers to fight for it?
High roller!