openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
55,779 Commits 9 Branches 82 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Balazs Gibizer 38a214466f Use admin neutron client to gather port resource requests 
The network_api get_requested_resource_for_instance() creates a neutron
client with the current request context and uses the client to query
neutron ports. Neutron does not return the resource_request of the
neutron port if it is queried by a non-admin. So if the request context
was a non admin context nova thought that none of the ports have resource
requests.

This patch ensures that an admin client is used to query the ports.

Change-Id: I1178fb77a74010c3b9f51eea22c7e7576b600015
Closes-Bug: #1849695
 		2019-11-06 15:39:54 -05:00
api-guide/source Enable evacuation with qos ports 2019-10-25 16:14:22 +00:00
api-ref/source Add image caching API for aggregates 2019-10-15 21:22:31 -04:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Revert "openstack server create" to "nova boot" in nova docs 2019-11-06 16:25:52 +00:00
etc/nova Deprecate [api]auth_strategy and noauth2 2019-10-09 15:16:07 -05:00
gate Remove redundant call to get/create default security group 2019-10-14 18:54:43 +00:00
nova Use admin neutron client to gather port resource requests 2019-11-06 15:39:54 -05:00
playbooks Merge "Convert nova-lvm job to zuul v3" 2019-09-04 20:08:05 +00:00
releasenotes Merge "Enable evacuation with qos ports" 2019-11-04 23:00:36 +00:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00: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 "Switch to devstack-plugin-ceph-tempest-py3 for ceph" 2019-11-01 20:56:49 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Remove descriptions of nonexistent hacking rules 2019-08-26 14:55:51 +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 Update api-ref location 2019-07-22 19:17:28 +02:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Added openssh-client into bindep 2019-10-23 07:21:23 +00:00
lower-constraints.txt Merge "Use os-brick locking for volume attach and detach" 2019-10-02 20:26:00 +00:00
requirements.txt Merge "Use os-brick locking for volume attach and detach" 2019-10-02 20:26:00 +00:00
setup.cfg setup.cfg: Cleanup 2019-10-11 19:00:56 +01:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Remove an unused file and a related description 2019-09-13 10:33:32 +09:00
tox.ini Stop building docs with (test-)requirements.txt 2019-10-25 12:48:31 -04: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: