I’m a long-time OpenVZ user running a few hundred OpenVZ containers and administrating another ~80 at my job for a data center, but actually I am unsure about the OpenVZ 7 thingy. Without even taking a closer look at OpenVZ 7, just by reading the „released“ page, I noticed a few things I don’t like
Don’t get me wrong. I *love* OpenVZ. I’m the guy at work you’ll throw „you and your openvz stuff…“ sentences at the head. I’m the one who doesn’t understand the world if people who develop a virtualization panel state that OpenVZ based on 2.6.x wouldn’t run/work in debian jessie (Guess what I have running – A decent sysadmin just needs about 15 minutes to find out, how. *hint* sysvinit *hint* *extrahint* sysvinit works fine in jesssie *extrahint* *superhint* openvz as well *superhint*)…
The article I am referring to is about the release of OpenVZ 7.0. Let’s take a quick look at some statements:
The new release focuses on merging OpenVZ and Virtuozzo source codebase, replacing our own hypervisor with KVM.
Might be my english, but what the hell has OpenVZ to do with KVM? And since when does OpenVZ had a hypervisor? If OpenVZ was a hypervisor, then we wouldn’t call the VEs containers but guests and our so-called guests wouldn’t share the (same) host-kernel. Probably that statement is referring to Virtuozzo or the new OpenVZ turns into a KVM thingy.
OpenVZ 7.0 becomes a complete Linux distribution based on our own VzLinux.
Nothing here states that I will still be able to use my favorite distribution. That at least makes me think and is already a no-way for me.
The main difference between the Virtuozzo (commercial) and OpenVZ (free) versions are the EULA, packages with paid features, and Anaconda installer.
Well. I nearly stopped reading at EULA. Anyway. I did not need that stuff before, why should I need or actually WANT it now?
The user documentation is publicly available.
EZ templates can be used instead of tarballs with template caches.
Sooner or later I’ll start to rant. Seriously. Now I am interested in what EZ templates are – Clicking the link in the article presents me with a nice 404. I guess that’s what they mean with „publicly available“. Now right after using google for that, it pretty much looks like EZ templates are some management utilities to work with „tarballs with template caches“. But probably I didn’t google hard enough.
Additional features (see below)
Now it is getting interesting!
RHEL7 (3.10+) kernel.
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.
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.
Virtual machine HDD images are stored in the QCOW2 format.
Seriously. The whole article reads as if OpenVZ 7 is all about KVM. Most if not all those nice features have been available with plain qemu/kvm for centuries. And the post states nearly „nothing“ about OpenVZ as we know it. Apart from that they’ll let simfs still work. For a while. Right. And instead of useful names we’ll get UUIDs.
Well. That change / switch is obviously not made for me:
- I do use simfs for various reasons (including files from the guest in the host for attack-prevention, simple host-based backups, easier for me to organize my storage (compression, encryption, etc), few more reasons..). Thats why I didn’t use ploop. While simfs will still work, they have no plans to improve it and the support is limited.
- I do not want to use some weird distribution just to run containers. I’ll stick to the distributions I’m used to. It’s not about that I do not like to learn something new, it’s about that I just don’t want to install a new system everytime something new is there AND while I know about the problems with the distributions I’m used to, I might not be able to handle problems with that new distribution that easy. Hence making this impossible for a production environment for me.
- I don’t want that extra stuff (anaconda.., kvm..) while not a real reason – I really just want containers.
Well, instead of crying I am just playing around with LXC now. I fear a bit because of the privileged vs unprivileged stuff but.. Let’s see. I also found another very very interesting project. Did you read about ClearLinux? If not, you should take a look.
P.S.: Kir, why?!1?!1!1!!1!ELEVEN