Bug 1695898

Summary: [RFE] Remove dependency on puppet-ceph for RGW deployment
Product: Red Hat OpenStack Reporter: John Fulton <johfulto>
Component: openstack-tripleo-heat-templatesAssignee: Francesco Pantano <fpantano>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.0 (Train)CC: fpantano, gcharot, gfidente, jamsmith, jjoyce, jschluet, mburns, nweinber, nwolf, sclewis, scohen, slinaber, tvignaud, yrabl
Target Milestone: z2Keywords: FutureFeature, Triaged
Target Release: 16.0 (Train on RHEL 8.1)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-0.20200315025718.033aae9.el8ost Doc Type: Enhancement
Doc Text:
Director operations involving the RADOS gateway no longer require interaction with puppet-ceph. Previously, tripleo-heat-templates had a dependency on puppet-ceph for the RADOS gateway component deployment. The move to tripleo-ansible eliminates this dependency.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-14 12:15:28 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: 1814148    

Description John Fulton 2019-04-03 21:13:05 UTC 
ceph-ansible replaced puppet-ceph for all functions of overcloud deployment with ceph except for a task necessary for RGW deployment. We create the swift-like user, service and endpoint for RGW in Keystone using puppet-ceph [1][2]. To remove puppet-ceph our best bet is probably to replace that code with a generic call for puppet-keystone.

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/deployment/ceph-ansible/ceph-rgw.yaml#L102-L109
[2] https://github.com/openstack/puppet-ceph/blob/master/manifests/rgw/keystone/auth.pp
Comment 21 errata-xmlrpc 2020-05-14 12:15:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2114