Scott Moser
55128d1c5d
The changes here are coming as a result of starting on blueprint config-drive-v2 [1]. I wanted to separate out the "Metadata" from the "Metadata Server". Thus, the creation of nova/api/metadata/base.py. The InstanceMetadata in base.py contains most of the logic for presenting metadata. As a result, the Metadata webservice in handler.py greatly simplified. This should make it easier to render duplicate data to a config drive. Additional changes here: * a few more tests * removal of the separate 'Versions' handler. Its now replaced by the single handler. Change-Id: I35fcfd8d7f247763954afc0a9f752f629b243e9b
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 <http://twitter.com/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