openstack
/
nova-specs
Code Issues Proposed changes

Merge "Remove barbican from scope of ksa adapter work"

This commit is contained in:
Zuul 2017-10-27 14:23:51 +00:00 committed by Gerrit Code Review
parent 1c5c57f846 649f13c8bf
commit 6d97a81253
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
specs/queens/approved/use-ksa-adapter-for-endpoints.rst
View File

@ -16,8 +16,7 @@ there is a drive to use these mechanisms consistently any time endpoint
discovery is needed. This effort aims to take advantage of Adapters to
make endpoint discovery consistent across Nova for the various services
it uses: identity (keystone), image (glance), block-storage (cinder),
network (neutron), baremetal (ironic), key-manager (barbican), and
placement.
network (neutron), baremetal (ironic), and placement.
.. note:: This is an evolving continuation of the effort begun via
`blueprint use-service-catalog-for-endpoints`_.
@ -136,6 +135,16 @@ keystone v3 version of interface. The config should accept both, but
the documentation attached to the conf options as exposed by
keystoneauth1 shows examples using ``public``.)
A Note About Barbican
---------------------
The Barbican configuration options are both supplied by and used from within
the castellan library. It may be possible to override/deprecate those options
from Nova to shoehorn them into conforming to the standard of the remainder of
this spec. However, the right way to make this happen is to have the castellan
project itself move toward common keystoneauth configuration. There will
therefore be no effort in the scope of this specification to "fix" the
``[barbican]`` or ``[key_manager]`` conf sections.
Alternatives
------------