Absolutely, especially the Python bit! I wrote a psuedo-OO wrapper
for OpenVZ (basically makes a bunch of vzctl calls at a higher layer
of abstraction so you can/start/stop/configure large numbers of
containers) and was thinking about writing something similar for LXC
that called the lxc-* BUT alw
2012/6/2 Rayson Ho :
> I'm from the Open Grid Scheduler Project (the official open source
> Grid Engine maintainer in the post Sun world), and we are using
> cgroups as the job container in our scheduler.
>
> Since LXC also uses cgroups, I was wondering if the developers want to
> change the behavi
Hi,
we've been talking (including a session at UDS) about getting a nice
API out of liblxc, with exports to python etc. This could be used: to
easily replace some of the tools which are currently scripts; to
increase code sharing with other projects - most immediately arkose and
libvirt; and to
Quoting Stéphane Graber (stgra...@ubuntu.com):
> On 05/25/2012 04:17 AM, Matthijs Kooijman wrote:
> > Hi Stéphane,
> >
> >> - stop: Is run after the container died
> >> [...]
> >> Potential other hooks include pre-start and post-stop
> > What would be the difference between stop and post-stop, if
