Using Deb Proxy to cache Debs to minimize time starting-up machines and its installation scripts
menno.smits at canonical.com
Wed Jul 5 22:13:27 UTC 2017
I use squid-deb-proxy to speed up deployments and it works well. If you're
using the lxd provider install the proxy on the host machine so that all
controllers and models benefit from the packages cached during previous
Ensure that squid-deb-proxy is configured to listen on the address of the
lxdbr0 bridge and remember to tell your Juju controllers and models to use
the proxy via the apt-http-proxy option. There's more detail on setting
this up here: https://github.com/juju/juju/wiki/Faster-LXD . There a
suggestion at the bottom of the page for defining a custom cloud type which
includes the options for speeding up test/development deployments. That
might be a good starting point for you.
On 6 July 2017 at 07:17, N. S. <n5pascal at hotmail.com> wrote:
> I am running juju latest version on local LXD.
> When deploying services,
> FOR each new machine, the "cloud init log" of the LXC in question captures
> some "apt-get install <some debs>"
> before starting up the machine and then i see that it's up to the
> "install" hook to install additional software and configure them.
> In my situation,
> I have some repetitive machines.
> I am thinking of using SQUID DEB PROXY or SIMILAR to cache the Debs for
> faster deploy of subsequent machines.
> My questions are:
> Where should I install and configure SQUID DEB PROXY or a similar PROXY?
> Is it on
> The host machine running the LXD including the controller juju-abcd-0?
> The controller machine juju-abcd-0 itself?
> So that I increase the "hit" rate of the needed-to-be-downloaded Debs and
> decease the readiness time?
> II. What proxy do you recommend?
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju