97096c8e4a
With the removal of the Core, Ram and Disk filters in change I8a0d332877fbb9794700081e7954f2501b7e7c09, there's now only a single caller for the 'estimate_instance_overhead' function. This call results in the 'memory_mb_used', 'local_gb_used', 'vcpus_used', 'free_ram_mb' and 'free_disk_gb' fields of a compute nodes 'ComputeNode' object being modified when calculating usage as part of the resource tracker to include driver-specific overhead. However, these fields are no longer used for for anything except logging and the 'os-hypervisors' API. Since overhead is not reflected in placement (and therefore the scheduler), reporting them as part of the various usage values for both logging and that API is actually a bit of a lie and is likely to cause confusion among users. Remove the whole thing and make our logs and the 'os-hypervisors' API better match what's stored in placement. Change-Id: I033e8269194de54432079cbc970431e3dcea7ce5 Signed-off-by: Stephen Finucane <sfinucan@redhat.com> |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
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: