2014-10-15 11:08 GMT+04:00 John Meinel <[email protected]>: > You could probably edit the /var/lib/juju/agents/unit-*/agent.conf and > /var/lib/juju/agents/machine-*/agent.conf to change the IP addresses stored > there (everyone needs to know how to get back to the API server). > > Generally the API server filters out 127.0.0.1 when reporting its possible > addresses to other units, since *most* of the time they can't actually > contact it at 127.* > In fact, the only time it works is when they are colocated, if you used > containers or VMs the 127.* address wouldn't ever work. > And generally colocating your services with the API server is considered a > security issue. (You have to give your cloud credentials to the API server > if you want to let it start instances for you, but that information should > not be available to the services you deploy.) > > If you did deploy into containers (like juju deploy --to lxc:0) then the > services would be isolated, and likely the API server would get a 10.0.3.1 > address, which could be preserved between packing it up and putting it > somewhere else.
Problem not in state server, as i see in wordpress config i have address 10.0.2.15 as i understand in relation-change than i'm attach mysql it gets it public_ip (that can't be 127 as it ignored). As i understand i need to delete relation from wordpress to mysql and add it again.. or not? -- 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
