Go to file
Kei Masumoto a98c52b6b3 fixed based on reviewer's comment.
1. erase wrapper function(remove/exists/mktempfile) from nova.utils.
2. nova-manage service describeresource(->describe_resource)
3. nova-manage service updateresource(->update_resource)
4. erase "my mistake print" statement

Additional changes are made at:
1. nova.image.s3.show
2. nova.compute.api.create

that's because instances cannot launched without this changes.
2011-02-18 14:15:04 +09:00
2011-02-18 14:15:04 +09:00
2010-12-16 19:13:37 +00:00
2011-02-10 11:39:24 +09:00
2011-01-07 15:17:03 +01:00
2011-02-09 09:49:59 -08:00
2010-07-15 01:28:51 -04:00
2010-07-15 18:13:48 -05:00
2010-05-27 23:05:26 -07:00
2011-01-20 00:46:20 +01:00
2010-12-20 14:54:27 -06: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 @novacc on twitter

To tame it for use in your own cloud: read http://nova.openstack.org/getting.started.html

To study its anatomy: read http://nova.openstack.org/architecture.html

To dissect it in detail: visit http://code.launchpad.net/nova

To taunt it with its weaknesses: use http://bugs.launchpad.net/nova

To watch it: http://hudson.openstack.org

To hack at it: read HACKING

To laugh at its PEP8 problems: http://hudson.openstack.org/job/nova-pep8/violations

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

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