Configure NAT with baremetal when necessary 91/57791/3
authorTim Rozet <trozet@redhat.com>
Wed, 23 May 2018 20:51:48 +0000 (16:51 -0400)
committerTim Rozet <trozet@redhat.com>
Wed, 30 May 2018 18:58:45 +0000 (18:58 +0000)
commitd0f4951e914cacd99c750cb04a332cd7251b9de8
treea4d9dc047c8be37c7c82f3f1583e613679b624ff
parentf0268bd12aab93870a8f2f322f75ccf3965ca476
Configure NAT with baremetal when necessary

We currently only enable NAT on undercloud for virtual deployments.
However, there could be a case where a baremetal deployment also needs
NAT as it is not using an interface on the overcloud nodes with external
access. Therefore this patch changes the behavior to configure NAT when
the gateway of either the external or admin (when external is disabled)
network matches an IP assigned to the undercloud.

JIRA: APEX-605

Change-Id: I9c79af371913e6e5f0d39b433f68205bc7e106c5
Signed-off-by: Tim Rozet <trozet@redhat.com>
apex/tests/test_apex_undercloud.py
apex/undercloud/undercloud.py
lib/ansible/playbooks/configure_undercloud.yml