Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1545411

Summary:	OSP 12 HCI documentation makes use of port definitions that are no longer installed
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	aschultz, bfournie, dsneddon, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-12 21:35: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 David Hill 2018-02-14 21:24:03 UTC

Description of problem:
OSP 12 HCI documentation [1] makes use of port definitions that are no longer installed:

Custom roles like ComputeHCI do not have the required port assignment Heat templates, so you need to define these yourself. To do so, create a new Heat template named ports.yaml in ~/templates containing the following:

resource_registry:
  OS::TripleO::ComputeHCI::Ports::ExternalPort: /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml  # 1
  OS::TripleO::ComputeHCI::Ports::InternalApiPort: /usr/share/openstack-tripleo-heat-templates/network/ports/internal_api.yaml
  OS::TripleO::ComputeHCI::Ports::StoragePort: /usr/share/openstack-tripleo-heat-templates/network/ports/storage.yaml
  OS::TripleO::ComputeHCI::Ports::TenantPort: /usr/share/openstack-tripleo-heat-templates/network/ports/tenant.yaml
  OS::TripleO::ComputeHCI::Ports::StorageMgmtPort: /usr/share/openstack-tripleo-heat-templates/network/ports/storage_mgmt.yaml # 2
1


and when we look for these files:
(undercloud) [stack@undercloud-0 ports]$ pwd
/usr/share/openstack-tripleo-heat-templates/network/ports
(undercloud) [stack@undercloud-0 ports]$ ls -atlr *storage_mgmt*
ls: cannot access *storage_mgmt*: No such file or directory



[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/hyper-converged_infrastructure_guide/


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Alex Schultz 2018-02-15 21:28:00 UTC

I believe this is one of the side effects of the switch to composable networks where the files are no longer statically defined but rather build when the templates are processed. I believe the references are still OK.  Moving over to the HardProv team to confirm.

Comment 2 Bob Fournier 2018-02-16 17:30:47 UTC

Alex - yes, this is correct, the network port files are now dynamically generated during the deploy process.  (See the discussion on rhos-tech here - http://post-office.corp.redhat.com/archives/rhos-tech/2018-February/msg00093.html).

There is some documentation here [1] on how to use composable networks

We also have a doc bug to improve it - https://bugzilla.redhat.com/show_bug.cgi?id=1538209 and describe better the tool to run before deployment if you want to see the resulting files.

Dave - I think this can probably be closed as a dup of 1538209, but I'm assigning to docs for now.  I agree there should probably be some description of how port and network files will not be in /usr/share/openstack-tripleo-heat-templates/network/ports and instead will be generated dynamically.  Perhaps there is more docs beyond that in [1], if there is this can be closed.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/advanced_overcloud_customization/index#defining_a_composable_network

Comment 3 Bob Fournier 2018-07-12 21:35:20 UTC

Marking this a dup of the documentation bug to better define how to handle nic config files generated using jinja.

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