Bug 1954403

Summary: [Docs] [RBD] client-side LUKS encryption built into librbd
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Harish Munjulur <hmunjulu>
Component: DocumentationAssignee: Amrita <asakthiv>
Status: CLOSED CURRENTRELEASE QA Contact: Veera Raghava Reddy <vereddy>
Severity: high Docs Contact: Karen Norteman <knortema>
Priority: unspecified    
Version: 5.0CC: asakthiv, asriram, hyelloji, idryomov, kdreyer, knortema, vereddy
Target Milestone: ---   
Target Release: 5.0z1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-16 13:40:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1917598    
Bug Blocks:    

Description Harish Munjulur 2021-04-28 06:12:02 UTC
Documentation of Luks Encryption

upstream doc: https://docs.ceph.com/en/latest/rbd/rbd-encryption/

Comment 1 Aron Gunn 2021-06-23 17:01:34 UTC
*** Bug 1954402 has been marked as a duplicate of this bug. ***

Comment 8 Harish Munjulur 2021-08-09 18:23:27 UTC
Hi Amrita, 

Syntax

Existing: rbd encryption format POOL_NAME/LUKS_IMAGE luks2 passphrase.txt
Required: rbd encryption format POOL_NAME/LUKS_IMAGE luks1|luks2 passphrase.txt (we should include the options either in the syntax or make it general like supported encryption format and mention the allowed formats)

Syntax

rbd device map -t nbd -o encryption-format=luks2,encryption-passphrase-file=passphrase.txt POOL_NAME/LUKS_IMAGE

Can we include both encryption-format to choose "luks2|luks1" in the syntax.

Comment 9 Veera Raghava Reddy 2021-08-10 11:47:09 UTC
Hi Amrita,
Please check comment https://bugzilla.redhat.com/show_bug.cgi?id=1954403#c8

Comment 14 Harish Munjulur 2021-08-11 17:38:27 UTC
looks good.