Bug 1411670

Summary: Add DeployIndentifier parameter in section 9.3 (customizing overcloud post-configuration) of Director Installation and Usage.
Product: Red Hat OpenStack Reporter: Navneet Krishnan <nkrishna>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: dmacpher, gkadam, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-09 04:15:58 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:

Description Navneet Krishnan 2017-01-10 09:21:12 UTC
Description of problem: The documentation to set-up the post-deploy script is missing the DeploymentIdentifier paramater. 

 The documentation for OS::TripleO::NodeExtraConfigPost [1] does not include a DeployIdentifier parameter, so the configuration will only be applied during initial stack creation (or when something in the configuration actually changes). This when the OS::TripleO::NodeExtraConfigPost is overriding settings applied by puppet since these are run on every stack update.

The doc in question is:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

The documentation should be up

Additional info:

Comment 1 Navneet Krishnan 2017-01-10 09:44:02 UTC
This traces its root from https://bugzilla.redhat.com/show_bug.cgi?id=1312007

An example configuration is give here: 


Even though this procedure is documented for RHOS 7 , it may effect subsequent versions (RHOS 8,9,10 ) also: (refer section 9.3)


Comment 2 Dan Macpherson 2018-04-09 04:15:58 UTC
This appears to be fixed for OSP7 now. Have checked subsequent versions and DeployIdentifier seems to be used throughout.