Bug 1304025

Summary: [RFE] Permit modifying policy.json files for openstack services based on config needs
Product: Red Hat OpenStack Reporter: Freddy Wissing <fwissing>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: agurenko, asimonel, emacchi, jcoufal, jschluet, mburns, nlevinki, rhel-osp-director-maint, sasha, sputhenp, vcojot
Target Milestone: Upstream M1Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170419202046.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 20:40:44 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:
Bug Depends On:    
Bug Blocks: 1442136, 1469578    

Description Freddy Wissing 2016-02-02 17:12:56 UTC 
Customer use case is as a hosting provider requires control access and permission within the stack in a granular fashion.  The way that this is done (presently) is through the use of each component's policy.json file.  

The ability to automate this via puppet or heat template at time of deploy would be a nice feature to have as it would assist in consolidating the post deployment actions that are being done and allow for a structured approach in crafting specialized permissions.

====

Additional info

Due to the nature of hosting, this customer would like to have the ability to dictate during the initial data dump into director to add the configuration changes to each components policy.json file.  This would allow for the services to be hardened at the time of deployment rather than either being scripted out later or a manual process post deploy.
Comment 2 Mike Burns 2016-02-03 16:43:20 UTC 
*** Bug 1304024 has been marked as a duplicate of this bug. ***
Comment 3 Mike Burns 2016-04-07 21:07:13 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 5 Emilien Macchi 2017-02-01 22:19:16 UTC 
The blueprint has been created upstream:https://blueprints.launchpad.net/tripleo/+spec/modify-policy-json

Target is pike-1 milestone for now.
Comment 6 Red Hat Bugzilla Rules Engine 2017-02-01 22:19:23 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 7 Red Hat Bugzilla Rules Engine 2017-03-13 04:45:40 UTC 
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 15 Gurenko Alex 2017-11-23 11:38:50 UTC 
Verified on build 2017-11-20.1. Update scenario verified on 2017-11-20.1 -> 2017-11.22.7
Comment 18 errata-xmlrpc 2017-12-13 20:40:44 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/RHEA-2017:3462