Hi Bharath, I have commented out those lines for three machines in the yaml file. Now, I am able to ssh into the 16.04 based instances.
Thanks for your help. ​Regards , Ganesh On Sat, Sep 2, 2017 at 7:48 PM, bharath thiruveedula < bharath_...@hotmail.com> wrote: > > Hi Ganesh, > > > If you see the heat template for the VMs with ubuntu 16.04 image, we are > trying to change the network interface name to eth0. Once the installation > is done, it reboots. After that, in my case too, the network interface is > not up. So we commented that part (which renames the network interface) in > the heat template and created the stack. > > > WARNING: you have to make sure, you change the "eth0" to correct net iface > name in the scripts > > Best Regards > Bharath T > > ------------------------------ > *From:* onap-discuss-boun...@lists.onap.org <onap-discuss-bounces@lists. > onap.org> on behalf of Ganesh Kaila <gane...@biarca.com> > *Sent:* Saturday, September 2, 2017 7:30 PM > *To:* Kumar Skand Priya, Viswanath V > *Cc:* onap-discuss@lists.onap.org > *Subject:* Re: [onap-discuss] [E] ONAP v1.0 Vanilla Openstack SDC VM is > not responding > > Hi Viswa, > > Thanks for your reply. > > I could SSH into that machine *vm1-sdc *when the heat deployment > finished. I am able to see the portal page after 1 hour 15 minutes of the > deployment. By that time, I am loosing the access to the machines which are > spinned with Ubuntu 16.04 image like *vm1-sdc*, *vm1-mso*,* vm1-robot* > machines. > > FYI, I have allowed ICMP, TCP 22, 8989, 8080, 8443, 3306 ports for now > explicitly. > > > Thanks, > Ganesh > > On Sat, Sep 2, 2017 at 6:55 PM, Kumar Skand Priya, Viswanath V < > viswanath.kumarskandpr...@verizon.com> wrote: > >> Ganesh, >> >> In the YAML template you would be using Ubuntu 16.04 / 14.04 cloud >> images which will have password based SSH login disabled by default. >> You may need to use the keypair that you mentioned in onap_key var. >> >> Once you get into SDC VM, try to get status of docker containers by >> using sudo docker ps -a, and verify all the components of SDC are up ( >> FE, BE, DB etc.. ) >> >> W.r.t ICMP, check your security group whether ICMP egress / ingress is >> allowed. Do the same check for SSH as well. As a WA, try getting >> inside console directly. >> >> Hope this helps. >> >> BR, >> Viswa >> >> >> Viswanath Kumar Skand Priya >> Architect >> SDN, Cloud Services & Orchestration >> >> >> >> On Sat, Sep 2, 2017 at 5:35 PM, Ganesh Kaila <gane...@biarca.com> wrote: >> > Hi all, >> > >> > I am trying to deploy ONAP v1.0.0 on Vanilla openstack. I have used the >> > following heat templates to deploy it. >> > >> > >> > https://nexus.onap.org/content/sites/raw/org.openecomp.demo/ >> heat/OpenECOMP/1.0.0/onap_openstack.yaml >> > >> > https://nexus.onap.org/content/sites/raw/org.openecomp.demo/ >> heat/OpenECOMP/1.0.0/onap_openstack.env >> > >> > >> > I have updated /etc/hosts file with the demo domain names mentioned in >> the >> > Tutorial: Accessing the ONAP Portal and able to access the portal home >> page >> > as guided in the wiki. >> > >> > When I am trying the Creating a Licensing Model , I could not see the >> SDC >> > widget loading. To verify the vm1-sdc vm, I am not able to SSH into that >> > machine and it is not even responding to ICMP requests. Did anyone see >> the >> > similar problem? If yes, how do I resolve this problem? >> > >> > Please help me. Thanks in advance. >> > >> > >> > Regards >> > , >> > Ganesh >> > >> > _______________________________________________ >> > onap-discuss mailing list >> > onap-discuss@lists.onap.org >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.o >> nap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=udBTRvFvX >> C5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkR >> VTaKybM-QdOEEflZQ1UA1C3bK3Y3fLmJGlCViaBBmZar&m=_YnT3QRgu7zaH >> 8UIhQe1HV3tqp6ed6SX__CoJSboj7M&s=8QzVgl7V1c7-s8WcbY >> RYCFZ2KioGg3cfYC28z-QVu80&e= >> > >> > >
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
