OpenStack Compute (Nova)
Go to file
Matt Riedemann f8c0c4671c Document unset/reset wrinkle for *_allocation_ratio options
This is a follow up to I43a23a3290db0c835fed01b8d6a38962dc61adce
which makes the cpu/disk/ram_allocation_ratio config "sticky" in
that once set to a non-default value, it is not possible to reset
back to the default behavior (when config is 0.0) on an existing
compute node record by unsetting the option from nova.conf. To
reset back to the defaults, the non-0.0 default would have to be
explicitly put into config, so cpu_allocation_ratio=16.0 for example.

Alternatively operators could delete the nova-compute service
record via the DELETE /os-services/{service_id} REST API and
restart the nova-compute service to get a new compute_nodes record,
but that workaround is messy and left undocumented in config.

Change-Id: I908615d82ead0f70f8e6d2d78d5dcaed8431084d
Related-Bug: #1789654
(cherry picked from commit c45adaca5d)
(cherry picked from commit a039f83977)
2019-03-25 05:42:35 +00:00
api-guide/source api-ref: Add X-Openstack-Request-Id description 2017-07-10 14:03:14 +00:00
api-ref/source Block deleting compute services which are hosting instances 2018-07-05 16:24:32 -04:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Skip test_rebuild_server_in_error_state for cells v1 2017-08-22 18:42:17 +00:00
doc Merge "Note the aggregate allocation ratio restriction in scheduler docs" into stable/pike 2019-03-13 14:57:45 +00:00
etc/nova rootwrap.d cleanup mislabeled files 2017-08-01 16:09:18 +10:00
gate move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
nova Document unset/reset wrinkle for *_allocation_ratio options 2019-03-25 05:42:35 +00:00
placement-api-ref/source [placement] Add api-ref for usages 2017-08-09 15:54:48 +00:00
playbooks/legacy/nova-live-migration Migrate tempest-dsvm-multinode-live-migration job in-tree 2018-05-10 11:14:03 -04:00
plugins/xenserver XenAPI Remove useless files when use os-xenapi lib 2017-01-10 18:06:17 -08:00
releasenotes Merge "Fix bug case by none token context" into stable/pike 2019-03-22 19:05:28 +00:00
tools tools/xenserver: Remove 'cleanup_sm_locks' 2017-08-07 12:26:53 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Backport tox.ini to switch to stestr 2018-07-05 16:28:04 -04:00
.gitreview Update .gitreview for stable/pike 2017-08-11 12:29:20 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Backport tox.ini to switch to stestr 2018-07-05 16:28:04 -04:00
.zuul.yaml Migrate nova v2.0 legacy job to zuulv3 2019-01-25 08:37:07 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Enable global hacking checks and removed local checks 2017-02-10 15:09:37 +01:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst doc: Rework README to reflect new doc URLs 2017-08-03 16:06:08 -04:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Update bindep.txt for doc builds 2017-11-21 20:09:12 +00:00
requirements.txt Updated from global requirements 2017-08-07 00:49:24 +00:00
setup.cfg Using plain routes for the microversions test 2017-07-23 22:43:53 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Backport tox.ini to switch to stestr 2018-07-05 16:28:04 -04:00
tests-functional-py3.txt Remove invalid URL in gabbi tests 2017-01-17 21:10:45 +00:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini tox: Don't write byte code (maybe) 2019-02-22 15:43:18 +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: