On Tue, Oct 21, 2014 at 6:26 AM, Vasiliy Tolstov <[email protected]> wrote:
> 2014-10-21 14:18 GMT+04:00 Kapil Thangavelu < > [email protected]>: > > it looks like the machine agent isn't starting up, can you pastebin the > log > > machine-0.log from /var/log/juju > > > I find the issue - agent.conf have internal ip address =(. Does it > possible to manually enter all ip addresses / override it via command > line? Now i'm use sed to change ip address. > 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 -k > > -- > Vasiliy Tolstov, > e-mail: [email protected] > jabber: [email protected] >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
