Go to file
Maru Newby dad188ca07 Raise ApiError in response to InstanceTypeNotFound
* Updates methods in nova.compute.instance_types to catch
   InstanceTypeNotFound exceptions and re-raise them as ApiError.
   - Previously, the methods in instance_types were raising ApiError in
     response to DBError, but the underlying db calls have since been
     updated to detect empty results and throw more specific exceptions.
 * Updates get_instance_type_by_flavor_id to not try to catch DBError,
   as the underlying db call only ever raises FlavorNotFound.
   get_instance_type_by_flavor_id should not raise ApiError, as callers
   expect the FlavorNotFound exception and know how to handle it.
 * Fixes bug 872618

Change-Id: I8652f04889adb448017afd253ecdcc840fbb660f
2012-02-03 00:15:12 -08:00
2012-01-20 12:33:38 +00:00
2011-12-08 15:17:51 -08:00
2012-01-05 10:21:57 -06:00
2010-05-27 23:05:26 -07:00
2011-11-20 18:54: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 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