Bug 1304024

Summary: [RFE] Permit modifying policy.json files for openstack services based on config needs
Product: Red Hat OpenStack Reporter: Freddy Wissing <fwissing>
Component: rhosp-directorAssignee: Hugh Brock <hbrock>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0 (Liberty)CC: mburns, rhel-osp-director-maint, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-03 16:43:20 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:

Description Freddy Wissing 2016-02-02 17:12:31 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 

*** This bug has been marked as a duplicate of bug 1304025 ***