openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
52,883 Commits 9 Branches 82 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Matt Riedemann 3c50711249 Add docs for (initial) allocation ratio configuration 
This adds a new section to the admin scheduler configuration
docs devoted to allocation ratios to call out the differences
between the override config options and the initial ratio
options, and how they interplay with the resource provider
inventory allocation ratio override that can be performed
via the placement REST API directly.

This moves the note about bug 1804125 into the new section
and also links to the docs from the initial allocation ratio
config option help text.

Part of blueprint initial-allocation-ratios
Related-Bug: #1804125

Change-Id: I7d8e822cd40dccaf5244e2cd95fa1af43fa9ed87
 		2018-12-05 11:36:29 -05:00
api-guide/source Fix server query examples 2018-11-19 23:22:39 +00:00
api-ref/source Merge "api-ref: Add a description about sort order" 2018-11-12 06:50:27 +00:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Add docs for (initial) allocation ratio configuration 2018-12-05 11:36:29 -05:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Add volume-backed evacuate test 2018-10-25 16:15:56 -04:00
nova Add docs for (initial) allocation ratio configuration 2018-12-05 11:36:29 -05:00
placement-api-ref Merge "Document no content on POST /reshaper 204" 2018-08-29 09:22:16 +00:00
playbooks/legacy Add post-test hook for testing evacuate 2018-10-25 16:15:56 -04:00
releasenotes Add compute_node ratio online data migration script 2018-12-05 11:36:23 -05: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 Add post-test hook for testing evacuate 2018-10-25 16:15:56 -04: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
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 Use SleepFixture instead of mocking _ThreadingEvent.wait 2018-11-08 16:50:39 -05:00
requirements.txt Use SleepFixture instead of mocking _ThreadingEvent.wait 2018-11-08 16:50:39 -05:00
setup.cfg Remove the CachingScheduler 2018-10-18 17:55:36 -04: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 tox: Stop build *all* docs in 'docs' 2018-10-26 18:00:53 +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: