OK thanks Arun and apologies for missing the latest email. I was starting my email stack from the bottom ☺
I’m glad you were able to reboot the VMs correctly. Marco From: "Arun Arora (c)" <aroraa...@vmware.com> Date: Monday, May 29, 2017 at 6:38 AM To: "Arun Arora (c)" <aroraa...@vmware.com>, "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org> Cc: "Kapil Gupta (c)" <gka...@vmware.com>, "Gaurav Gupta (c)" <guptagau...@vmware.com>, "Abhishek Saxena (c)" <abhisheksax...@vmware.com>, Suresh Babu Nekkalapudi <snekkalap...@vmware.com>, Ramesh Tammana <rame...@vmware.com> Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation Hi Marco, I figured that change in /etc/default/grub should be OK. However, change in interface name is also required in /etc/udev/rules.d/70-persistent-net.rules. This file also has the interface name which remain ensX after reboot which causes network interface configuration failure. If following is executed then after reboot VM is reachable, interface name is changes to eth0 and network works fine. sed -i "s/ens[0-9]*/eth0/g" /etc/udev/rules.d/70-persistent-net.rules Thanks, Arun From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c) Sent: Monday, May 29, 2017 3:15 PM To: PLATANIA, MARCO (MARCO) <plata...@research.att.com>; onap-discuss@lists.onap.org Cc: Kapil Gupta (c) <gka...@vmware.com> Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation Hi Marco, I realized you were referring to /etc/default/grub but in my previous email I attached grub.conf files for all VM. I am attaching /etc/default/grub of each VM now. Pls note as all three VMs use Ubuntu 16.04 as image I am assuming that the original grub is same for all. So, I created a VM with Ubuntu 16.04 and took grub file from it. Pls let me know if this is incorrect procedure to get unmodified /etc/default/grub. Thanks, Arun From: Arun Arora (c) Sent: Monday, May 29, 2017 12:55 PM To: PLATANIA, MARCO (MARCO) <plata...@research.att.com<mailto:plata...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>> Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation Hi Marco, I am attaching the Original and modified grub.cfg file for all VMs. Pls let me know of any possible fix. Also, In my understanding whatever fix is done should happen automatically when creating ONAP stack via HEAT. We can try the fix and then can think of how to automate it. With Regards, Arun From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com] Sent: Friday, May 26, 2017 6:51 PM To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>> Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation Hello Arun, Some components need to know their public IP address. This is retrieved in <component>_vm_init.sh (i.e. policy, sdc). We use this command: ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2 Because Ubuntu 16.04 VMs have a different vNIC name, as you said ensX, we changed the interface name in those VMs to reflect the usual case. We didn’t see any problem after rebooting the VMs. Thank you for letting us know. I think the problem is not in the vNIC per se, but in the grub file that gets modified. That prevents correct start up. Could you please attach the original grub file? Thanks, Marco From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "Arun Arora (c)" <aroraa...@vmware.com<mailto:aroraa...@vmware.com>> Date: Friday, May 26, 2017 at 8:15 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Cc: "Kapil Gupta (c)" <gka...@vmware.com<mailto:gka...@vmware.com>> Subject: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation 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://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=0W0Iqz1u4tpxjq-popdh_Dub7VDg8oFWFEzedDoFcQU&s=-c1dDfM35o9Ih-STMgfXqEGBxtvMeaBGaskuy9V2bAQ&e=> 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://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master&d=DwMF-g&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=0W0Iqz1u4tpxjq-popdh_Dub7VDg8oFWFEzedDoFcQU&s=-c1dDfM35o9Ih-STMgfXqEGBxtvMeaBGaskuy9V2bAQ&e=> 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
