ad6654eaa7
Now that we have added the field for persisting the disk alloc ratio, we can have the ResouceTracker persisting it by adding it to the local ComputeNode object which is persisted by calling the _update() method. It will then send by default 0.0 unless the operator explicitely specified an allocation ratio in the compute nova.conf. Thanks to the ComputeNode object hydratation on the scheduler side, the facade will make sure that if a default 0.0 is provided by either a compute node or by the scheduler's nova.conf, it will actually get the original allocation ratios (ie. 1.0 for disk) Since the Scheduler reads the same RT opt but goes thru the ComputeNode object, it will also get the Facade returning 1.0 unless the operator explicitely provided other ratios for the scheduler's nova.conf Amending the release note now that the behaviour is changing. DocImpact Disk alloc ratio is now per computenode UpgradeImpact Change-Id: Ief6fa32429d58b80e70029ed67c7f42e0bdc986d Implements: blueprint disk-allocation-ratio-to-rt |
||
---|---|---|
api-guide/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
nova | ||
plugins/xenserver | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bandit.yaml | ||
openstack-common.conf | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-py3.txt | ||
tox.ini |
README.rst
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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 wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast