move already deployed service to new vps with different ip address.
Vasiliy Tolstov
v.tolstov at selfip.ru
Tue Oct 21 10:41:51 UTC 2014
2014-10-21 14:37 GMT+04:00 Kapil Thangavelu <kapil.thangavelu at canonical.com>:
> 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 at myenv-m1
> juju add-machine ubuntu at myenv-m2
> juju add-machine ubuntu at myenv-m3
Hm... nice! I don't think about manual creating lxc containers.
--
Vasiliy Tolstov,
e-mail: v.tolstov at selfip.ru
jabber: vase at selfip.ru
More information about the Juju
mailing list