Add BarbicanClient service for configuring edge sites
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 commit 5080e45fd283c795f973c86719d1959948f642e3)
Reviewed: https:/ /review. opendev. org/742177 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=b5b2bb640b9 3001ffcfb2d09aa ee7d586604aa62
Committed: https:/
Submitter: Zuul
Branch: stable/ussuri
commit b5b2bb640b93001 ffcfb2d09aaee7d 586604aa62
Author: Alan Bishop <email address hidden>
Date: Fri Jul 10 06:35:11 2020 -0700
Add BarbicanClient service for configuring edge sites
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 2b77d264ff3e94e 64ef6064c77 5f973c86719d195 9948f642e3)
Change-Id: I17d6c3a3af5b19
(cherry picked from commit 5080e45fd283c79