49ff7b524b
As documented in bug 901594, previous nova releases, the IP address was exposed as the DNS hostname, which worked well with euca-tools. This is unfortunately not always ideal for private clouds. Whilst it is expected to be able to euca-describe-instances --ipv4 in newer euca2ools releases, this behaviour is not always desired. This patchset allows the nova admin to set a global flag of: --ec2_private_dns_show_ip=True, to restore legacy nova behaviour. This does not change the current default behaviour of nova. Change-Id: I7c71ffe63929d90d45d9c724ab3409dcdee52b44
The Choose Your Own Adventure README for Nova
You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs.
To monitor it from a distance: follow @openstack on twitter.
To tame it for use in your own cloud: read http://docs.openstack.org
To study its anatomy: read http://nova.openstack.org
To dissect it in detail: visit http://github.com/openstack/nova
To taunt it with its weaknesses: use http://bugs.launchpad.net/nova
To watch it: http://jenkins.openstack.org
To hack at it: read HACKING
To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations