Bug 1398165 - [Doc] Section 8.3. Examining Composable Service Architecture
Summary: [Doc] Section 8.3. Examining Composable Service Architecture
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 09:13 UTC by VIKRANT
Modified: 2017-01-17 16:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 16:22:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description VIKRANT 2016-11-24 09:13:11 UTC 
Description of problem:

Correct file path in section "8.3. Examining Composable Service Architecture" 

Mentioned output : 

~~~
grep "OS::TripleO::Services::Keystone" /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml
  OS::TripleO::Services::Keystone: puppet/services/keystone.yaml
~~~

But I am not able to see yaml template "/usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml".

No template with name "overcloud-resource-registry-puppet.yaml" is present in path 

$ pwd
/usr/share/openstack-tripleo-heat-templates
$ find . -name overcloud-resource-registry-puppet.yaml
$

Correct path seems to be : 

~~~
grep "OS::TripleO::Services::Keystone" /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.j2.yaml
  OS::TripleO::Services::Keystone: puppet/services/keystone.yaml
~~~

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Dan Macpherson 2016-12-10 15:00:09 UTC 
Yep, this should only modify the OSP10 docs.
Note You need to log in before you can comment on or make changes to this bug.