5080e45fd2
A new BarbicanClient tripleo service provides a means of configuring the barbican Key Manager settings for cinder, glance and nova services running at an edge site. This is necessary because the BarbicanApi tripleo service is only capable of configuring the Key Manager settings for services running in the control plane. For cinder, the BarbicanClient ensures the KeyManager settings are available to the cinder-volume and cinder-backup services. This is necessary because the Key Manager setttings are traditionally associated with the cinder-api service, but cinder-api is not deployed at the edge. Closes-Bug: #1886070 Change-Id: I17d6c3a3af5b192b77d264ff3e94e64ef6064c77
14 lines
568 B
YAML
14 lines
568 B
YAML
---
|
|
features:
|
|
- |
|
|
Add new BarbicanClient tripleo service for configuring DCN/Edge nodes
|
|
to access a barbican service running in the control plane. The client
|
|
service is disabled by default, and can be enabled by including the
|
|
environments/services/barbican-edge.yaml environment file when deploying
|
|
a DCN/Edge stack.
|
|
fixes:
|
|
- |
|
|
Ensure the barbican Key Manager settings are configured on DCN/Edge nodes
|
|
when the barbican service is deployed in the control plane. See `bug 1886070
|
|
<https://bugs.launchpad.net/tripleo/+bug/1886070>`_.
|