2018-03-05 18:28:35 +00:00
|
|
|
heat_template_version: rocky
|
2014-10-23 19:17:49 +00:00
|
|
|
description: >
|
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-29 01:00:59 +00:00
|
|
|
Software Config to drive os-net-config for a simple interface on a bridge.
|
2015-05-06 19:12:34 +00:00
|
|
|
parameters:
|
2015-07-27 11:35:49 +00:00
|
|
|
ControlPlaneIp:
|
|
|
|
default: ''
|
|
|
|
description: IP address/subnet on the ctlplane network
|
|
|
|
type: string
|
2018-05-18 16:11:38 +00: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 15:48:25 +00: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-09-24 23:06:48 +00:00
|
|
|
ControlPlaneStaticRoutes:
|
|
|
|
default: []
|
|
|
|
description: >
|
|
|
|
Routes for the ctlplane network traffic.
|
|
|
|
JSON route e.g. [{'destination':'10.0.0.0/16', 'nexthop':'10.0.0.1'}]
|
|
|
|
Unless the default is changed, the parameter is automatically resolved
|
|
|
|
from the subnet host_routes attribute.
|
|
|
|
type: json
|
2018-09-03 23:08:28 +00:00
|
|
|
ControlPlaneMtu:
|
|
|
|
default: 1500
|
|
|
|
description: The maximum transmission unit (MTU) size(in bytes) that is
|
|
|
|
guaranteed to pass through the data path of the segments in the network.
|
|
|
|
(The parameter is automatically resolved from the ctlplane network's mtu attribute.)
|
|
|
|
type: number
|
2018-06-30 23:13:49 +00: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
|
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-29 01:00:59 +00:00
|
|
|
{%- for network in networks %}
|
|
|
|
{{network.name}}IpSubnet:
|
2015-05-06 19:12:34 +00: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-29 01:00:59 +00:00
|
|
|
description: IP address/subnet on the {{network.name_lower}} network
|
2015-09-21 20:41:21 +00:00
|
|
|
type: string
|
2018-06-07 10:36:18 +00:00
|
|
|
{{network.name}}InterfaceRoutes:
|
|
|
|
default: []
|
|
|
|
description: >
|
|
|
|
Routes for the {{network.name_lower}} network traffic.
|
|
|
|
JSON route e.g. [{'destination':'10.0.0.0/16', 'nexthop':'10.0.0.1'}]
|
|
|
|
Unless the default is changed, the parameter is automatically resolved
|
|
|
|
from the subnet host_routes attribute.
|
|
|
|
type: json
|
2018-09-03 23:08:28 +00:00
|
|
|
{{network.name}}Mtu:
|
2019-01-07 21:09:27 +00:00
|
|
|
default: {{network.mtu|default('1500')}}
|
2018-09-03 23:08:28 +00:00
|
|
|
description: The maximum transmission unit (MTU) size(in bytes) that is
|
|
|
|
guaranteed to pass through the data path of the segments in the
|
|
|
|
{{network.name}} network.
|
|
|
|
type: number
|
2019-03-26 13:40:10 +00:00
|
|
|
{{network.name}}InterfaceDefaultRoute:
|
|
|
|
default: ''
|
|
|
|
description: default route for the {{network.name_lower}} network
|
|
|
|
type: string
|
2019-04-09 21:00:37 +00:00
|
|
|
{{network.name}}NetworkVlanID:
|
|
|
|
default: {{network.vlan|default(1)}}
|
|
|
|
description: Vlan ID for the {{network.name_lower}} network traffic.
|
|
|
|
type: number
|
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-29 01:00:59 +00:00
|
|
|
{%- endfor %}
|
2014-10-23 19:17:49 +00:00
|
|
|
resources:
|
|
|
|
OsNetConfigImpl:
|
2016-11-23 15:39:11 +00:00
|
|
|
type: OS::Heat::SoftwareConfig
|
2014-10-23 19:17:49 +00:00
|
|
|
properties:
|
2016-11-23 15:39:11 +00:00
|
|
|
group: script
|
2014-10-23 19:17:49 +00:00
|
|
|
config:
|
2016-11-23 15:39:11 +00: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: interface
|
|
|
|
name: interface_name
|
2014-10-23 19:17:49 +00:00
|
|
|
# force the MAC address of the bridge to this interface
|
|
|
|
primary: true
|
|
|
|
outputs:
|
2015-05-19 19:19:52 +00:00
|
|
|
OS::stack_id:
|
|
|
|
description: The OsNetConfigImpl resource.
|
2016-11-23 15:39:11 +00:00
|
|
|
value:
|
|
|
|
get_resource: OsNetConfigImpl
|
|
|
|
|