OpenStack Compute (Nova)
Go to file
Chris Dent 623cd722e0 [placement] demonstrate part of bug 1778591 with a gabbi test
The test creates a resource provider with a small amount of VCPU
inventory. It then tries to allocate a large number VCPU via a new
consumer (and thus using consumer_generation of null).

This fails with a 409 because capacity is violated.

Then it queries to GET allocations on that consumer, to see if consumer
generation is available. It is not.

The it tries to allocate a smaller amount and though it might be
expected that the generation should still be null, it takes a 0
for the allocation to be accepted.

Once we decide what the right behavior is here, we can fix it.

Change-Id: I196834efc2cb6ece4204abbf8544c8f2621aaa36
Related-Bug: #1778591
2018-06-27 14:57:37 +01:00
api-guide/source Enhance api-guide general info some updates 2018-06-05 16:54:18 +08:00
api-ref/source Merge "api-ref: Fix parameters about trusted certificate IDs" 2018-06-26 12:37:42 +00:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Skip ServerShowV263Test.test_show_update_rebuild_list_server for cellsv1 2018-06-18 12:12:07 -04:00
doc Merge "Update links in README" 2018-06-26 12:37:49 +00:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Make nova-manage db purge take --all-cells 2018-03-08 09:26:49 -08:00
nova [placement] demonstrate part of bug 1778591 with a gabbi test 2018-06-27 14:57:37 +01:00
placement-api-ref/source Add a microversion for consumer generation support 2018-06-20 12:11:09 +01:00
playbooks/legacy Add PLACEMENT_DB_ENABLED=True to the nova-next job 2018-06-15 12:27:08 +00:00
releasenotes Merge "Make nova list and migration-list ignore down cells" 2018-06-26 05:07:38 +00:00
tools Remove deprecated monkey_patch config options 2018-05-16 11:40:41 -04: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 Merge "add lower-constraints job" 2018-05-15 01:12:25 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Removed unnecessary parantheses in yield statements 2018-03-07 16:44:36 +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 keystoneauth1 minimum to 3.9.0 2018-06-22 09:13:19 -05:00
requirements.txt Bump keystoneauth1 minimum to 3.9.0 2018-06-22 09:13:19 -05:00
setup.cfg Implement granular policy rules for placement 2018-05-17 11:12:16 -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
tests-py3.txt Remove mox in unit/virt/xenapi/test_vmops.py 2018-05-06 22:31:05 +00:00
tox.ini fix tox python3 overrides 2018-06-08 08:55:56 -05: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: