How much of a mess does OpenVZ make? ;) Was: What can OpenVZ do?
Eric W. Biederman
ebiederm at xmission.com
Fri Mar 13 17:27:02 PDT 2009
Oren Laadan <orenl at cs.columbia.edu> writes:
> Dave Hansen wrote:
>> On Fri, 2009-03-13 at 14:01 -0700, Linus Torvalds wrote:
>>> On Fri, 13 Mar 2009, Alexey Dobriyan wrote:
>>>>> Let's face it, we're not going to _ever_ checkpoint any kind of general
>>>>> case process. Just TCP makes that fundamentally impossible in the general
>>>>> case, and there are lots and lots of other cases too (just something as
>>>>> totally _trivial_ as all the files in the filesystem that don't get rolled
>>>> What do you mean here? Unlinked files?
>>> Or modified files, or anything else. "External state" is a pretty damn
>>> wide net. It's not just TCP sequence numbers and another machine.
>> This is precisely the reason that we've focused so hard on containers,
>> and *didn't* just jump right into checkpoint/restart; we're trying
>> really hard to constrain the _truly_ external things that a process can
>> interact with.
>> The approach so far has largely been to make things are external to a
>> process at least *internal* to a container. Network, pid, ipc, and uts
>> namespaces, for example. An ipc/sem.c semaphore may be external to a
>> process, so we'll just pick the whole namespace up and checkpoint it
>> along with the process.
>> In the OpenVZ case, they've at least demonstrated that the filesystem
>> can be moved largely with rsync. Unlinked files need some in-kernel TLC
>> (or /proc mangling) but it isn't *that* bad.
> And in the Zap we have successfully used a log-based filesystem
> (specifically NILFS) to continuously snapshot the file-system atomically
> with taking a checkpoint, so it can easily branch off past checkpoints,
> including the file system.
> And unlinked files can be (inefficiently) handled by saving their full
> contents with the checkpoint image - it's not a big toll on many apps
> (if you exclude Wine and UML...). At least that's a start.
Oren we might want to do a proof of concept implementation like I did
with network namespaces. That is done in the community and goes far
enough to show we don't have horribly nasty code. The patches and
individual changes don't need to be quite perfect but close enough
that they can be considered for merging.
For the network namespace that seems to have made a big difference.
I'm afraid in our clean start we may have focused a little too much
on merging something simple and not gone far enough on showing that
things will work.
After I had that in the network namespace and we had a clear vision of
the direction. We started merging the individual patches and things
More information about the Containers