Go to file

Mohammed Naser deea22a41d Expose a limited networks API for users

Currently, users do not have any way of knowing what networks
are available for use, and in some scenarios such as when a
user wants to add a fixed IP, they do not have access to the
network ID.

This exposes a limited amount of information through the
existing networks extension for users and fixes LP Bug #1003979

Change-Id: I14cc3a377ee0f031b4edaf7eeec3a6550a402b1a

2012-05-24 13:26:52 -04:00

bin

Finish quota refactor.

2012-05-23 10:17:41 -05:00

nova

Expose a limited networks API for users

2012-05-24 13:26:52 -04:00

.gitignore

Scope coverage report generation to nova module.

2012-04-24 07:58:25 -04:00

.gitreview

Add .gitreview config file for gerrit.

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

.mailmap

Merge "Fix Multi_Scheduler to process host capabilities"

2012-05-18 22:32:22 +00:00

Authors

fixed_ip_get_by_address read_deleted from context

2012-05-18 07:15:31 -07:00

HACKING.rst

Improved tools/hacking.py

2012-04-24 09:29:43 -07:00

LICENSE

initial commit

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

MANIFEST.in

Generate a Changelog for Nova

2012-05-04 10:17:36 -07: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