Configure NAT with baremetal when necessary 21/58121/1
authorTim Rozet <trozet@redhat.com>
Wed, 23 May 2018 20:51:48 +0000 (16:51 -0400)
committerTim Rozet <trozet@redhat.com>
Thu, 31 May 2018 17:52:54 +0000 (17:52 +0000)
commita4589fcbd106fa06555b1d83ba314029ff438e6a
treefdf57db778080c991ccfae67b371da674dd8244f
parentfd7f3285fa0d872f3eb23ded248e45bf720ebda7
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>
(cherry picked from commit d0f4951e914cacd99c750cb04a332cd7251b9de8)
apex/tests/test_apex_undercloud.py
apex/undercloud/undercloud.py
lib/ansible/playbooks/configure_undercloud.yml