0a8f019be0
Provide a new method: nova.utils.get_ksa_adapter(service_type, ks_auth=None, ks_session=None, min_version=None, max_version=None)) ...to configure a keystoneauth1 Adapter for a service. The Adapter, and its component keystoneauth1 artifacts not passed into the method, are loaded based on options in the conf group corresponding to the specified service_type. The ultimate goal is to replace the various disparate mechanisms used by different services to do endpoint URL and version discovery. In Queens, the original mechanisms will still take precedence, but (other than [glance]api_servers - see the spec) will be deprecated. In Rocky, the deprecated options will be removed. This change incorporates the above utility into endpoint discovery for glance and ironic. Future change sets will do the same for other services (cinder, neutron, placement). Change-Id: If625411f40be0ba642baeb02950f568f43673655 Partial-Implements: bp use-ksa-adapter-for-endpoints Closes-Bug: #1707860 |
||
---|---|---|
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 | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tests-functional-py3.txt | ||
tests-py3.txt | ||
tox.ini |
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: