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.
 
 
 
Marius Cornea 9932c2841c Enable management network in network_data 4 years ago
..
README.md Enable management network in network_data 4 years ago
compute-dpdk.j2.yaml Render NIC config templates with jinja2 5 years ago
controller-no-external.j2.yaml Remove the lacp bond mode constraints 4 years ago
controller-v6.j2.yaml Remove the lacp bond mode constraints 4 years ago
role.role.j2.yaml Remove the lacp bond mode constraints 4 years ago

README.md

This directory contains Heat templates to help configure VLANs on a bonded pair of NICs for each Overcloud role.

There are two versions of the controller role template, one with an external network interface, and another without. If the external network interface is not configured, the ctlplane address ranges will be used for external (public) network traffic.

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/bond-with-vlans/cinder-storage.yaml OS::TripleO::Compute::Net::SoftwareConfig: network/config/bond-with-vlans/compute.yaml OS::TripleO::Controller::Net::SoftwareConfig: network/config/bond-with-vlans/controller.yaml OS::TripleO::ObjectStorage::Net::SoftwareConfig: network/config/bond-with-vlans/swift-storage.yaml OS::TripleO::CephStorage::Net::SoftwareConfig: network/config/bond-with-vlans/ceph-storage.yaml

Or use this Heat environment file:

environments/net-bond-with-vlans.yaml

Configuration with no External Network

Same as above except set the following value for the controller role:

OS::TripleO::Controller::Net::SoftwareConfig: network/config/bond-with-vlans/controller-no-external.yaml

Configuration with System Management Network

The Management network is enabled for backwards-compatibility, but is not included in any roles by default. To enable the optional System Management network, create a Heat environment that looks something like this:

resource_registry: OS::TripleO::Network::Management: ../network/management.yaml OS::TripleO::Controller::Ports::ManagementPort: ../network/ports/management.yaml OS::TripleO::Compute::Ports::ManagementPort: ../network/ports/management.yaml OS::TripleO::CephStorage::Ports::ManagementPort: ../network/ports/management.yaml OS::TripleO::ObjectStorage::Ports::ManagementPort: ../network/ports/management.yaml OS::TripleO::BlockStorage::Ports::ManagementPort: ../network/ports/management.yaml

Or use this Heat environment file:

environments/network-management.yaml

Or, add the network to the list of networks used by each role in the role definition file (e.g. roles_data.yaml). Refer to installation documentation for procedure to generate a role file for custom roles.