For those who expressed interest in OpenVZ in the past,
I've just added a Review Request for vzctl, the OpenVZ control utility: https://bugzilla.redhat.com/show_bug.cgi?id=866495
As previously said, getting OpenVZ to work with Upstream Linux Kernel is a huge and ongoing effort. But with the release of vzctl 4.0, Fedora users should already be able to start a container with basic networking, and get it running.
Checkpoint/Restore is expecting to be working (and thus, live migration available) by no lator than Fedora 19, and will depend on an aditional userspace package to work (to be submitted any time soon)
Thanks
On Mon, Oct 15, 2012 at 9:59 AM, Glauber Costa glommer@gmail.com wrote:
For those who expressed interest in OpenVZ in the past,
I've just added a Review Request for vzctl, the OpenVZ control utility: https://bugzilla.redhat.com/show_bug.cgi?id=866495
As previously said, getting OpenVZ to work with Upstream Linux Kernel is a huge and ongoing effort. But with the release of vzctl 4.0, Fedora users should already be able to start a container with basic networking, and get it running.
Checkpoint/Restore is expecting to be working (and thus, live migration available) by no lator than Fedora 19, and will depend on an aditional userspace package to work (to be submitted any time soon)
Which package(s)? The criu-tools have already been packaged by Adrian Reber, so that's at least one down.
As for actually enabling the kernel config options for CRIU in the kernel, we talked about that yesterday at FUDCon. I need to discuss this with the kernel team still, but a tentative idea is to enable it in rawhide debug kernels to start with and see how things go from there. That's 3.7 based at the moment. I've resisted enabling it so far because namespaces aren't completed yet and it depends on those. It's also hidden behing CONFIG_EXPERT, which I _really_ don't want to enable because it makes the kernel configs a mess.
josh
On Mon, Oct 15, 2012 at 6:25 PM, Josh Boyer jwboyer@gmail.com wrote:
On Mon, Oct 15, 2012 at 9:59 AM, Glauber Costa glommer@gmail.com wrote:
For those who expressed interest in OpenVZ in the past,
I've just added a Review Request for vzctl, the OpenVZ control utility: https://bugzilla.redhat.com/show_bug.cgi?id=866495
As previously said, getting OpenVZ to work with Upstream Linux Kernel is a huge and ongoing effort. But with the release of vzctl 4.0, Fedora users should already be able to start a container with basic networking, and get it running.
Checkpoint/Restore is expecting to be working (and thus, live migration available) by no lator than Fedora 19, and will depend on an aditional userspace package to work (to be submitted any time soon)
Which package(s)? The criu-tools have already been packaged by Adrian Reber, so that's at least one down.
For live migration, that would be enough. I was actually unaware that criu has been packaged already, so this is very good news.
There are more userspace utilities to land, like vzlist, vzpid, etc, but those will be bundled in the vzctl package itself.
As for actually enabling the kernel config options for CRIU in the kernel, we talked about that yesterday at FUDCon. I need to discuss this with the kernel team still, but a tentative idea is to enable it in rawhide debug kernels to start with and see how things go from there. That's 3.7 based at the moment. I've resisted enabling it so far because namespaces aren't completed yet and it depends on those. It's also hidden behing CONFIG_EXPERT, which I _really_ don't want to enable because it makes the kernel configs a mess.
Well, there is a bunch of patches still in flight to give criu the ability to CR whole containers. But this is moving very fast. =)
On Mon, Oct 15, 2012 at 06:33:39PM +0400, Glauber Costa wrote:
On Mon, Oct 15, 2012 at 6:25 PM, Josh Boyer jwboyer@gmail.com wrote:
On Mon, Oct 15, 2012 at 9:59 AM, Glauber Costa glommer@gmail.com wrote:
For those who expressed interest in OpenVZ in the past,
I've just added a Review Request for vzctl, the OpenVZ control utility: https://bugzilla.redhat.com/show_bug.cgi?id=866495
As previously said, getting OpenVZ to work with Upstream Linux Kernel is a huge and ongoing effort. But with the release of vzctl 4.0, Fedora users should already be able to start a container with basic networking, and get it running.
Checkpoint/Restore is expecting to be working (and thus, live migration available) by no lator than Fedora 19, and will depend on an aditional userspace package to work (to be submitted any time soon)
Which package(s)? The criu-tools have already been packaged by Adrian Reber, so that's at least one down.
For live migration, that would be enough. I was actually unaware that criu has been packaged already, so this is very good news.
I have packaged crtools but not yet submitted for review. I was waiting until the kernel has enabled the necessary options. Without those options enabled the package does not make much sense. Once it is enabled I still plan to submit crtools for review.
Adrian
On 10/15/2012 08:11 PM, Adrian Reber wrote:
I have packaged crtools but not yet submitted for review. I was waiting until the kernel has enabled the necessary options. Without those options enabled the package does not make much sense. Once it is enabled I still plan to submit crtools for review.
You can submit it for review right away noting that it isn't expected to be functional. Others can review the spec meanwhile. Work can move forward in parallel. We have done that before.
Rahul
On Mon, 15.10.12 17:59, Glauber Costa (glommer@gmail.com) wrote:
For those who expressed interest in OpenVZ in the past,
I've just added a Review Request for vzctl, the OpenVZ control utility: https://bugzilla.redhat.com/show_bug.cgi?id=866495
As previously said, getting OpenVZ to work with Upstream Linux Kernel is a huge and ongoing effort. But with the release of vzctl 4.0, Fedora users should already be able to start a container with basic networking, and get it running.
Hey, can I interest you in supporting the interfaces listed here with openvz?
http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
This improves intergration of systemd with the container logic, and makes sure SELinux doesn't choke on the container, and "journalctl -m" on the host works fine.
Thanks,
Lennart