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 1705214

Summary: [DOCS] Need to update HW guide to reflect minimum of 50GB recommended for disk space for MON
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: DocumentationAssignee: Karen Norteman <knortema>
Status: CLOSED CURRENTRELEASE QA Contact: Tejas <tchandra>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2CC: agunn, asriram, kdreyer, tchandra
Target Milestone: z5   
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: 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:    
Bug Blocks: 1809203    

Description Mike Hackett 2019-05-01 18:41:59 UTC
Description of problem:
Currently the HW guide does not reflect the recommended 50GB minimum for for ceph-mon store.db for bare metal clusters. The containerized section of the guide reflects this properly, we need bare metal to match.

Bare Metal Guide: 
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/red_hat_ceph_storage_hardware_selection_guide/ceph-hardware-min-recommend

Container HW guide:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/red_hat_ceph_storage_hardware_selection_guide/recommended_minimum_hardware_for_containerized_ceph_clusters

Bare metal should read:

ceph-mon

Disk Space: 10 GB per daemon (50GB Recommended)

Comment 1 Giridhar Ramaraju 2019-08-05 13:06:38 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:09:15 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri