OpenStack Compute (Nova)
Go to file
Matt Riedemann 24fa4a5e20 libvirt: generalize rbd volume fallback removal statement
The warning being modified here was added in Pike:

  I6fc7108817fcd9df4a342c9dabbf14ab7911d06a

And then updated to say we would remove the fallback in
Queens:

  I006f41383dcef68d63a646665a56cbd4c3f93c4b

And here we're long past Queens and still have this old
warning with no immediate plans to do data migrations to
drop the fallback code, so this change simply makes the
warning message more generic.

Change-Id: Icdc02d0bbd023e916bd39945fe7afc52b7a3942c
2018-12-21 17:07:49 -05:00
api-guide/source Fix server query examples 2018-11-19 23:22:39 +00:00
api-ref/source Merge "api-ref: sort parameters for limits, quotas and quota classes" 2018-12-17 16:36:11 +00:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Merge "Fix destination_type attribute in the bdm_v2 documentation" 2018-12-21 11:52:22 +00:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Merge "Remove placement perf check" 2018-12-08 04:56:56 +00:00
nova libvirt: generalize rbd volume fallback removal statement 2018-12-21 17:07:49 -05:00
playbooks/legacy Remove placement perf check 2018-11-30 15:12:48 +00:00
releasenotes Merge "Address nits on I1f1fa1d0f79bec5a4101e03bc2d43ba581dd35a0" 2018-12-19 17:27:23 +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 Remove Placement API reference 2018-11-28 03:38:41 +00: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 irrelevant-files for grenade-py3 jobs" 2018-12-21 11:52:05 +00: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
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Add a hacking rule for deprecated assertion methods 2018-10-25 11:49:10 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt Merge "Migrate upgrade checks to oslo.upgradecheck" 2018-12-17 23:23:17 +00: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
requirements.txt Merge "Migrate upgrade checks to oslo.upgradecheck" 2018-12-17 23:23:17 +00:00
setup.cfg Update mailinglist from dev to discuss 2018-12-05 09:44:35 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Fix ironic client ironic_url deprecation warning 2018-10-24 17:59:10 +02:00
tox.ini Merge "Add python 3.7 unit and functional tox jobs" 2018-12-17 16:36:04 +00:00

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: