Bug 1456321

Summary: [Doc]: Use systemctl to manage radsogw in Object gateway guide for Ubuntu
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Tejas <tchandra>
Component: DocumentationAssignee: Aron Gunn <agunn>
Status: CLOSED CURRENTRELEASE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.3CC: agunn, asriram, kdreyer
Target Milestone: rc   
Target Release: 2.4   
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: 2017-12-26 03:41:22 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: 1465789    

Description Tejas 2017-05-29 03:56:13 UTC 
Description of problem:

  The object gateway guide for ubuntu:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/object_gateway_guide_for_ubuntu/
has a lot of references to "/etc/init.d/radosgw" to start and stop the radosgw service.
In ubuntu 16.04 xenial we have moved to systemctl way of managing the service. The RHEL doc has been updated accordingly, we should do it similarly for ubuntu also.

I see 6 such instances:
sudo /etc/init.d/radosgw start

Radosgw service name has also changed.

ex: systemctl status ceph-radosgw.service 

So the command needs to be updated like this.
Comment 3 Tejas 2017-09-15 09:36:59 UTC 
LGTM. moving to verified.