In case you haven't seen it yet,
dowdle (Scott Dowdle) has done an interview with me on montanalinux.org. Here's the piece I like most:
ML: Can you update us on the current status of OpenVZ integration into the mainline kernel? Do you expect anything to happen in the near future regarding integration?
Kir: Most notable is the addition of the PID namespace patchset by Pavel Emelyanov into -mm (Andrew Morton's) tree -- it means the code will be in Linus' kernel in a few months. PID namespaces is a feature that makes it possible to have different sets of PIDs in different containers. The code was mostly developed by OpenVZ's Pavel Emelyanov, with some pieces from IBM's Sukadev Bhattiprolu. With the first version sent back in May, it was rewritten a few times to incorporate comments, suggestions and feature requests from everyone who was interested.
This is a good example of how we work together with other teams (this is truly a cooperative work between OpenVZ and IBM, with some help from other parties), and a good example of complexity -- after all, PID namespaces accounts for only about 5% of all OpenVZ code. IPC and utsname() virtualization which have been in the kernel since the release of 2.6.19, both account for another 5% or so. That means we have a long (and exciting!) way to go.
Anther good thing that happened was the acceptance of the user namespace patches from IBM (Serge Hallyn and Cedric Le Goater). This code is much smaller than the PID namespaces code -- what it does is add a basic ability for a container to have its own set of users, including root.
While those two patchsets will appear in the mainstream kernel soon, we have already backported those to our 2.6.22 kernel in order to give this new code a broader testing coverage. That actually helps -- we already found a small bug in the user namespaces code.
As for the future, I think that the rate of patches (and the rate of accepted patches!) will increase. I would guess that some kind of memory accounting (from OpenVZ beancounters) and some kind of network virtualization will be merged in a few months.
The interview is quite long; see the rest at montanalinux.org.
I'd also like to add that just a few days ago the memory controller patchset was also accepted into -mm tree. It does things similar to user beancounters in OpenVZ. So far, the accepted code only provides group-based RSS and page cache accounting, plus a generic infrastructure to add another accountables. The code was developed by Pavel Emelyanov and Balbir Singh (of IBM) in close collaboration.
With that in place, today Pavel already sent the first version of kernel memory controller. The code is not aimed for inclusion yet -- it is mostly aimed at spiking the discussion and trying to determine the needs.
ML: Can you update us on the current status of OpenVZ integration into the mainline kernel? Do you expect anything to happen in the near future regarding integration?
Kir: Most notable is the addition of the PID namespace patchset by Pavel Emelyanov into -mm (Andrew Morton's) tree -- it means the code will be in Linus' kernel in a few months. PID namespaces is a feature that makes it possible to have different sets of PIDs in different containers. The code was mostly developed by OpenVZ's Pavel Emelyanov, with some pieces from IBM's Sukadev Bhattiprolu. With the first version sent back in May, it was rewritten a few times to incorporate comments, suggestions and feature requests from everyone who was interested.
This is a good example of how we work together with other teams (this is truly a cooperative work between OpenVZ and IBM, with some help from other parties), and a good example of complexity -- after all, PID namespaces accounts for only about 5% of all OpenVZ code. IPC and utsname() virtualization which have been in the kernel since the release of 2.6.19, both account for another 5% or so. That means we have a long (and exciting!) way to go.
Anther good thing that happened was the acceptance of the user namespace patches from IBM (Serge Hallyn and Cedric Le Goater). This code is much smaller than the PID namespaces code -- what it does is add a basic ability for a container to have its own set of users, including root.
While those two patchsets will appear in the mainstream kernel soon, we have already backported those to our 2.6.22 kernel in order to give this new code a broader testing coverage. That actually helps -- we already found a small bug in the user namespaces code.
As for the future, I think that the rate of patches (and the rate of accepted patches!) will increase. I would guess that some kind of memory accounting (from OpenVZ beancounters) and some kind of network virtualization will be merged in a few months.
The interview is quite long; see the rest at montanalinux.org.
I'd also like to add that just a few days ago the memory controller patchset was also accepted into -mm tree. It does things similar to user beancounters in OpenVZ. So far, the accepted code only provides group-based RSS and page cache accounting, plus a generic infrastructure to add another accountables. The code was developed by Pavel Emelyanov and Balbir Singh (of IBM) in close collaboration.
With that in place, today Pavel already sent the first version of kernel memory controller. The code is not aimed for inclusion yet -- it is mostly aimed at spiking the discussion and trying to determine the needs.


Comments
Do you still stand by your opinions above now in 2016?…