9e265a209d
Recent changes to the network interface configurations in THT make it unneccessary to use the special controller-v6.yaml template. Instead, adding both an IPv6 and an IPv4 network to the default_route_networks: parameter in roles_data.yaml will result in both an IPv4 and an IPv6 default route. For instance: default_route_networks: ['ControlPlane', 'External'] Change-Id: I23ae304362bd0029cc921010155414f023b19c54 Closes-bug: 1793581
20 lines
970 B
YAML
20 lines
970 B
YAML
# This template configures each role to use Vlans on a single nic for
|
|
# each isolated network.
|
|
# 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.
|
|
#
|
|
# There is no longer a requirement to use net-single-nic-with-vlans-v6.yaml
|
|
# when deploying with IPv6. You may now define both an IPv4 network
|
|
# and an IPv6 network as default routes by adding both networks to the
|
|
# default_route_networks list for the Controller role in roles_data.yaml.
|
|
# Then include this environment file to use single-nic-vlans NIC configs.
|
|
|
|
resource_registry:
|
|
{%- for role in roles %}
|
|
# Network configuration assignments for the {{role.name}}
|
|
OS::TripleO::{{role.name}}::Net::SoftwareConfig: ../network/config/single-nic-vlans/{{role.deprecated_nic_config_name|default(role.name.lower() ~ ".yaml")}}
|
|
{%- endfor %}
|