e645d2e753
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
20 lines
1.0 KiB
YAML
20 lines
1.0 KiB
YAML
# NOTE: This environment file uses the compute-dpdk
|
|
#
|
|
# 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. The nic4 and nic5 are configured for dpdkbond and a provider
|
|
# network shall be associated with it. This template assumes use of
|
|
# network-isolation.yaml.
|
|
#
|
|
# 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:
|
|
{%- for role in roles if role.name != "Compute" %}
|
|
# 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 won't handle any custom compute roles, instead we should have a generic way to override this
|
|
OS::TripleO::Compute::Net::SoftwareConfig: ../network/config/bond-with-vlans/compute-dpdk.yaml
|