bbaded6cac
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 (cherry picked from commit5080e45fd2
) (cherry picked from commitb5b2bb640b
)
5 lines
250 B
YAML
5 lines
250 B
YAML
# A Heat environment file which can be used to configure services running at
|
|
# a DCN/Edge site to access Barbican in the control plane.
|
|
resource_registry:
|
|
OS::TripleO::Services::BarbicanClient: ../../deployment/barbican/barbican-client-puppet.yaml
|