Hi All,
We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using the following YAML and env files: https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master Once ONAP stack is created, the SDC, MSO and Robot VMs remain accessible till they reboot as part of their respective install script execution. The install script for each VM is: 1) SDC - /opt/asdc_install.sh 2) MSO - /opt/mso_install.sh 3) Robot - /opt/robot_install.sh We found that in each script the following line is written which changes the NIC interface name from ens[x] to eth0 sed -i "s/ens[0-9]*/eth0/g" /etc/network/interfaces.d/*.cfg Due to this after reboot each VM becomes inaccessible. If the above line is commented, the issue does not happen. We want to know the reason for changing the Interface name. We searched and found some discussions that the Ubuntu-16.04 does not work well with NIC name as ensX however, we didn’t see any such problem. With Regards, Arun Arora
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
