openstack
/
nova-specs
Code Issues Proposed changes
OpenStack Compute (Nova) Specifications
159 Commits 1 Branch 0 Tags 59 MiB
Python 90.3%
Shell 9.7%
Go to file
Daniel P. Berrange df28970637 Virt driver guest NUMA node placement & topology 
This feature aims to enhance the libvirt driver to be able todo
intelligent NUMA node placement for guests. This will increase
the effective utilization of compute resources and decrease
latency by avoiding cross-node memory accesses by guests.

Change-Id: I70fab6d7187ea7be879f9bcfe23809a2380ffa77
 		2014-06-24 18:32:21 -07:00
doc/source Allow DB migration backports to Icehouse 2014-03-31 14:01:23 -04:00
specs Virt driver guest NUMA node placement & topology 2014-06-24 18:32:21 -07:00
tests Trailing white space check. 2014-05-22 09:36:42 -05:00
.gitignore Add .testrepository to gitignore 2014-04-04 19:07:21 +02:00
.gitreview Added .gitreview 2014-03-14 23:09:48 +00:00
.testr.conf Add unit test to make sure all sections are present 2014-03-31 12:03:41 -04:00
LICENSE Switch license to CC-BY 3.0. 2014-03-24 16:28:41 -04:00
README.rst Note HTML docs result from running 'tox'. 2014-04-02 10:02:07 -04:00
requirements.txt Add unit test to make sure all sections are present 2014-03-31 12:03:41 -04:00
setup.cfg Make sphinxbuild fail on formatting errors 2014-03-31 11:56:45 -04:00
setup.py Make nova-specs an oslosphinx project 2014-03-24 16:28:41 -04:00
tox.ini Relax min tox from 1.6 to 1.4 2014-06-03 15:04:29 +01:00

README.rst

OpenStack Nova Specifications

This git repository is used to hold approved design specifications for additions to the Nova project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.

The layout of this repository is:

specs/<release>/

You can find an example spec in doc/source/specs/template.rst.

Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.

Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.

Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

http://blueprints.launchpad.net/nova

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see:

https://wiki.openstack.org/wiki/Gerrit_Workflow

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.