summaryrefslogtreecommitdiffstats
path: root/patches/opnfv-fuel/0009-ci-deploy.sh-Rework-bridge-arguments-for-MCP.patch
AgeCommit message (Collapse)AuthorFilesLines
2017-07-26p/fuel: network: public: Use arm-virtual2 POD cfgAlexandru Avadanii1-0/+181
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: Replace the gateway at 10.16.0.1 (now 10.0.9.1) with the same IP address as our lab's gateway (10.0.9.254), to keep both possible network layouts in sync (using all virtual networks created via virsh, respectively our lab's static config). This will ensure deploys continue to work in both 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. To pass bridge information from CI, Fuel@OPNFV deploy scripts need some small adjustments as well. While at it, rebase our patches on top of latest Fuel@OPNFV changes. Change-Id: I92f01dd819ebf41b1da68d3b934fb10a23257e33 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>