[lxc-devel] [PATCH] Add mechanism for container to notify host about end of boot

[Daniel P. Berrange]

On Thu, Sep 13, 2012 at 11:26:39PM +0200, Christian Seiler wrote:
> > I like the idea but haven't looked at the implementation yet as the
> > patch is really quite large. Quickly scanning through I briefly noticed
> > that the copyright headers for the new files are wrong (refer to IBM and
> > Daniel instead of Christian).
> 
> I just copy&pasted them from the other files, most header files I saw
> contained the same copyright. Just tell me what exactly to put there and
> then I'll do that for the next version of the patch.
> 
> > I'm also wondering if we shouldn't try to keep the "protocol" a bit more
> > generic to eventually allow the container to send/receive more than just
> > its status?
> 
> If we want to have a back-channel, we'd need a socket, which makes just
> doing echo RUNNING > /dev/lxc-notify impossible, you'd need a special
> program for that. Having the template scripts dump an additional script
> or upstart job or systemd unit file or whatever in the container when
> creating it seems a lot easier than having to use a special program.

FYI, the systemd team actually want to be able to expose a full socket
from the container to the host, so that the host systemd/systemctl cmd
can directly communicate with the container's systemd. So I don't think
that /dev/lxc-notify would be useful for systemd.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|