© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Along the same lines as bug 1224515. Here the underlying openstack deployment seems to be using one network for both the private and floating ips:
| 0ea1f03f-
The best Juju can do is pick one to display in dns-name, there's no further information to pick out which is actually publicly routable. One solution is to add all the address information for machines to status, which would basically give the user the same option as juju itself does of trying to connect to both and seeing which works. There doesn't seem to be anything neater unless the deployment segregates its address spaces more clearly or we use neutron to inspect the exact setup.