Bug 1465564
Summary: | [Docs] OC deployment command: anything we ship under tripleo-heat-templates should be referenced from the same root path | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 13.0 (Queens) | CC: | akaris, bfournie, bschmaus, djuran, dmacpher, ealcaniz, emacchi, jjoyce, mcornea, pablo.iranzo, rcernin, rhos-docs, srevivo |
Target Milestone: | async | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-16 02:29:52 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
Alexander Chuzhoy
2017-06-27 16:02:34 UTC
Clearing target release pending docs triage. This is a fairly simple documentation requirement for OSP12. Basically including *.j2.yaml environment files will only work from the template directory they're included from. Per Sasha's example: RIGHT: Template directory: /usr/share/openstack-tripleo-heat-templates/ Environment file: /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml (network-isolation.j2.yaml before rendering) RIGHT: Template directory: /home/stack/tripleo-heat-templates Environment file: /home/stack/tripleo-heat-templates/environments/network-isolation.yaml (network-isolation.j2.yaml before rendering) WRONG: Template directory: /usr/share/openstack-tripleo-heat-templates/ Environment file: /home/stack/tripleo-heat-templates/environments/network-isolation.yaml (network-isolation.j2.yaml before rendering) This will mostly affect the network isolation documentation. Also, this might reduce the network isolation documentation since this new feature auto-renders the network iso resources for composable services. Requires: - a note in network iso section about network-isolation.j2.yaml environment file location with the template collection - Removing the manual composable role config (ports, networks, etc) from network iso section Hi Dan Isn't this one similar for OSP10? https://bugzilla.redhat.com/show_bug.cgi?id=1485359 What should we do with "openstack overcloud deploy" without "network-isolation.yaml". Without "network-isolation.yaml", default networks are applied to network interfaces on overcloud nodes. That means that networkings basically do not work. Only the following files exist: /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.j2.yaml /usr/share/openstack-tripleo-heat-templates/environments/network-isolation-v6.j2.yaml /usr/share/openstack-tripleo-heat-templates/environments/network-isolation-no-tunneling.j2.yaml Accepting into RHOSP 14 program and flagging for 12, 13, and 14. Assignee to discuss with DFG which versions to apply fix to. Assigning to Alex for review. Alex, there's some additional discussion in this BZ that appears to be outside the scope of original request. See Dan's comment 4 for the suggested work to satisfy the original request. Updating version to a supported release. This BZ is still valid fro OSP13+. Thanks, Sasha! |