openstack
/
manila-specs
Code Issues Proposed changes

Update patch set 4 

Patch Set 4:

(3 comments)

Patch-set: 4
Attention: {"person_ident":"Gerrit User 32919 \u003c32919@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_36178\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 36178 \u003c36178@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_36178\u003e replied on the change"}
This commit is contained in:
Gerrit User 36178 2023-12-07 14:50:36 +00:00 committed by Gerrit Code Review
parent 7753eddbbc
commit 9848d39918
1 changed files with 51 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
7e375d234c48fb3e6c33584ea12452ec0e29ee60
View File

@ -17,6 +17,40 @@
"revId": "7e375d234c48fb3e6c33584ea12452ec0e29ee60",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "6f3cec58_13b8c17c",
"filename": "specs/caracal/share_encryption.rst",
"patchSetId": 4
},
"lineNbr": 53,
"author": {
"id": 36178
},
"writtenOn": "2023-12-07T14:50:36Z",
"side": 1,
"message": "What call would be made if the share created on a storage server has already a mechanism of encrypting it. Do you provide one more option to overwrite the settings whatever already configured at the backend.",
"revId": "7e375d234c48fb3e6c33584ea12452ec0e29ee60",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "60369c15_c25f3d4c",
"filename": "specs/caracal/share_encryption.rst",
"patchSetId": 4
},
"lineNbr": 82,
"author": {
"id": 36178
},
"writtenOn": "2023-12-07T14:50:36Z",
"side": 1,
"message": "Different vendors handle encryption differently. For instance, NetApp can handle encryption at aggregate level (pools in Manila), volume level (shares in manila). If user has enabled encryption already at storage server (vserver in NetApp) level, how would that be impacted if user tries to modify that via openstack level. Do we assume that, if the share is already encrypted by the vendor in his own way, we\u0027ll not overwrite that with the settings we have in Barbican ?",
"revId": "7e375d234c48fb3e6c33584ea12452ec0e29ee60",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
@ -225,6 +259,23 @@
"revId": "7e375d234c48fb3e6c33584ea12452ec0e29ee60",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "65aca70d_df25af72",
"filename": "specs/caracal/share_encryption.rst",
"patchSetId": 4
},
"lineNbr": 306,
"author": {
"id": 36178
},
"writtenOn": "2023-12-07T14:50:36Z",
"side": 1,
"message": "How do we control this when user goes for DHSS\u003dTrue option. Do you expect us to enable the encryption settings at storage server (vserver) level. If that happens, user need not to do any extra steps to encrypt all the shares created further, inside this DHSS server, as encryption can be made just automatic for all of them whenever created.",
"revId": "7e375d234c48fb3e6c33584ea12452ec0e29ee60",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {