Bug 1940304

Summary: [Doc task] - Conceptual information on Orchestrator CLI
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ranjini M N <rmandyam>
Component: DocumentationAssignee: Ranjini M N <rmandyam>
Status: CLOSED CURRENTRELEASE QA Contact: Preethi <pnataraj>
Severity: medium Docs Contact: Amrita <asakthiv>
Priority: unspecified    
Version: 5.0CC: agunn, asakthiv, asriram, hyelloji, kdreyer, vereddy
Target Milestone: ---Keywords: Documentation, FutureFeature
Target Release: 5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1936096 Environment:
Last Closed: 2021-09-16 13:40:47 UTC Type: ---
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: 1936096    
Bug Blocks: 1929147    

Comment 7 Preethi 2021-05-24 11:05:49 UTC 
@Ranjini, Have verified the chapter 2 i.e Conceptual information on Orchestrator CLI . Section content looks good however In sec 2.2, we need to remove last two lines from the stateless service content. 
Please remove the lines marked below "*"




Stateless service of Orchestrators

A stateless service is a service that does not need information of the state to be available. For example, to start an rgw service, additional information is not needed to start or run the service. The rgw service does not create information about this state in order to provide the functionality. Regardless of when the rgw service starts, the state is the same.

***************************************************************************************************************************

These services are easy to manage as they do not require the state of the system to start, stop, or pause the service.

You can configure the following services as a stateless service: MDS, RGW, NFS, RBD-MIRROR, and iSCSI.
****************************************************************************************************************************

Reason to remove them - these services are stateless by their own nature, your configuration is not going to change that, you cannot deploy a MDS as stateless or statefull.. because MDS is stateless, no matter what was the way you deployed it. (ansible, cephadm, rook...) .
Comment 9 Preethi 2021-05-24 11:50:27 UTC 
@Ranjini,Looks good. I moved to Verified.