What it could mean, besides the fact that OpenVZ team is a valueable contributor to the mainstream kernel? It also means we do care much for stability and security of OpenVZ, we do a lot of testing and QA, which is good for OpenVZ kernel, but for the mainstream kernel as well.
In a broader sense, this is a nice example of how collaborative open source development works. A nice example of “everybody wins” strategy. Indeed, in open source everybody wins.
Update: our kernel team found a bug in this blog post. Looks like the bug belongs to the infamous "off-by-one" category. :) There are actually 5 patches from OpenVZ developers, not 6 — it's just Greg sent one patchtwice and thus I counted it twice. Fixed.
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?…