fast containers & dev workflow with juju 1.18
Serge E. Hallyn
serge at hallyn.com
Fri Apr 11 21:17:58 UTC 2014
Quoting Kapil Thangavelu (kapil.thangavelu at canonical.com):
> Hi Folks,
>
> instructions on getting a speedy workflow with local provider (a container
> per second)
Hey Kapil,
sounds interesting - but I don't see a link? Is it hidden in plain
sight?
> with juju's builtin local provider (running 1.18) if you have btrfs @
> /var/lib/lxc and install squid-deb-proxy on the host, and run juju set-env
> apt-http-proxy="http://10.0.3.1:8000" you should be able to use the local
> provider with significant speed improvements. (clone for containers package
> caches, you also need to modify the squid deb proxy conf to allow for ppa
> access). that won't include nested containers or device access (open juju
> bugs for hat) you can however use add-machine kvm:0 to get a kvm machine in
> local provider for greater machine access on particular workloads. you'll
> need to configure the 'network-bridge' option in environments.yaml to point
> to virbr0 so lxc and kvm come up on the same network. The first container
> will see some lag as juju downloads and populates the lxc cloud images into
> /var/cache/lxc and creates a template container for subsequent cloning.
>
> cheers,
>
> Kapil
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
More information about the Juju
mailing list