May 19th, 2006
During the Linux Tag in Germany (3-6 May) we met with a lot of interesting people. Perhaps the most surprising visit was from Andrew Morton (a kernel hacker, the right hand of Linus Torvalds) who came to our booth and said hello. As he was just from the plane that came in from the U.S., he had a bad jet lag, so the visit was short and he said he would stop by the next day.
And so he did. We showed Andrew what OpenVZ is, what it consists of and what it can do, including our cool "live migration" demo. Then Kirill Korotaev (our OpenVZ kernel team leader) and Andrew moved on to the kernel stuff, showing some lines of code to each other and discussing it. We have also discussed the possibility of merging some of the OpenVZ code, and how to do that the best possible way.
For those of you who like visuals, here is a photo of (from left to right) Kirill Korotaev, Andrew Morton, and me. ( 800x670 JPG, 73KCollapse )
The next day, Andrew gave a keynote about the Linux 2.6 development process. The funny thing was part of the presentation was telling why such big projects can't be easily merged. Among the reasons cited was out-of-tree development, length and complexity of patches, lack of people with the knowledge to review the code, etc. That doesn't mean OpenVZ can't be merged — that means the process is not going to be easy and fast.
And the story continued just today. Serge Hallyn from IBM sent another set of OS-virtualization patches, and Andrew replied with a general thoughts and a request for discussion of how we should proceed with merging some sort of OS-level virtualization. Surely this is not the first round, but as more people are actively involved chances are becoming higher for integrating OpenVZ code in the Linux kernel.
And so he did. We showed Andrew what OpenVZ is, what it consists of and what it can do, including our cool "live migration" demo. Then Kirill Korotaev (our OpenVZ kernel team leader) and Andrew moved on to the kernel stuff, showing some lines of code to each other and discussing it. We have also discussed the possibility of merging some of the OpenVZ code, and how to do that the best possible way.
For those of you who like visuals, here is a photo of (from left to right) Kirill Korotaev, Andrew Morton, and me. ( 800x670 JPG, 73KCollapse )
The next day, Andrew gave a keynote about the Linux 2.6 development process. The funny thing was part of the presentation was telling why such big projects can't be easily merged. Among the reasons cited was out-of-tree development, length and complexity of patches, lack of people with the knowledge to review the code, etc. That doesn't mean OpenVZ can't be merged — that means the process is not going to be easy and fast.
And the story continued just today. Serge Hallyn from IBM sent another set of OS-virtualization patches, and Andrew replied with a general thoughts and a request for discussion of how we should proceed with merging some sort of OS-level virtualization. Surely this is not the first round, but as more people are actively involved chances are becoming higher for integrating OpenVZ code in the Linux kernel.

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