[baremetal] Retire mas01 NAT 45/49845/3
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 2 Jan 2018 04:36:07 +0000 (05:36 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 3 Jan 2018 00:16:02 +0000 (01:16 +0100)
commit9a6e655e0b851ff6e449027c01ac1a66188b0064
tree96c24dd1bd1894411267651ded0c561046d41ad2
parent68859c38817fcf5993054796e75d8231f98ed3bb
[baremetal] Retire mas01 NAT

Isolate networks by retiring NAT on mas01; also cutting direct
internet access from cluster nodes that are not facing the public
network (prx, cmp).

NOTE: Since we are removing mas01 NAT, VCP VMs (except prx which have
public IPs) and kvm nodes (cmp also have public IPs) will no longer
have direct internet connectivity.
Cluster deployment and operations will work without it, but if it is
required for different reasons, the MaaS proxy could be enabled by
uncommenting the /etc/enviroment section in:
- cluster.baremetal-mcp-pike-common-ha.include.proxy.yml

JIRA: FUEL-317

Change-Id: I5ed8b420296b27df34a54ec1ebd7b7cf58041425
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
mcp/config/states/maas
mcp/salt-formulas/maas/pxe_nat.sls [deleted file]