122d4e0865
This modification adds an encryption key UUID field to the volume table, which is sufficient to make Cinder "aware" of encrypted volumes as designated by predefined volume types. Integration with a key manager is necessary to obtain an actual encryption key UUID (the current implementation generates a random UUID when an encrypted volumes is created). Cinder should *not* presume that it necessarily will have access to the key itself -- this decision depends upon the design, implementation, and policy for encrypted volumes. The key's UUID is stored in Cinder because it is metadata about the volume. Implements: blueprint encrypt-cinder-volumes Change-Id: I164290e761a9922919a70f22f99af70dac213b61 SecurityImpact |
||
|---|---|---|
| .. | ||
| rootwrap.d | ||
| api-paste.ini | ||
| cinder.conf.sample | ||
| logging_sample.conf | ||
| policy.json | ||
| rootwrap.conf | ||