Documentation: OC deployment command: anything we ship under tripleo-heat-templates should be referenced from the same root path Previously it was possible to deploy with the following deployment command: openstack overcloud deploy \ --templates /home/stack/tripleo-heat-templates \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml In OSP12 the file /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml doesn't exist and it gets generated by the deployment workflow. For that to work, anything we ship under tripleo-heat-templates should be referenced from the same root path, so in OSP12 we should use: openstack overcloud deploy \ --templates /home/stack/tripleo-heat-templates \ -e /home/stack/tripleo-heat-templates/environments/network-isolation.yaml Need to state the above as a deployment command note. Note: custom (user defined) environments can still go anywhere,
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!