Bug 2173529

Summary: rbd kernel module : redundant subsection and must do tweak in sequencing of steps
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: DocumentationAssignee: Anjana Suparna Sriram <asriram>
Documentation sub component: Block Device Guide QA Contact: Aditya Ramteke <aramteke>
Status: NEW --- Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 5.3   
Target Milestone: ---   
Target Release: 6.1z2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Vasishta 2023-02-27 08:27:00 UTC 
Describe the issue:
In chapter The rbd kernel module
1) the subsection "Getting a list of images" doesn't make much sense as  there is no compulsion in functionality to fetch the list, user can skip listing images if user knows which image is to be worked on.
This subsection can be merged with its below subsection as a step or note asking user to refer to the list of already created images t choose the image which is to be mapped.

2) In subsection Mapping a block device,
we can tweak step 2 to depict that step 1 and 2 are explaining same operation for two different scenarios.

3) Prerequisites of "Unmapping a block device" can be tweaked to make it more specific saying "An image that has been mapped already.

4) In Unmapping a block device, we can add a line to ask users to obtain the device specification of the device that has been mapped.
device specification can be obtained bu checking rbd device list. (explained in 1 subsection above in the document)
Describe the task you were trying to accomplish:

Product Version:
5.3

Environment Details:
NA
Any other versions of this document that also needs this update:
YEs, (IBM/RH counterpart, 4.x, 6.x
Additional information: