On Tue, Oct 21, 2014 at 8:08 AM, Vasiliy Tolstov <[email protected]> wrote:
> 2014-10-21 14:37 GMT+04:00 Kapil Thangavelu < > [email protected]>: > > the other option to try, rather than using manual on localhost, is to use > > manual on lxc containers created within host, this isolates all the juju > > components to things in containers off the lxc bridge, which won't change > > addresses as you image and reinstance. that still leaves one extra piece > of > > writing something to scan status and to forward traffic to exposed > services > > via iptables. as an example of doing something like that > > https://github.com/kapilt/juju-lxc/blob/master/juju_lxc/add.py#L37 .. or > > alternatively via cli something like > > > > lxc-create -t ubuntu-cloud -n trusty-base -- -r trusty -S > ~/.ssh/id_rsa.pub > > lxc-clone -B aufs trusty-base myenv-m1 > > lxc-clone -B aufs trusty-base myenv-m2 > > lxc-clone -B aufs trusty-base myenv-m3 > > > > lxc-start -d -n myenv-m1 > > ... > > > > juju bootstrap ubuntu@myenv-m1 > > juju add-machine ubuntu@myenv-m2 > > juju add-machine ubuntu@myenv-m3 > > > This is not works =( > > sudo lxc-clone -B aufs trusty-base juju > > lxc_container: aufs is only for snapshot clones > lxc_container: failed getting pathnames for cloned storage: > /var/lib/lxc/trusty-base/rootfs > lxc_container: Error copying storage > clone failed > > try with -s ie. $ sudo lxc-clone -s -B aufs trusty trusty-new Created container trusty-new as snapshot of trusty
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
