OpenStack Compute (Nova)
Go to file
Ryan Rossiter 7e435fa8f3 Removed enum duplication from nova.compute
There are many state constants held within nova.compute. Because these
now need to be used in versioned notifications, they were converted into
enums within nova.objects.fields. In order to prevent duplication, the
constants in nova.compute were converted over to use the enums created
for the notifications.

Also, because the comments in nova.compute.vm_states were not the best,
they were rearranged to more appropriately fit the lines they were
attempting to comment.

The object hash changes are ignored as it is only caused by the new
sentinel enum value _UNUSED which is not intended to be used.

Change-Id: I4c147a1a1145295b6ccfe9680706abe34cb35170
2016-09-02 07:30:44 +00:00
api-guide/source [api-guide]: Update reference links 2016-08-23 14:16:10 +07:00
api-ref/source Merge "Make api-ref bug link point to nova" 2016-08-31 14:28:46 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Add RC file for excluding tempest tests for LVM job 2016-05-17 10:25:45 -04:00
doc Documentation for the vendordata reboot. 2016-08-30 15:03:17 -04:00
etc/nova Remove namespace from nova-config-generator.conf 2016-07-28 18:14:12 -04:00
nova Removed enum duplication from nova.compute 2016-09-02 07:30:44 +00:00
plugins/xenserver plugins/xenserver: Resolve PEP8 issues 2016-08-15 18:11:49 +01:00
releasenotes Merge "Adds nova-policy-check cmd" 2016-09-01 17:56:56 +00:00
tools Remove locals() for formatting strings. 2016-08-22 17:32:38 +07:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Add policy sample generation 2016-06-28 20:52:44 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add initial framing of placement API 2016-07-29 10:31:36 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Remove hacking check [N347] for config options. 2016-08-11 14:23:21 +02:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst Refresh README and its docs links 2016-08-08 10:26:08 +01:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
requirements.txt Updated from global requirements 2016-08-25 09:28:26 +00:00 Add description on how to run ./ -8 2016-01-11 13:17:04 +00:00
setup.cfg Merge "Adds nova-policy-check cmd" 2016-09-01 17:56:56 +00:00 Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2016-08-29 16:51:55 +00:00
tests-py3.txt Remove nova/api/ 2016-08-16 09:52:29 +00:00
tox.ini Merge "List system dependencies for running common tests" 2016-08-30 12:59:30 +00:00


OpenStack Nova

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.

OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.


To learn how to use Nova's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs, please see:


To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

For information about the different compute (hypervisor) drivers supported by Nova, please read:

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:


For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.

Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.

Further developer focused documentation is available at: