Quoting Jäkel, Guido (g.jae...@dnb.de):
>
> >On the other hand, I *do* also feel that any services on the containers
> >ought to be robust to unavailability, so that startup order should not
> >matter.
>
> Dear Serge,
>
> yes - it's Xmas time, bells are ringing and all is warm and bright. ;)
:)
>On the other hand, I *do* also feel that any services on the containers
>ought to be robust to unavailability, so that startup order should not
>matter.
Dear Serge,
yes - it's Xmas time, bells are ringing and all is warm and bright. ;)
Unfortunately, it matters to the greater part of software.
Quoting Jäkel, Guido (g.jae...@dnb.de):
> Hi all,
>
> here my 5ct on auto start and start order: Because i'm using a farm of LXC
> hosts where my containers may be spread over, i also need to persist the
> "preferred host" of a container. This is currently stored in a separate
> configuration file
Hi all,
here my 5ct on auto start and start order: Because i'm using a farm of LXC
hosts where my containers may be spread over, i also need to persist the
"preferred host" of a container. This is currently stored in a separate
configuration file. Because this information should be easy accessi
On Mon, 2012-12-10 at 11:35 -0600, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Mon, 2012-12-10 at 08:10 -0600, Serge Hallyn wrote:
> > > Quoting Michael H. Warfield (m...@wittsend.com):
> > > > There has been very little discussion in the main project over how to
>
Quoting Michael H. Warfield (m...@wittsend.com):
> On Mon, 2012-12-10 at 08:10 -0600, Serge Hallyn wrote:
> > Quoting Michael H. Warfield (m...@wittsend.com):
> > > There has been very little discussion in the main project over how to
> > > manage autobooting containers (or maybe I've missed it).
Quoting Michael H. Warfield (m...@wittsend.com):
> We do have the case with the current Ubuntu stuff, though, where it will
> start containers using config files that have not been run through
> lxc-create. Is this something we want to support??? Is it too great a
Not really, imo. I don't see a
On Mon, 2012-12-10 at 08:10 -0600, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > There has been very little discussion in the main project over how to
> > manage autobooting containers (or maybe I've missed it). Maybe it's
> > time we had it.
> >
> > What I do now is s
Quoting Michael H. Warfield (m...@wittsend.com):
> There has been very little discussion in the main project over how to
> manage autobooting containers (or maybe I've missed it). Maybe it's
> time we had it.
>
> What I do now is specific to my constellations of 6 lxc hosts (about 4
> dozen guest
On 12/08/2012 08:59 PM, Michael H. Warfield wrote:
> I like having the containers named for the host names
you could do both; if there's a prefix, it's started before non-prefixed
containers, and prefixes are 'stripped' so that whenever there's
anything deduced, it's without the prefix.
--
Add
On Sat, 2012-12-08 at 19:51 +0100, Daniel Baumann wrote:
> On 12/08/2012 06:24 PM, Michael H. Warfield wrote:
> > It's possible to drop a full configuration file there into /etc/lxc/auto and
> > not have it exist in /var/lib/lxc and then "-f " would work
> > while "-n $c -d" would fail. That woul
On 12/08/2012 06:24 PM, Michael H. Warfield wrote:
> It's possible to drop a full configuration file there into /etc/lxc/auto and
> not have it exist in /var/lib/lxc and then "-f " would work
> while "-n $c -d" would fail. That would be my guess there.
that was the intention when i wrote it in d
Hello,
I think I can answer part of this, even though I am not an Ubuntu
user... Maybe this will prompt some more generic discussion over
autoboot of containers and automatic lxc startup on some distros where
it's lacking.
On Fri, 2012-12-07 at 23:45 +0100, Papp Tamas wrote:
> hi All,
> Regardi
hi All,
Regarding the bug #1087765 is there a way in Ubuntu to specify the starting
order of containers?
I this this code in /etc/init/lxc.conf:
for f in /etc/lxc/auto/*; do
c="$(basename $f .conf)"
lxc-info -n $c 2>/dev/null | grep state | grep -q "RUNNING" ||
lxc-start
14 matches
Mail list logo
