Go to file

Andrew Bogott e763ffe6ea Change the logic for deleting a record dns_domains.

Since keys are just the domain name, we need to be able
to reuse them.  That means we have to do a real record
deletion to free up namespace rather than just mark the
records as deleted.

For blueprint public-and-private-dns.

Change-Id: If47e961cf2cb977d297b506bd397f1a438499f18

2012-01-21 01:07:35 +00:00

doc

Adds extension documentation for some but not all extensions

2011-12-02 13:02:06 -06:00

nova

Change the logic for deleting a record dns_domains.

2012-01-21 01:07:35 +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

HACKING.rst

Update HACKING.rst.

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

LICENSE

initial commit

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

README.rst

Converted README to RST format.

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

setup.cfg

Remove remnants of babel i18n infrastructure

2011-12-06 11:31:02 +00:00

setup.py

Implements blueprint vnc-console-cleanup

2012-01-17 14:18:31 -08: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