summaryrefslogtreecommitdiffstats
path: root/network/external.yaml
diff options
context:
space:
mode:
authorDan Sneddon <dsneddon@redhat.com>2016-05-18 16:05:18 -0700
committerDan Sneddon <dsneddon@redhat.com>2016-08-08 16:13:30 +0000
commit5aabce1091cbb73887914d6900f06d5a5069d97c (patch)
treea3f77fef6498d7918e744c91768ce897d15c09a0 /network/external.yaml
parentdb229cd82c86bcadc5cd5290f3a2e107770d0bf1 (diff)
Updates and fixes to NIC config template routes
This change adds the ManagementInterfaceDefaultRoute parameter for setting the Management network as the default route in some deployments. Notes were added to indicate that if the Management network is used as the default gateway, then the default route on the control plane should be commented out. The sample network-environment.yaml was modified to include the ManagementInterfaceDefaultRoute, but this is commented out like the rest of the Management network parameters. This change also adds the ControlPlaneDefaultRoute and ExternalInterfaceDefaultRoute to all templates, so that if the networks are customized, the NIC configs can be modified without having to modify the parameters section of the template. The default for the ExternalInterfaceDefaultRoute is '10.0.0.1', and the default for ManagementInterfaceDefaultRoute is set to 'unset'. This change also converts the single-nic-linux-bridge-vlans from DHCP to static IPs on the Control Plane Interface, bringing these templates in line with the rest of the NIC config templates. The parameters needed to be updated in these templates as well. The controller-v6.yaml templates had a default value of "10.0.0.1" for the ExternalInterfaceDefaultRoute. This was confusing, and is now undefined. This change also sets a default gateway on the Control Plane in controller-no-external.yaml templates. Change-Id: I8ea6733fe46902e1baeff4ccfbcd42ecc5a1825f
Diffstat (limited to 'network/external.yaml')
0 files changed, 0 insertions, 0 deletions