2018-03-05 19:28:35 +01:00
|
|
|
heat_template_version: rocky
|
2014-10-23 15:17:49 -04:00
|
|
|
description: >
|
|
|
|
Software Config to drive os-net-config with 2 bonded nics on a bridge.
|
2015-05-06 15:12:34 -04:00
|
|
|
parameters:
|
2015-11-13 13:50:36 +03:00
|
|
|
BondInterfaceOvsOptions:
|
|
|
|
default: ''
|
2017-02-03 01:57:41 -08:00
|
|
|
description: The ovs_options or bonding_options string for the bond
|
|
|
|
interface. Set things like lacp=active and/or bond_mode=balance-slb
|
|
|
|
for OVS bonds or like mode=4 for Linux bonds using this option.
|
2015-11-13 13:50:36 +03:00
|
|
|
type: string
|
2016-08-12 18:07:24 -02:30
|
|
|
constraints:
|
2016-11-23 10:39:11 -05:00
|
|
|
- allowed_pattern: ^((?!balance.tcp).)*$
|
2017-02-03 01:57:41 -08:00
|
|
|
description: The balance-tcp bond mode is known to cause packet loss and
|
2016-11-23 10:39:11 -05:00
|
|
|
should not be used in BondInterfaceOvsOptions.
|
2015-07-27 07:35:49 -04:00
|
|
|
ControlPlaneIp:
|
|
|
|
default: ''
|
|
|
|
description: IP address/subnet on the ctlplane network
|
|
|
|
type: string
|
2018-05-18 18:11:38 +02:00
|
|
|
ControlPlaneSubnetCidr:
|
|
|
|
default: ''
|
|
|
|
description: >
|
|
|
|
The subnet CIDR of the control plane network. (The parameter is
|
|
|
|
automatically resolved from the ctlplane subnet's cidr attribute.)
|
|
|
|
type: string
|
2018-06-30 17:48:25 +02:00
|
|
|
ControlPlaneDefaultRoute:
|
|
|
|
default: ''
|
|
|
|
description: The default route of the control plane network. (The parameter
|
|
|
|
is automatically resolved from the ctlplane subnet's gateway_ip attribute.)
|
|
|
|
type: string
|
2018-07-01 01:13:49 +02:00
|
|
|
DnsServers: # Override this via parameter_defaults
|
|
|
|
default: []
|
|
|
|
description: >
|
|
|
|
DNS servers to use for the Overcloud (2 max for some implementations).
|
|
|
|
If not set the nameservers configured in the ctlplane subnet's
|
|
|
|
dns_nameservers attribute will be used.
|
|
|
|
type: comma_delimited_list
|
2018-06-30 21:07:55 +02:00
|
|
|
EC2MetadataIp: # Here for compatability, not used.
|
|
|
|
default: ''
|
|
|
|
description: The IP address of the EC2 metadata server. (The parameter
|
|
|
|
is automatically resolved from the ctlplane subnet's host_routes attribute.)
|
|
|
|
type: string
|
Render NIC config templates with jinja2
This change converts the existing NIC templates to jinja2 in
order to dynamically render the ports and networks according
to the network_data.yaml. If networks are added to the
network_data.yaml file, parameters will be added to all
NIC templates. The YAML files (as output from jinja with
the default network_data.yaml) are present as an example.
The roles in roles_data.yaml are used to produce NIC configs
for the standard and custom composable roles. In order to
keep the ordering of NICs the same in the multiple-nics
templates, the order of networks was changed in the
network_data.yaml file. This is reflected in the network
templates, and in some of the files that is the only
change.
The roles and roles_data.yaml were modified to include
a legacy name for the NIC config templates for the
built-in roles Controller, Compute, Object Storage,
Block Storage, Ceph Storage, Compute-DPDK, and
Networker roles. There will now be a file produced
with the legacy name, but also one produced with the
<role>-role.j2.yaml format (along with environment
files to help use the new filenames).
Note this change also fixes some typos as well as
a number of templates that had VLANs with device:
entries which were ignored.
Closes-Bug: 1737041
Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35
Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4
2017-11-28 17:00:59 -08:00
|
|
|
{%- for network in networks %}
|
|
|
|
{{network.name}}IpSubnet:
|
2015-05-06 15:12:34 -04:00
|
|
|
default: ''
|
Render NIC config templates with jinja2
This change converts the existing NIC templates to jinja2 in
order to dynamically render the ports and networks according
to the network_data.yaml. If networks are added to the
network_data.yaml file, parameters will be added to all
NIC templates. The YAML files (as output from jinja with
the default network_data.yaml) are present as an example.
The roles in roles_data.yaml are used to produce NIC configs
for the standard and custom composable roles. In order to
keep the ordering of NICs the same in the multiple-nics
templates, the order of networks was changed in the
network_data.yaml file. This is reflected in the network
templates, and in some of the files that is the only
change.
The roles and roles_data.yaml were modified to include
a legacy name for the NIC config templates for the
built-in roles Controller, Compute, Object Storage,
Block Storage, Ceph Storage, Compute-DPDK, and
Networker roles. There will now be a file produced
with the legacy name, but also one produced with the
<role>-role.j2.yaml format (along with environment
files to help use the new filenames).
Note this change also fixes some typos as well as
a number of templates that had VLANs with device:
entries which were ignored.
Closes-Bug: 1737041
Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35
Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4
2017-11-28 17:00:59 -08:00
|
|
|
description: IP address/subnet on the {{network.name_lower}} network
|
2015-09-21 13:41:21 -07:00
|
|
|
type: string
|
Render NIC config templates with jinja2
This change converts the existing NIC templates to jinja2 in
order to dynamically render the ports and networks according
to the network_data.yaml. If networks are added to the
network_data.yaml file, parameters will be added to all
NIC templates. The YAML files (as output from jinja with
the default network_data.yaml) are present as an example.
The roles in roles_data.yaml are used to produce NIC configs
for the standard and custom composable roles. In order to
keep the ordering of NICs the same in the multiple-nics
templates, the order of networks was changed in the
network_data.yaml file. This is reflected in the network
templates, and in some of the files that is the only
change.
The roles and roles_data.yaml were modified to include
a legacy name for the NIC config templates for the
built-in roles Controller, Compute, Object Storage,
Block Storage, Ceph Storage, Compute-DPDK, and
Networker roles. There will now be a file produced
with the legacy name, but also one produced with the
<role>-role.j2.yaml format (along with environment
files to help use the new filenames).
Note this change also fixes some typos as well as
a number of templates that had VLANs with device:
entries which were ignored.
Closes-Bug: 1737041
Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35
Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4
2017-11-28 17:00:59 -08:00
|
|
|
{%- endfor %}
|
2014-10-23 15:17:49 -04:00
|
|
|
resources:
|
|
|
|
OsNetConfigImpl:
|
2016-11-23 10:39:11 -05:00
|
|
|
type: OS::Heat::SoftwareConfig
|
2014-10-23 15:17:49 -04:00
|
|
|
properties:
|
2016-11-23 10:39:11 -05:00
|
|
|
group: script
|
2014-10-23 15:17:49 -04:00
|
|
|
config:
|
2016-11-23 10:39:11 -05:00
|
|
|
str_replace:
|
|
|
|
template:
|
|
|
|
get_file: network/scripts/run-os-net-config.sh
|
|
|
|
params:
|
|
|
|
$network_config:
|
|
|
|
network_config:
|
|
|
|
- type: ovs_bridge
|
|
|
|
name: bridge_name
|
|
|
|
use_dhcp: true
|
|
|
|
members:
|
|
|
|
- type: ovs_bond
|
2014-10-23 15:17:49 -04:00
|
|
|
name: bond1
|
|
|
|
use_dhcp: true
|
2016-11-23 10:39:11 -05:00
|
|
|
ovs_options:
|
|
|
|
get_param: BondInterfaceOvsOptions
|
2014-10-23 15:17:49 -04:00
|
|
|
members:
|
2016-11-23 10:39:11 -05:00
|
|
|
- type: interface
|
|
|
|
name: nic1
|
|
|
|
- type: interface
|
|
|
|
name: nic2
|
2014-10-23 15:17:49 -04:00
|
|
|
outputs:
|
2015-05-19 12:19:52 -07:00
|
|
|
OS::stack_id:
|
|
|
|
description: The OsNetConfigImpl resource.
|
2016-11-23 10:39:11 -05:00
|
|
|
value:
|
|
|
|
get_resource: OsNetConfigImpl
|