|
Im not sure who / how this value was changed, but when you are doing a virtual "AUTOMATED" installation, then the value needs to remain as the FUEL VM, since in a nested
environment, the idea is NOT to allow the VM's external access (only to the FUEL VM on the ADMIN network )...
If you need to have a different "virtualConfiguration", the create a new subdirectory and a alternate configuration rather than the working / default template for CI for FUEL Nested Setup
Change-Id: I6163307bac285d710a5a5c683798a3c20c609932
Signed-off-by: lmcdasm <lmcdasm@OPNFV-VNCSRV1.opnfvericsson.ca>
JIRA: 007
|