Bug 1952811

Summary:	Adding OSD's by using "advanced OSD services" not exist in ceph-5 Administration Guide
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	skanta
Component:	Documentation	Assignee:	Ranjini M N <rmandyam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	skanta
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	asriram, hyelloji, kdreyer, rmandyam
Target Milestone:	---
Target Release:	5.0
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:	1929147

Description skanta 2021-04-23 08:27:02 UTC

Describe the issue: In the ceph-5 administration guide, Adding OSD's by using the advanced OSD services does not exist. 

This feature is newly added in ceph 5. Please check the below upstream doc for further details.

https://docs.ceph.com/en/latest/cephadm/osd/#advanced-osd-service-specifications



Describe the task you were trying to accomplish:

Suggestions for improvement:

Document URL: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/administration_guide/index?lb_target=preview

Chapter/Section Number and Title:

Product Version:

Environment Details:

Any other versions of this document that also needs this update:

Additional information:

Comment 2 skanta 2021-06-07 05:04:29 UTC

As per the upstream document, there are the following ways to deploy OSD's using advanced service specifications.

1.Rotational
============

       If rotational =1 then OSD will be configured with  SSD's/NVME's.If rotational=0 then the configuration will happen with HDD's. 
       Please explain in details about the how limit option can be used in the above case.

       Refer- https://bugzilla.redhat.com/show_bug.cgi?id=1949467.

2.Size
======
   There are no details mentioned about the size.
   Size options which 5.0 supports-
              LOW:HIGH
                 :HIGH
              LOW:
              EXACT   
   In the document please explain what exactly is the LOW, HIGH, and EXACT 
   
 There exist a bug on this feature- https://bugzilla.redhat.com/show_bug.cgi?id=1946156 

3.MODEL
=======

    There are so many ways we get the model name. The naming convention is different for different commands.
     For example:
                   1.lsblk -o NAME,FSTYPE,LABEL,MOUNTPOINT,SIZE,MODEL
                   2.smartctl -i /dev/sdb

     From the above two commands, we can get the model name. The convention is different.

     In this case, we have to inform to the customers that use "ceph orch device ls --wide" command to get the details. This information is provided by integration with libstoragemgmt. By default, this integration is disabled.
     To enable customer need to execute  "ceph config set mgr mgr/cephadm/device_enhanced_scan true"  command.

     
      Reference for the DOC- https://docs.ceph.com/en/latest/cephadm/osd/#list-devices
 
      Few more details exist at-  https://bugzilla.redhat.com/show_bug.cgi?id=1944527

4. Vendor
=========
        
     There exist a few limitations to the vendor option.
     Please refer- 
                   1.https://bugzilla.redhat.com/show_bug.cgi?id=1946417
                   2.https://bugzilla.redhat.com/show_bug.cgi?id=1949359

5.Device path
=============
               specify directly device paths in specific hosts   
  

6.Limit option
===============

           Please refer -https://bugzilla.redhat.com/show_bug.cgi?id=1949467
   


Please refer- https://docs.ceph.com/en/latest/cephadm/osd/

The hyper link mentioned at "See the Advanced service specifications and filters for deploying OSDs section in the Red Hat Ceph Storage Operations Guide." is navigating to CEPH-4 Documnet.

Comment 4 skanta 2021-06-10 00:34:52 UTC

LGTM and moving to the verified state.