You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This replaces net-config-noop.yaml mappings to OS::Heat::None. Also removes all unnecessary setting of it in environments as we map them in overcloud-resource-registry-puppet.j2.yaml. Normally that should be enough but we override them in so many places, so there will be some redundancy. Depends-On: https://review.opendev.org/755275 Change-Id: Ib4d07c835568cb3072770f81a082b5a5e1c790ea
|1 year ago|
|nic-configs||1 year ago|
|README||4 years ago|
|network-environment.yaml||1 year ago|
|network-isolation-absolute.yaml||2 years ago|
|network-isolation.yaml||4 years ago|
|ui-settings.pickle||4 years ago|
Generated Network Isolation Templates
These templates were generated by the UI tool at
ui-settings.pickle is specific to the tool. TripleO will not use it when
doing deployments with these templates, but it is needed to be able to
load the templates into the UI again. Note that the UI only reads this file,
so any changes made by hand to the templates will not be reflected in the UI.
The network-isolation.yaml file needs to reference the port files shipped with
tripleo-heat-templates, so by default the tool generates the paths assuming
network-isolation.yaml will be copied into the environments/ directory of
If the standard tripleo-heat-templates are in use, then the
network-isolation-absolute.yaml file can be used instead. It has hard-coded
references to the port files in /usr/share/openstack-tripleo-heat-templates.
If the generated network isolation templates are at ~/generated-templates, an
example deployment command would look like:
openstack overcloud deploy --templates -e ~/generated-templates/network-isolation-absolute.yaml -e ~/generated-templates/network-environment.yaml