openstack
/
tripleo-heat-templates
Code Issues Proposed changes

Add note indicating only Controllers use network VIPs 

Networks defined in the network_data YAML files should only set
vip: true on networks that are attached to the roles hosting
high-availability endpoints (Controller by default). Only these
roles are wired to take advantage of the virtual IPs.

Change-Id: Iaefd5b91ef4e24897c57b0113b551295f443dca3
Closes-bug: 1928142
This commit is contained in:
Dan Sneddon 2021-05-11 15:00:42 -07:00
parent 2732d826c8
commit 5e54723370
5 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
network_data.yaml
View File

@ -23,7 +23,8 @@
# new segment for the network.
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
# vlan: vlan for the network (optional)
# vip: Enable creation of a virtual IP on this network
# vip: Enable creation of a virtual IP on this network. Only for networks attached
# to the roles running high-availability clustering (Controller by default).
# 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'}]

3
network_data_dashboard.yaml
View File

@ -8,7 +8,8 @@
# enabled: Is the network enabled (optional, defaults to true)
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
# vlan: vlan for the network (optional)
# vip: Enable creation of a virtual IP on this network
# vip: Enable creation of a virtual IP on this network. Only for networks attached
# to the roles running high-availability clustering (Controller by default).
# 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'}]

3
network_data_ganesha.yaml
View File

@ -23,7 +23,8 @@
# new segment for the network.
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
# vlan: vlan for the network (optional)
# vip: Enable creation of a virtual IP on this network
# vip: Enable creation of a virtual IP on this network. Only for networks attached
# to the roles running high-availability clustering (Controller by default).
# 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'}]

3
network_data_routed.yaml
View File

@ -18,7 +18,8 @@
# enabled: Is the network enabled (optional, defaults to true)
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
# vlan: vlan for the network (optional)
# vip: Enable creation of a virtual IP on this network
# vip: Enable creation of a virtual IP on this network. Only for networks attached
# to the roles running high-availability clustering (Controller by default).
# 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'}]

3
network_data_subnets_routed.yaml
View File

@ -11,7 +11,8 @@
# enabled: Is the network enabled (optional, defaults to true)
# NOTE: False will use noop.yaml for unused legacy networks to support upgrades.
# vlan: vlan for the network (optional)
# vip: Enable creation of a virtual IP on this network
# vip: Enable creation of a virtual IP on this network. Only for networks attached
# to the roles running high-availability clustering (Controller by default).
# 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'}]