f14c16af82
When working on a fix for bug #1811870, it was noted that the check to ensure pinned instances do not overcommit was not pagesize aware. This means if an instance without hugepages boots on a host with a large number of hugepages allocated, it may not get all of the memory allocated to it. Put in concrete terms, consider a host with 1 NUMA cell, 2 CPUs, 1G of 4k pages, and a single 1G page. If you boot a first instance with 1 CPU, CPU pinning, 1G of RAM, and no specific page size, the instance should boot successfully. An attempt to boot a second instance with the same configuration should fail because there is only the single 1G page available, however, this is not currently the case. The reason this happens is because we currently have two tests: a first that checks total (not free!) host pages and a second that checks free memory but with no consideration for page size. The first check passes because we have 1G worth of 4K pages configured and the second check passes because we have the single 1G page. Close this gap. Change-Id: I74861a67827dda1ab2b8451967f5cf0ae93a4ad3 Signed-off-by: Stephen Finucane <sfinucan@redhat.com> Closes-Bug: #1811886 |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
playbooks | ||
releasenotes | ||
roles | ||
tools | ||
.coveragerc | ||
.git-blame-ignore-revs | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic.
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: