OpenStack Compute (Nova)
Go to file
Jay Pipes 4f9a7da581 update project/user for consumer in allocation
Adds code to the util.ensure_consumer() method that updates the
consumer's project and user foreign key identifiers when a user supplies
a different external project or user identifier in the paylod of PUT
/allocations/{consumer_uuid} or POST /allocations.

Change-Id: I9368ad2280551ffa9a011d3a30c4b45861305455
Closes-bug: #1779717
Related-Bug: #1781008
2018-07-10 16:05:38 +00:00
api-guide/source Enhance api-guide general info some updates 2018-06-05 16:54:18 +08:00
api-ref/source api-ref: Example verification for servers.inc 2018-07-09 14:47:46 +00:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Merge "Skip ServerShowV247Test.test_update_rebuild_list_server in nova-cells-v1 job" 2018-06-29 02:44:42 +00:00
doc Merge "Remove duplicate parameter in API sample documents" 2018-07-10 13:20:48 +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 update project/user for consumer in allocation 2018-07-10 16:05:38 +00:00
placement-api-ref/source Handle CannotDeleteParentResourceProvider to 409 Conflict 2018-06-27 13:28:46 +00:00
playbooks/legacy Add PLACEMENT_DB_ENABLED=True to the nova-next job 2018-06-15 12:27:08 +00:00
releasenotes Merge "Allow templated cell_mapping URLs" 2018-07-10 06:10:07 +00:00
tools trivial: Remove 'tools/releasenotes_tox.sh' 2018-06-28 15:06:46 +01: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 Use ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa in tree 2018-06-28 12:37:19 -04: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 Fix placement incompatible with webob 1.7 2018-06-29 16:55:03 +02:00
requirements.txt Fix placement incompatible with webob 1.7 2018-06-29 16:55:03 +02: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 tox: Document and dedupe mostly everything 2018-06-28 15:24:17 +01: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: