lxc apt configuration

[Scott Moser]

On Mon, 29 Jul 2013, Mark Canonical Ramm-Christensen wrote:

> Another related suggestion that I have heard is to create packages for the
> Ubuntu Cloud images themselves, so that the normal apt machinery keeps the
> local base images up to date.   Either that or making a package that
> automates syncing down the cloud images using the same simple streams data
> we use for the actual clouds.

Yes, we want to do that.  There saucy contains 'sstream-sync' which can
be probably fairly easily be utilized to keep a 'cloudimg-precise-amd64'
as an alias for the most recent downloaded content.

> My theory is that making that first experience of the juju local provider
> as fast and easy as possible will be a big win for juju adoption.  And
> recent conversations with folks who were surprised at the deployment time
> of a local container at OSCON and gave up too quickly seems to back that
> up.

Having clean and up to date images is definitely important, but using a
local mirror or proxy is equally so.  It might even be more so.  I'd guess
that the download size of "apt-get dist-upgrade" on a reasonably recent
image of precise at this point is less data download and dpkg install than
'juju deploy wordpress' does in 'apt-get install PKGNAME'.

They're both important, really.

One thing I've been using recently, and I'm just giddy over is
'eatmydata'.  For the intended purpose of 'devbox' for the local provider,
we're probably not overly concerned about all possible 'fsync' calls
actually getting to disk.  eatmydata dramatically improves the speed of a
large 'apt-get' after the download occurs (well, maybe not 'dramatically'
on an SSD).

Scott
>
> --Mark Ramm
>
> On Mon, Jul 29, 2013 at 9:24 PM, Tim Penhey <tim.penhey at canonical.com>wrote:
>
> > On 30/07/13 12:32, Andreas Hasenack wrote:
> > > On Mon, Jul 29, 2013 at 7:37 PM, David Britton
> > > <david.britton at canonical.com <mailto:david.britton at canonical.com>>
> > wrote:
> > >
> > >     Just bumping this thread again:
> > >
> > >     Using squid-deb-proxy-{client/server} on my local net, it would be
> > >     nice if we had the option to append or influence the cloud-init that
> > >     is used to start the lxc containers on your local machine.  Does
> > >     anything like this exist?
> > >
> > >
> > > +1 for "influencing". Something like a .d directory where you could put
> > > your own additions to the cloud-config file that gets sent to the
> > instance.
> >
> > That certainly seems doable, and relatively easy.
> >
> > Someone care to document how they think this should behave?
> >
> > Tim
> >
> >
> > --
> > Juju mailing list
> > Juju at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju
> >
>