Default route should be set in os-net-config templates for tripleo network isolation

[Dan Sneddon]

The os-net-config templates that are used with the network isolation code in TripleO Heat Templates does not set a default route. In most cases, this will result in the default route being placed on the underlcloud 'ctlplane' network. This means that if Horizon and the public APIs are configured on the external interface, only local subnet traffic will reach those services.

The os-net-config templates in the network/config directory of tripleo-heat-templates should be updated with a default route parameter on the external network.

[Dan Sneddon (dsneddon)]

Fix released in https://review.openstack.org/206022

[Dan Sneddon (dsneddon)]

author Dan Prince <email address hidden>
 Mon, 27 Jul 2015 03:35:49 -0800 (07:35 -0400)
committer Dan Prince <email address hidden>
 Thu, 17 Sep 2015 16:39:54 -0800 (20:39 -0400)
This patch updates all network configuration templates so that
we configure the ctlplane network interface with a static IP
instead of using DHCP.

The IP address used for the static IP is passed into each
nested stack network configuration template via the ControlPlaneIp
parameter.

Three new nested stack parameters called ControlPlaneSubnetCidr,
ControlPlaneDefaultRoute, and EC2MetadataIp have been added to help
configure the CIDR, default route, and EC2 metadata route on the ctlplane
statically. These parameters can be customized via the
parameter_defaults section in the heat environment.

A single new template called net-config-static-bridge.yaml has
been added to help migrate towards using the static
configuration templates when not using network isolation.

Depends-On: I257e1cba6dee16f73f75512d1284e1e3b9d4c831

Change-Id: Ib267e6dcf2d5ff77f7a82ee20a123965c2d07565