OpenStack Compute (Nova)
Go to file
Matt Riedemann 5fe80b6339 (Re)start caching scheduler after starting computes in tests
This moves the scheduler restart logic from the heal_allocations
tests into a more generic location (like restart_compute_service)
so that we can re-use it in other functional tests that rely on
the caching scheduler. There are a couple of other tests that don't
need to restart the scheduler if we just move the start of the
scheduler to after we start the computes.

Change-Id: I7720fe4a3a0e537b7b356947317766597d4b47cf
Related-Bug: #1781648
2018-08-29 13:16:09 -04:00
api-guide/source Update api-guide and api-ref to be clear about forced-down 2018-08-17 01:41:31 +00:00
api-ref/source Merge "Making consistent used of GiB and MiB in API ref" 2018-08-22 04:03:01 +00:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Skip test_resize_server_revert_with_volume_attached in nova-lvm 2018-07-19 12:22:18 -04:00
doc Fix a broken conf file description in networking doc 2018-08-29 15:46:35 +09:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Add placement perf info gathering hook to end of nova-next 2018-08-14 15:42:08 +01:00
nova (Re)start caching scheduler after starting computes in tests 2018-08-29 13:16:09 -04:00
placement-api-ref Merge "Document no content on POST /reshaper 204" 2018-08-29 09:22:16 +00:00
playbooks/legacy Add placement perf info gathering hook to end of nova-next 2018-08-14 15:42:08 +01:00
releasenotes Merge "[placement] Add /reshaper handler for POST" 2018-08-29 09:22:10 +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 Merge "Add tempest-slow job to run the tempest slow tests" 2018-08-08 23:57:20 +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 Revert "Don't use '_TransactionContextManager._async'" 2018-08-28 17:18:51 +01:00
requirements.txt Revert "Don't use '_TransactionContextManager._async'" 2018-08-28 17:18:51 +01:00
setup.cfg Remove ChanceScheduler 2018-08-20 15:56:13 +01: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 Remove blacklisted py3 xen tests 2018-08-14 16:34:19 +00: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: