On Mon, Dec 15, 2014 at 01:34:27AM -0500, Nathan Scott wrote:
>
>
> ----- Original Message -----
> > > [...]
> > > Nathan Scott (1):
> > > libpcp/pmcd: protocol-level support for containers
> > > [...]
> >
> > Can you explain further your intended design for this, so we can get a
> > chance to review before it gets cast in stone?
> >
>
> We're discussing here the implementation of:
> http://www.pcp.io/pipermail/pcp/2014-June/005030.html
> ... for which the above was the first, preparatory commit of several
> pending commits.
...
(Note: I've never used containers on Linux, so I don't know what their
limitations/annoyances are. Therefore, I may be missing something totally
obvious that answers my questions - sorry.)
Interesting. As a Illumos (OpenSolaris-fork) fan & developer, I'm curious
if you've given any thought to what this would mean for Solaris/Illumos
zones.
There, the global zone has access to all the state of the non-global zones.
E.g., the list of mounts includes *all* the mounts across all the zones; the
list of processes includes *all* processes on the system. (If you are in a
non-global zone, you only see processes/mounts/etc. related to the zone you
are in.) I bring this up because a large-ish portion of the above link
seems to talk about how to deal with state extraction across the container
boundary.
FWIW, zones get a integer ID when they boot (rebooting a zone will change
its ID). There's a way to map it to a user-supplied zone name which is
persistent across zone reboots.
Jeff.
--
Bad pun of the week: The formula 1 control computer suffered from a race
condition
|