Eric Fried
9519601401
Change the Adapter loading for glance to use the auth from the user context instead of exposing and requiring it in the conf. With this change, it is possible to leave the [glance] conf section empty and still be able to discover the image API endpoint from the service catalog. Note that, when we do this, we often end up with the user auth being a _ContextAuthPlugin, which doesn't conform to the characteristics of keystoneauth1.identity.base.BaseIdentityPlugin as augmented in keystoneauth1 3.1.0. This requires a series of workarounds until bug 1709118 is fixed. These, along with workarounds for bugs 1707993 and 1707995, are subsumed with this change set in a (hopefully temporary) helper method nova.utils.get_endpoint. This lays the foundation for other services that should use user context for authentication - those via which Nova is acting on behalf of the user, i.e. cinder, keystone, and (sometimes) neutron[1]. (Services such as placement and ironic (and sometimes neutron) should continue to use admin auth context loaded from the conf.) [1] https://github.com/openstack/nova/blob/bb4faf40dfb02237af119646a5ebd960b072b31e/nova/network/neutronv2/api.py#L149-L160 Co-Authored-By: Eric Fried <efried@us.ibm.com> Partial-Implements: bp use-ksa-adapter-for-endpoints Change-Id: I4e755b9c66ec8bc3af0393e81cffd91c56064717
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/badges/nova.svg
:target: https://governance.openstack.org/reference/tags/index.html
.. Change things from this point on
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:
- `Compute API Guide <https://developer.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://developer.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
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:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
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:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
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:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/