Merge lp:~lifeless/juju/bug-945505 into lp:juju
|Status:||Work in progress|
|Diff against target:||70 lines (+7/-7) 3 files modified|
|To merge this branch:||bzr merge lp:~lifeless/juju/bug-945505|
|Related bugs and blueprints:||
Description of the Change
This changes the EC2 Machine provider to supply the public IP rather than the public DNS to the Machine instance. Machines don't have ip and dns, only one contact field, but that is stringifie pretty much everywhere, so putting ip addresses in it works fine.
I think we should probably rename the public and private names to endpoints, or something similar, to avoid confusion, but thats clearly orthogonal to this patch, which merely changes how its populated.
We don't, as far as I can tell, need to do this for internal names, as the inside-openstack dnsmasq instance handles them, its only the public ones, for the client machine, that need to avoid depending on DNS.
- 545. By Robert Collins on 2012-06-24
Use the EC2 IP address rather than public DNS name. Openstack clouds do
not have out of the box sane DNS mapping implementations (vs EC2 which
just has the ip address statically mapped in DNS), so the public name
returned by openstack is 'server-N' rather than something sensible like
3.openstack. domain' . Further complicating matters, folk running
private openstack deploys will often not have local DNS setup at all, and
using the IP address avoids all of that complexity.
This requires txaws rev 134, which is in quantal and will be backported to
precise in an SRU shortly.