tripleo-heat-templates/environments/net-bond-with-vlans-no-external.j2.yaml
Dan Sneddon e645d2e753 Fix comments in environments/net-* network configuration envs
The environment files that select which network configuration files
to use for a deployment have an incorrect comment. The comment
mentions port configurations above the network configuration
templates. This patch corrects the comments.

Change-Id: Idb5c09f7c803a89d388e4458b032bbebd4b2590b
Closes-bug: 1822693
2019-04-01 17:12:28 -07:00

24 lines
1.2 KiB
YAML

# This template configures each role to use a pair of bonded nics (nic2 and
# nic3) and configures an IP address on each relevant isolated network
# for each role.
# This template assumes use of network-isolation.yaml and should be specified
# last on the CLI as a Heat environment so as to override specific
# registry settings in the network-isolation registry.
#
# FIXME: if/when we add functionality to heatclient to include heat
# environment files we should think about using it here to automatically
# include network-isolation.yaml.
resource_registry:
# Set external ports to noop
OS::TripleO::Network::External: OS::Heat::None
OS::TripleO::Controller::Ports::ExternalPort: ../network/ports/noop.yaml
{%- for role in roles if role.name != "Controller" %}
# Network configuration assignments for the {{role.name}}
OS::TripleO::{{role.name}}::Net::SoftwareConfig: ../network/config/bond-with-vlans/{{role.deprecated_nic_config_name|default(role.name.lower() ~ ".yaml")}}
{%- endfor %}
# FIXME this should really be handled via enabled networks in roles_data not overriding here.
OS::TripleO::Controller::Net::SoftwareConfig: ../network/config/bond-with-vlans/controller-no-external.yaml