p/fuel: network: public: Use arm-virtual2 POD cfg 97/37697/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 18 Jul 2017 17:19:46 +0000 (19:19 +0200)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 18 Jul 2017 17:21:14 +0000 (19:21 +0200)
commit779c0cc56646da234019577e17f4af378a205e08
tree30b90e73c10aacf8bec7efba82a09a94995ab737
parent4532c1df3f22a4d69b56e3956dcccf0a9d3ad258
p/fuel: network: public: Use arm-virtual2 POD cfg

FIXME: This should be converted into a dynamic configuration read
from the universal POD descriptor in securedlab, once that is ready.

Until then, just align the public network configuration used by the
virtual POD with the Enea lab configuration specific to arm-virtual2
(i.e. public network on 10.0.9.0/24).

NOTE: Instead of replacing the gateway 10.16.0.1 (now 10.0.9.1) with
our lab's gateway (10.0.9.254), keep it as an extra hop, in order not
to break deploys in different enviroments.

Also, since our gateway resides at 10.0.9.254, trim the DHCP pool
range for the public network to not include that address.

Change-Id: If45ca3140f770f758f0d02c1049084f67f83264e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
patches/opnfv-fuel/0008-network-public-Use-arm-virtual2-POD-config.patch [new file with mode: 0644]