summaryrefslogtreecommitdiffstats
path: root/patches/opnfv-fuel/0008-network-public-Use-arm-virtual2-POD-config.patch
AgeCommit message (Collapse)AuthorFilesLines
2017-07-19Revert "p/fuel: network: public: Use arm-virtual2 POD cfg"Alexandru Avadanii1-164/+0
This reverts commit 779c0cc56646da234019577e17f4af378a205e08. Change-Id: Ia5261da363579e7bec442ada58ca16635025f872
2017-07-18p/fuel: network: public: Use arm-virtual2 POD cfgAlexandru Avadanii1-0/+164
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>