2016-12-08 17:34:08 +00:00
|
|
|
# List of networks, used for j2 templating of enabled networks
|
|
|
|
#
|
|
|
|
# Supported values:
|
|
|
|
#
|
|
|
|
# name: Name of the network (mandatory)
|
|
|
|
# name_lower: lowercase version of name used for filenames
|
|
|
|
# (optional, defaults to name.lower())
|
2018-06-11 09:50:45 -04:00
|
|
|
# service_net_map_replace: if name_lower is set to a custom name this should be set
|
|
|
|
# to original default (optional). This field is only necessary when
|
|
|
|
# changing the default network names, not when adding a new custom network.
|
2016-12-08 17:34:08 +00:00
|
|
|
# enabled: Is the network enabled (optional, defaults to true)
|
2019-02-13 14:00:59 -05:00
|
|
|
# external_resource_network_id: Optional. If set, it should be the UUID of an existing already
|
|
|
|
# created Neutron network that will be used in place of creating a
|
|
|
|
# new network.
|
2019-02-19 14:43:27 -05:00
|
|
|
# external_resource_vip_id: Optional. If set, it should be the UUID of an existing already
|
|
|
|
# created Neutron port for the VIP that will be used
|
|
|
|
# in place of creating a new port.
|
2019-02-13 14:00:59 -05:00
|
|
|
# external_resource_subnet_id: Optional. If set, it should be the UUID of an existing already
|
|
|
|
# created Neutron subnet that will be used in place of creating a
|
|
|
|
# new subnet for the network.
|
|
|
|
# external_resource_segment_id: Optional. If set, it should be the UUID of an existing already
|
|
|
|
# created Neutron segment that will be used in place of creating a
|
|
|
|
# new segment for the network.
|
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
|
|
|
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
|
2017-06-19 11:34:05 -07:00
|
|
|
# vlan: vlan for the network (optional)
|
2016-12-08 17:34:08 +00:00
|
|
|
# vip: Enable creation of a virtual IP on this network
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
# ip_subnet: IP/CIDR, e.g. '192.168.24.0/24' or '2001:db8:fd00:1000::/64'
|
|
|
|
# (optional, may use parameter defaults instead)
|
|
|
|
# allocation_pools: IP range list e.g. [{'start':'10.0.0.4', 'end':'10.0.0.250'}]
|
2017-06-19 11:34:05 -07:00
|
|
|
# gateway_ip: gateway for the network (optional, may use parameter defaults)
|
2018-07-04 23:05:27 +02:00
|
|
|
# routes: Optional, list of networks that should be routed via network gateway.
|
|
|
|
# Example: [{'destination':'10.0.0.0/16', 'nexthop':'10.0.0.1'}]
|
|
|
|
# A single /16 supernet route could be used for 255 smaller /24 subnets.
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
# ipv6_subnet: Optional, sets default IPv6 subnet if IPv4 is already defined.
|
|
|
|
# ipv6_allocation_pools: Set default IPv6 allocation pools if IPv4 allocation pools
|
|
|
|
# are already defined.
|
2018-08-15 16:46:23 +02:00
|
|
|
# gateway_ipv6: Set an IPv6 gateway if IPv4 gateway already defined.
|
2018-07-12 10:48:05 +02:00
|
|
|
# routes_ipv6: Optional, list of networks that should be routed via network gateway.
|
|
|
|
# Example: [{'destination':'fd00:fd00:fd00:3004::/64',
|
|
|
|
# 'nexthop':'fd00:fd00:fd00:3000::1'}]
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
# ipv6: If ip_subnet not defined, this specifies that the network is IPv6-only.
|
|
|
|
# NOTE: IP-related values set parameter defaults in templates, may be overridden,
|
|
|
|
# either by operators, or e.g in environments/network-isolation-v6.yaml where we
|
|
|
|
# set some default IPv6 addresses.
|
|
|
|
# compat_name: for existing stack you may need to override the default
|
|
|
|
# transformation for the resource's name.
|
2018-09-04 01:08:28 +02:00
|
|
|
# mtu: Set the maximum transmission unit (MTU) that is guaranteed to pass
|
|
|
|
# through the data path of the segments in the network.
|
|
|
|
# (optional, defaults to 1500)
|
2018-07-12 10:48:05 +02:00
|
|
|
# subnets: A map of additional subnets for the network (optional). The map
|
|
|
|
# takes the following format:
|
|
|
|
# {'<subnet name>': {'enabled': '<true|false>',
|
|
|
|
# 'vlan': '<vlan-id>',
|
|
|
|
# 'ip_subnet': '<IP/CIDR>',
|
|
|
|
# 'allocation_pools': '<IP range list>',
|
|
|
|
# 'gateway_ip': '<gateway IP>',
|
|
|
|
# 'routes': '<Routes list>',
|
|
|
|
# 'ipv6_subnet': '<IPv6/CIDR>',
|
|
|
|
# 'ipv6_allocation_pools': '<IPv6 range list>',
|
|
|
|
# 'gateway_ipv6': '<IPv6 gateway>',
|
2019-02-13 14:00:59 -05:00
|
|
|
# 'routes_ipv6': '<Routes list>',
|
|
|
|
# 'external_resource_subnet_id': '<Existing subnet UUID (optional)>'}}
|
|
|
|
# 'external_resource_segment_id': '<Existing segment UUID (optional)>'}}
|
2017-06-19 11:34:05 -07:00
|
|
|
#
|
|
|
|
# Example:
|
|
|
|
# - name Example
|
|
|
|
# vip: false
|
|
|
|
# ip_subnet: '10.0.2.0/24'
|
|
|
|
# allocation_pools: [{'start': '10.0.2.4', 'end': '10.0.2.250'}]
|
|
|
|
# gateway_ip: '10.0.2.254'
|
2016-12-08 17:34:08 +00:00
|
|
|
#
|
2018-06-16 16:46:11 -04:00
|
|
|
# To support backward compatibility, two versions of the network definitions
|
|
|
|
# will be created, network/<network>.yaml and network/<network>_v6.yaml. Only
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
# one of these files may be used in the deployment at a time, since the
|
|
|
|
# parameters used for configuration are the same in both files. In the
|
|
|
|
# future, this behavior may be changed to create only one file for custom
|
|
|
|
# networks. You may specify IPv6 addresses for ip_subnet, allocation_pools,
|
|
|
|
# and gateway_ip if no IPv4 addresses are used for a custom network, or set
|
|
|
|
# ipv6: true, and the network/<network>.yaml file will be configured as IPv6.
|
|
|
|
#
|
|
|
|
# For configuring both IPv4 and IPv6 on the same interface, use two separate
|
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
|
|
|
# networks, and then assign both IPs to the same interface in a custom NIC
|
|
|
|
# configuration templates.
|
|
|
|
#
|
|
|
|
# The ordering of the networks below will determine the order in which NICs
|
|
|
|
# are assigned in the network/config/multiple-nics templates, beginning with
|
|
|
|
# NIC2, Control Plane is always NIC1.
|
2017-06-19 11:34:05 -07:00
|
|
|
|
2016-12-08 17:34:08 +00:00
|
|
|
- name: Storage
|
|
|
|
vip: true
|
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
|
|
|
vlan: 30
|
2017-06-22 17:25:03 +02:00
|
|
|
name_lower: storage
|
2018-02-21 16:23:30 +01:00
|
|
|
ip_subnet: '172.16.1.0/24'
|
|
|
|
allocation_pools: [{'start': '172.16.1.4', 'end': '172.16.1.250'}]
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
ipv6_subnet: 'fd00:fd00:fd00:3000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:3000::10', 'end': 'fd00:fd00:fd00:3000:ffff:ffff:ffff:fffe'}]
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|
2016-12-08 17:34:08 +00:00
|
|
|
- name: StorageMgmt
|
|
|
|
name_lower: storage_mgmt
|
|
|
|
vip: true
|
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
|
|
|
vlan: 40
|
2018-02-21 16:23:30 +01:00
|
|
|
ip_subnet: '172.16.3.0/24'
|
|
|
|
allocation_pools: [{'start': '172.16.3.4', 'end': '172.16.3.250'}]
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
ipv6_subnet: 'fd00:fd00:fd00:4000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:4000::10', 'end': 'fd00:fd00:fd00:4000:ffff:ffff:ffff:fffe'}]
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|
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
|
|
|
- name: InternalApi
|
|
|
|
name_lower: internal_api
|
|
|
|
vip: true
|
|
|
|
vlan: 20
|
2018-02-21 16:23:30 +01:00
|
|
|
ip_subnet: '172.16.2.0/24'
|
|
|
|
allocation_pools: [{'start': '172.16.2.4', 'end': '172.16.2.250'}]
|
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
|
|
|
ipv6_subnet: 'fd00:fd00:fd00:2000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:2000::10', 'end': 'fd00:fd00:fd00:2000:ffff:ffff:ffff:fffe'}]
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|
2016-12-08 17:34:08 +00:00
|
|
|
- name: Tenant
|
|
|
|
vip: false # Tenant network does not use VIPs
|
2017-06-22 17:25:03 +02:00
|
|
|
name_lower: tenant
|
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
|
|
|
vlan: 50
|
2017-06-19 11:34:05 -07:00
|
|
|
ip_subnet: '172.16.0.0/24'
|
2018-02-21 16:23:30 +01:00
|
|
|
allocation_pools: [{'start': '172.16.0.4', 'end': '172.16.0.250'}]
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
ipv6_subnet: 'fd00:fd00:fd00:5000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:5000::10', 'end': 'fd00:fd00:fd00:5000:ffff:ffff:ffff:fffe'}]
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|
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
|
|
|
- name: External
|
|
|
|
vip: true
|
|
|
|
name_lower: external
|
|
|
|
vlan: 10
|
|
|
|
ip_subnet: '10.0.0.0/24'
|
2018-02-21 16:23:30 +01:00
|
|
|
allocation_pools: [{'start': '10.0.0.4', 'end': '10.0.0.250'}]
|
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
|
|
|
gateway_ip: '10.0.0.1'
|
|
|
|
ipv6_subnet: '2001:db8:fd00:1000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': '2001:db8:fd00:1000::10', 'end': '2001:db8:fd00:1000:ffff:ffff:ffff:fffe'}]
|
|
|
|
gateway_ipv6: '2001:db8:fd00:1000::1'
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|
2016-12-08 17:34:08 +00:00
|
|
|
- name: Management
|
2018-04-19 19:06:32 -04:00
|
|
|
# Management network is enabled by default for backwards-compatibility, but
|
|
|
|
# is not included in any roles by default. Add to role definitions to use.
|
|
|
|
enabled: true
|
2016-12-08 17:34:08 +00:00
|
|
|
vip: false # Management network does not use VIPs
|
2017-06-22 17:25:03 +02:00
|
|
|
name_lower: management
|
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
|
|
|
vlan: 60
|
2017-06-19 11:34:05 -07:00
|
|
|
ip_subnet: '10.0.1.0/24'
|
|
|
|
allocation_pools: [{'start': '10.0.1.4', 'end': '10.0.1.250'}]
|
2018-09-04 18:33:36 -07:00
|
|
|
gateway_ip: '10.0.1.1'
|
2018-12-05 13:14:24 +00:00
|
|
|
gateway_ipv6: 'fd00:fd00:fd00:6000::1'
|
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated
networks using j2. To allow for backward compatibility,
there will be 2 versions of the network definitions,
<network>.yaml and <network>_v6.yaml. If the ip_subnet
contains an IPv6 address, or if ipv6: true is set on the
network definition in network_data.yaml, then the
<network>.yaml version will contain an IPv6 definition,
otherwise the <network>.yaml will be IPv4, and the
<network>_v6.yaml will be IPv6.
In a future follow-up patch, we will probably only
create the required versions of the networks, either
IPv4, IPv6, not both.
The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway
settings in the network_data.yaml definition file are
used for the <network>_v6.yaml network definition.
Note that these subnet/cidr/gateway definitions only set
the defaults, which can be overridden with parameters
set in an environment file.
Since the parameters for IP and subnet range are the
same (e.g. InternalApiNetCidr applies to both IPv4/v6),
only one version can be used at a time. If an operator
wishes to use dual-stack IPv4/IPv6, then two different
networks should be created, and both networks can be
applied to a single interface.
Note that the workflow for the operator is the same as
before this change, but a new example template has been
added to environments/network-environment-v6.yaml.
Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc
Partially-Implements: blueprint composable-networks
Closes-bug: 1714115
2017-08-30 11:26:52 -07:00
|
|
|
ipv6_subnet: 'fd00:fd00:fd00:6000::/64'
|
|
|
|
ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:6000::10', 'end': 'fd00:fd00:fd00:6000:ffff:ffff:ffff:fffe'}]
|
2018-09-04 01:08:28 +02:00
|
|
|
mtu: 1500
|