Go to file
Vishvananda Ishaya 9ae539c452 Separate metadata api into its own service
part 1 of blueprint separate-nova-metadata

 * adds api/metadata/ and moves code from ec2
 * moves metadata into separate binary
 * changes metadata forward to use metadata host and port
 * moves the metadata accept rule to the metadata api
 * adds nova-api-* to setup.py

Change-Id: I7f5d8e6cafc55b5c383cd88991f29c6059fb8d82
2011-11-15 13:27:58 -08:00
2011-09-09 08:46:58 +02:00
2011-07-26 09:50:05 +04:00
2010-05-27 23:05:26 -07:00
2011-11-10 12:01:08 -05:00

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 laugh at its PEP8 problems: http://jenkins.openstack.org/job/nova-pep8/

To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations

Description
RETIRED, Client code for the common scheduler for OpenStack
Readme 18 MiB