OpenStack Compute (Nova)
Go to file
Balazs Gibizer 042bc07fd8 Test alloc_cands with indirectly sharing RPs
There are two new test cases proposed in this patch about shared RPs.
The generic setup in both cases are the following:

       CN1 (VCPU, MEMORY_MB)
     /      \
    /agg1    \agg2
   /          \
  SS1 (      SS2 (
   DISK_GB)   IPV4_ADDRESS
              SRIOV_NET_VF)

In the first case we only request resources provided by SS1 and SS2
but not CN1. In the second case we also request resources from CN1
besides requesting resources from SS1 and SS2.

The first case had been broken before nested providers are supported.
But this is fixed now thanks to the following commit, which enables
getting nested providers as well as sharing providers.
patch: https://review.openstack.org/#/c/567508/
commit: 068c56f55d

Closes-Bug: #1732731
Change-Id: Iaf7993773b8f1f5cf3cb83c161b4c88d9368297b
Co-Authored-By: Tetsuro Nakamura <nakamura.tetsuro@lab.ntt.co.jp>
2018-06-25 10:41:35 +00:00
api-guide/source Enhance api-guide general info some updates 2018-06-05 16:54:18 +08:00
api-ref/source Fix bug to api-ref 2018-06-22 12:05:26 +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 Fix nits from change Ia7cf4414feb335b3c2e863b4c8b4ff559b275c34 2018-06-21 17:43:05 -05: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 Test alloc_cands with indirectly sharing RPs 2018-06-25 10:41:35 +00: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 "libvirt: Log breadcrumb for known encryption bug" 2018-06-22 21:41:15 +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 Merge "Use oslo.messaging per-call monitoring" 2018-06-14 21:55:37 +00:00
requirements.txt Fix retrying lower bound in requirements.txt 2018-06-16 08:45:13 -04: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: