82a94bbcec
- Share type extra-spec "encryption_support" should be set to "share_server". - Use encryption_key_ref from user provided share create API option - Create ACL for barbican user from current user context, so barbican user can fetch the secret from secret_ref in backend driver. - Create server_encryption_keys project level quota which helps to control the encrypted share servers. Such share servers do not support migration/unmanage etc. - Create application credentials for barbican user during share server creation and delete during share server deletion. partially-implements: blueprint share-encryption Change-Id: I9e3ff98e12027eaf75cdc5f6089a016c102315d3 Signed-off-by: Kiran Pawar <kinpaa@gmail.com>
23 lines
710 B
JSON
23 lines
710 B
JSON
{
|
|
"share": {
|
|
"description": "My custom share London",
|
|
"share_type": null,
|
|
"share_proto": "nfs",
|
|
"share_network_id": "713df749-aac0-4a54-af52-10f6c991e80c",
|
|
"share_group_id": null,
|
|
"name": "share_London",
|
|
"snapshot_id": null,
|
|
"is_public": true,
|
|
"size": 1,
|
|
"metadata": {
|
|
"project": "my_app",
|
|
"aim": "doc"
|
|
},
|
|
"scheduler_hints": {
|
|
"same_host": "d9c66489-cf02-4156-b0f2-527f3211b243,4ffee55f-ba98-42d2-a8ce-e7cecb169182",
|
|
"different_host": "903685eb-f242-4105-903d-4bef2db94be4"
|
|
},
|
|
"encryption_key_ref": "86babe9b-7277-4c3a-a081-6eb3eac9231d"
|
|
}
|
|
}
|