c57948012c
This change adds a 2-bonds-with-vlans example template which demonstrates the use of two Linux bonds. This template will place the 'Tenant*' networks on a bond with an OVS bridge. Other networks will be placed as VLANs on the Linux bond without a bridge. There is special handling for the Tenant network on DPDK-enabled Compute nodes. Change-Id: I9277c0e6a1267392943214eb5fe55509f7956fbc
18 lines
917 B
YAML
18 lines
917 B
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.
|
|
#
|
|
# NOTE: This version of the templates uses two Linux bonds, but
|
|
# reuses the BondInterfaceOvsOptions parameter for both bond
|
|
# configurations. You can modify this template to have two
|
|
# different parameters for the bonds if options differ.
|
|
#
|
|
# 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 %}
|
|
# Port assignments for the {{role.name}}
|
|
OS::TripleO::{{role.name}}::Net::SoftwareConfig: ../network/config/2-linux-bonds-vlans/{{role.deprecated_nic_config_name|default(role.name.lower() ~ ".yaml")}}
|
|
{%- endfor %}
|