launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxxx>]

Hi Gary,

On 17 March 2012 01:35, Gary Poster <gary.poster@xxxxxxxxxxxxx> wrote:
> Hi Martin.
>
> We haven't announced setuplxc as a developer tool, AFAIK, even though it has
> had a commit or two in that direction, so I was somewhat surprised to hear
> that it was being used for that outside of our squad.  I guess I shouldn't
> have been.  So, first off, here's a warning for Launchpad developers.  I'm
> sorry we didn't send this out earlier.

No problem.  I guess I shouldn't be surprised word of mouth was
unreliable.  With hindsight, it would have helped if you'd posted
about the project even just "don't use it yet" or "we decided this is
not for setting up development environments", to correct people's
wrong impressions.

> Adding the DNS server is reasonable and expected AFAIK, and can be
> convenient if it works.  We will check with the LXC developers to make sure
> that our understanding is correct.

Right, they said something similar on that bug, so it sounds like
there might be a dnsmasq bug too.

> IIRC, there is a single function that does all of the non-lxc host changes.
>  Another single function creates the lxc container, and another configures
> the lxc container.

It looks a bit cleaner now than I remember it being a month ago.  The
modifications to the resolv conf file are made from create_lxc, which
I suppose is reasonable.  I suppose really just having some docs
listing all the changes and/or a bottleneck/greppable function through
which all changes are made to the host would be nice.

-- 
Martin