openstack
/
cinder-specs
Code Issues Proposed changes

Update patch set 2 

Patch Set 2:

(1 comment)

Patch-set: 2
Attention: {"person_ident":"Gerrit User 4523 \u003c4523@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_597\u003e replied on the change"}
This commit is contained in:
Gerrit User 597 2024-02-19 22:01:20 +00:00 committed by Gerrit Code Review
parent 6b4020ac23
commit 985cb1d0eb
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
0cfece2ed6af598b97959ae23024344f4817809f
View File

@ -85,6 +85,24 @@
"revId": "0cfece2ed6af598b97959ae23024344f4817809f",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": false,
"key": {
"uuid": "91ba9d12_7f1747cc",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 2
},
"lineNbr": 0,
"author": {
"id": 597
},
"writtenOn": "2024-02-19T22:01:20Z",
"side": 1,
"message": "I think that oddly enough, everything should work. Every backup is assigned one static key. And the management of these keys is placed on sysadmins. As long as the export copies the encrypted data without damaging it to the new place, it should be possible to restore it if the administrator preserved the key. Just another reason allow more keys than one: the backup could be imported into a cloud that already has encrypted backups of its own.",
"parentUuid": "e1b06b79_f897a297",
"revId": "0cfece2ed6af598b97959ae23024344f4817809f",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {