Go to file

Brian Waldon 117ead3576 Add policy checks to Compute.API

* Second step of blueprint interim-nova-authz-service
 * Adds policy.json to define policy
 * Add nova.policy.wrap_enforce decorator
 * wrap majority of compute api functions with wrap_enforce

Change-Id: If6702873db3249921f931a42e889ee7d0338e4b8

2012-01-12 10:36:34 -08:00

bin

nova-manage floating ip fixes

2012-01-10 16:51:06 -06:00

nova

Add policy checks to Compute.API

2012-01-12 10:36:34 -08:00

Imported Translations from Launchpad

2011-12-18 23:03:28 +00:00

.gitignore

Rename .nova-venv to .venv.

2011-12-08 15:17:51 -08:00

.gitreview

Add .gitreview config file for gerrit.

2011-10-24 15:07:19 -04:00

.mailmap

Remove 'location' from GlanceImageService

2012-01-11 13:36:23 -08:00

Authors

Tell users what is about to be installed via sudo

2012-01-05 16:08:04 +00:00

HACKING.rst

Update HACKING.rst.

2012-01-05 10:21:57 -06:00

LICENSE

initial commit

2010-05-27 23:05:26 -07:00

MANIFEST.in

Sanitize EC2 manifests and image tarballs

2011-12-13 16:00:41 +01:00

README.rst

Converted README to RST format.

2011-11-20 18:54:08 -05:00

README.rst

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