![]() By design, nova.compute.provider_tree._Provider is intended to be accessed only through ProviderTree interfaces to ensure thread safety. However, certain ProviderTree methods were returning _Provider objects, allowing callers to think it was okay to access their internals directly. With this change, we truly hide _Provider behind ProviderTree. As long as callers are well-behaved (accessing only public methods of public classes), there is no longer any way to access _Provider internals. Summary of the changes: - ProviderTree.find is removed. - ProviderTree.new_root and .new_child now return the UUID of the newly-created _Provider, rather than the _Provider itself. (We return the UUID because it may have been generated; and there is currently no other way for the caller to discover it.) Note: It is possible that future changes will be necessary to provide (read-only) access to some _Provider attributes. No such accessors are implemented herein. Change-Id: If5eed34cb5a2cd94a6305a7626adfe7129119e44 blueprint: nested-resource-providers |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref/source | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-functional-py3.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: