OpenStack Compute (Nova)
Go to file
Matt Riedemann 4e3616b562 No longer call _normalize_inventory_from_cn_obj from upt flow
With change I72c83a95dabd581998470edb9543079acb6536a5 we no
longer have a need to call _normalize_inventory_from_cn_obj for
in-tree drivers that implement the update_provider_tree() interface.
That change also documented the expectation on the upt interface
that virt drivers should report allocation ratios and reserved
amounts if necessary, like the libvirt driver does with config
option values.

This change removes the call to _normalize_inventory_from_cn_obj
from the ResourceTracker when the virt driver implements the
update_provider_tree() method.

Change-Id: Ib3591f583453d98245382be0f7a04b6195d67106
Related-Bug: #1799727
2018-10-29 12:55:03 -04:00
api-guide/source Rename "polling_changes-since_parameter.rst" 2018-09-23 06:42:34 -04:00
api-ref/source Merge "Add restrictions on updated_at when getting instance action records" 2018-10-29 04:33:15 +00:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Provide allocation_ratio/reserved amounts from update_provider_tree() 2018-10-29 12:27:31 -04:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Add volume-backed evacuate test 2018-10-25 16:15:56 -04:00
nova No longer call _normalize_inventory_from_cn_obj from upt flow 2018-10-29 12:55:03 -04:00
placement-api-ref Merge "Document no content on POST /reshaper 204" 2018-08-29 09:22:16 +00:00
playbooks/legacy Add post-test hook for testing evacuate 2018-10-25 16:15:56 -04:00
releasenotes Merge "Fix os-simple-tenant-usage result order" 2018-10-27 08:57:52 +00:00
tools Make Xen code py3-compatible 2018-08-10 20:04:19 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Implement granular policy rules for placement 2018-05-17 11:12:16 -04: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
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Add post-test hook for testing evacuate 2018-10-25 16:15:56 -04:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Add a hacking rule for deprecated assertion methods 2018-10-25 11:49:10 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Docs: modernise links 2018-03-24 20:27:11 +08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
lower-constraints.txt Bump os-brick version to 2.6.1 2018-10-16 20:29:51 +00:00
requirements.txt Bump os-brick version to 2.6.1 2018-10-16 20:29:51 +00:00
setup.cfg Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Cleanup ugly stub in TestLocalDeleteAllocations 2018-05-16 09:23:55 -04:00
tox.ini Fix missing specifying doctrees directory 2018-09-20 20:48:35 +09:00

README.rst

Team and repository tags

image

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, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

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

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

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

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:

Developers

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:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: