Rely on barbican to manage barbican keys association of cinder-volume and cinder-backup services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
The bug is in continuation of issue seen at https:/
cinder backup service assumes that keyring for ceph for volume operation is present on node running cinder backup service instance. It is an implicit assumption and expected to be
fullfilled by cloud deployer. We can break this hard coupling in two ways:
1. [Medium term] Pass the keyring over the wire as part of response of initialize_
2. [short term] Relying on barbican to manage barbican keys association of cinder-volume and cinder-backup services. Cons: cinder will have dependency on barbican
This defect is to address the coupling aspect in long term i.e. option (2).
Related defect:
https:/
https:/
tags: | added: backup ceph rbd |