Enable firewall by default on the overcloud
authorBen Nemec <bnemec@redhat.com>
Thu, 26 May 2016 20:02:20 +0000 (15:02 -0500)
committerBen Nemec <bnemec@redhat.com>
Mon, 20 Jun 2016 18:01:57 +0000 (13:01 -0500)
commit73c76b867ddc8a23a30b9a3cac4031189d4178c6
tree968ca6efe2e28efe27d2c6437ddd43131ebe5351
parentdc0562cc7faff6f7f0876551613e71e35153494d
Enable firewall by default on the overcloud

We firewall the undercloud, which is only listening on the
provisioning network anyway, but our default settings leave the
overcloud, which needs to be publicly accessible (for a
deployment-specific definition of "public"), wide open.  This
seems like a bad default.

Anyone who is deploying additional services can either open the
firewall ports themselves as part of the deployment or can set the
ManageFirewall param to false.

Change-Id: I3731a0a7bc4be94c8e7a289c90d304599634e928
overcloud.yaml