Heat templates for deploying OpenStack
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
ramishra 1311f8a521 Don't assume every role has default_route_networks 5 months ago
..
README.md Remove legacy controller-v6.yaml NIC config templates 2 years ago
role.role.j2.yaml Don't assume every role has default_route_networks 5 months ago

README.md

This directory contains Heat templates to help configure Vlans on a single NICs for each Overcloud role.

Configuration

To make use of these templates create a Heat environment that looks something like this:

resource_registry: OS::TripleO::BlockStorage::Net::SoftwareConfig: network/config/single-nic-linux-bridge-vlans/cinder-storage.yaml OS::TripleO::Compute::Net::SoftwareConfig: network/config/single-nic-linux-bridge-vlans/compute.yaml OS::TripleO::Controller::Net::SoftwareConfig: network/config/single-nic-linux-bridge-vlans/controller.yaml OS::TripleO::ObjectStorage::Net::SoftwareConfig: network/config/single-nic-linux-bridge-vlans/swift-storage.yaml OS::TripleO::CephStorage::Net::SoftwareConfig: network/config/single-nic-linux-bridge-vlans/ceph-storage.yaml

Or use this Heat environment file:

environments/net-single-nic-linux-bridge-with-vlans.yaml

Configuration with IPv6 Networks

There is no longer a requirement to use controller-v6.yaml for Controller nodes 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.