| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
When Barbican is the encryption key_manager backend, any encryption keys |
| 5 |
associated with the legacy ConfKeyManager will be automatically migrated |
| 6 |
to Barbican. All database references to the ConfKeyManager's all-zeros key |
| 7 |
ID will be updated with a Barbican key ID. The encryption keys do not |
| 8 |
change. Only the encryption key ID changes. |
| 9 |
|
| 10 |
Key migration is initiated on service startup, and entries in the |
| 11 |
cinder-volume log will indicate the migration status. Log entries will |
| 12 |
indicate when a volume's encryption key ID has been migrated to Barbican, |
| 13 |
and a summary log message will indicate when key migration has finished. |