Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1687889

Summary: [DOC] Notes for 'osd_scenario: non-collocated' is confusing
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Karun Josy <kjosy>
Component: DocumentationAssignee: Karen Norteman <knortema>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: medium    
Version: 3.2CC: agunn, asriram, kdreyer, kjosy, knortema, mmurthy, vereddy
Target Milestone: z4   
Target Release: 3.3   
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: 2020-06-11 12:11:46 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:    
Bug Blocks: 1809203    

Description Karun Josy 2019-03-12 14:54:58 UTC
Description of problem:

In the Container installation guide [1], under Section 1.2, in table 1.1 notes of osd_scenario - non collocated is bit confusing.
It says :
"ceph-ansible expects the variables `devices` and `dedicated_devices` to match" 

From initial impression it seems the path/partition specified under `devices` and `dedicated_devices` should be same, which is entirely opposite of the non-collocated feature. 

Can we change it to :
"ceph-ansible expects the number of variables in `devices` and `dedicated_devices` to match" 


[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/container_guide/#installing-a-red-hat-ceph-storage-cluster-in-containers

Comment 1 Giridhar Ramaraju 2019-08-05 13:09:35 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 2 Giridhar Ramaraju 2019-08-05 13:10:49 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri