openstack-virtual-baremetal/overcloud-templates/bond-network-templates
Ben Nemec 6f371b1220 Regenerate network templates
The only actual change is some parameter descriptions so that they
are consistent with the ones in tripleo-heat-templates.
2018-02-01 17:11:42 -06:00
..
nic-configs Regenerate network templates 2018-02-01 17:11:42 -06:00
README Deprecate top-level network templates 2017-08-11 10:23:32 -05:00
network-environment.yaml Deprecate top-level network templates 2017-08-11 10:23:32 -05:00
network-isolation-absolute.yaml Deprecate top-level network templates 2017-08-11 10:23:32 -05:00
network-isolation.yaml Deprecate top-level network templates 2017-08-11 10:23:32 -05:00
ui-settings.pickle Deprecate top-level network templates 2017-08-11 10:23:32 -05:00

README

Generated Network Isolation Templates
-------------------------------------
These templates were generated by the UI tool at
https://github.com/cybertron/tripleo-scripts#net-iso-genpy

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
tripleo-heat-templates.

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