8be8d02aa7
There were several things wrong with this doc since the migration in-tree in pike, which are handled here: - Updated options to use the current names. - Any mention of the periodic_task_interval option is removed since this doc is really about the FilterScheduler, and the periodic task interval is only used by the CachingScheduler to cache and refresh hosts, something the FilterScheduler doesn't do. The note about service_down_time is already covered in the help text for the periodic_task_interval option. - Removed a broken (and oddly placed) link to the block storage docs; it's unclear why the compute scheduler docs need to randomly link to the block storage docs for schedluing (maybe that was super legacy from the nova-volume days). - Fixed a broken link to the 'evacuate instances' docs. This change does not get into details for the individual filters or weighers, only the overview and filter scheduler description. Change-Id: Ie5bb9781e1997ad12521b5df5245a78b587a4a20 Closes-Bug: #1749235 |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref/source | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-py3.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: