Big news for every serious OpenVZ user. Finally we have it!
Parallels, a sponsor behind OpenVZ project, is now offering an OpenVZ Maintenance Partnership program. The program provides bug resolution support and feature development to the OpenVZ community. The OpenVZ Maintenance Partnership has a small annual fee and provides two benefits to partnership members.
Partnership members will receive a support ID that will allow them to submit up to 10 high priority bugs per year. These bugs will be placed at the highest priority level in the development stack.
Partnership members will also be able to submit a feature request(s) which will be reviewed by the Parallels engineering team. They will work with you to clarify the requirements and implementation options and provide an implementation estimate and a schedule.
OpenVZ project has released both new vzctl and vzquota tools today.
New vzctl has a handful of new small features and a bunch of bugfixes, including compatibility with recent glibc, bash, and kernel headers.
New vzquota has only one (but quite useful) new feature -- an ability to explain what's wrong when it can not turn container's disk quota on or off. Recent OpenVZ kernels have a feature to report open files in container's private area, and now with the new vzquota the feature is finally available for mere mortals.
In the meantime Parallels has released Parallels Desktop for Mac 4.0 -- and that's just a coincidence, I'm sure they do not sync their release cycles with OpenVZ. Or maybe it's not a coincidence... We're sitting in the same office and for the last few weeks they've been providing free late dinners because of their release, that maybe made me leave the office later and thus maybe gave more time to work on OpenVZ tools. :)
SWsoft, sponsor of the OpenVZ project, has recently announced that it will adopt "Parallels" as a new corporate name moving into next year. So, you might ask what what does this mean for OpenVZ?
Absolutely nothing. We will keep doing what we do, providing new releases, fixing bugs, supporting our users and remain focused on integrating containers virtualization technology into the mainstream Linux.
Separate from the company name change, you'll see us slowly cease using the terms "VE" (virtual environment) and "OS-level virtualization". The terms commonly used in the industry are "containers" and "contaners-type virtualization" -- and we are already using those.
I tried it and was able to migrate a CentOS 7 container... but the Fedora 22 one seems to be stuck in the "started" phase. It creates a /vz/private/{ctid} dir on the destination host (with the same…
The fall semester is just around the corner... so it is impossible for me to break away for a trip to Seattle. I hope one or more of you guys can blog so I can attend vicariously.
Comments
Do you still stand by your opinions above now in 2016?…