Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-30 Thread Arun Arora (c) 
Hi Daniel,



Thanks for the info. I’ll do the needful.



Best Regards,

Arun



From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, May 30, 2017 7:59 PM
To: Arun Arora (c) ; PLATANIA, MARCO 

Cc: Kapil Gupta (c) ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



1)  Anyone can commit as long as they have LF account

2)  You need to make a jira ticket

3)  Gerrit.onap.org

4)  This is pretty similar processwise but not the same urls (obviously) 
https://www.mediawiki.org/wiki/Gerrit/Tutorial<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mediawiki.org_wiki_Gerrit_Tutorial&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=ahmkwVxaWA3gAK1pEM8OwB_TKb_y2KQIwZz6klu-PaE&s=ytZSkvJCRgp8cTFAbRK4l0z7E-_Br7CHcBsNOX4sArA&e=>





Thanks,

Daniel Rose

ECOMP / ONAP

com.att.ecomp

732-420-7308



From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, May 30, 2017 9:40 AM
To: PLATANIA, MARCO 
mailto:plata...@research.att.com>>
Cc: Kapil Gupta (c) mailto:gka...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Hi Marco,



Thanks for the suggestion. I would also have done the same change as I checked 
it locally already.



For the patch I would like to do all the heavy-lifting for submission of patch 
as in that way I would get familiar with the commit process.

For it I would request you help for the following things:

1)  How to enable my user as contributor?

2)  Any User Story that I need to create (create where?) or mention in the 
commit logs?

3)  The Git repo URL for SDC, MSO and Robot

4)  Any URL which explains the whole code commit hygiene such as:

a.   GIT branching strategy to commit

b.  Pull request submission requirement

c.   Any specific info to add into comments like commit-ID, Commit length 
restriction etc



I will surely add you as a reviewer for it.



With Best Regards,

Arun Arora



From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, May 30, 2017 6:48 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



You can add sed -i "s/ens[0-9]*/eth0/g" 
/etc/udev/rules.d/70-persistent-net.rules to mso/robot/asdc_install.sh, in the 
block of code in which the interface name is changed.



Then, you can commit the changes, I’ll review them and merge.



If you prefer, I can make those changes by myself.



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 3:57 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-30 Thread ROSE, DANIEL V 
1)  Anyone can commit as long as they have LF account

2)  You need to make a jira ticket

3)  Gerrit.onap.org

4)  This is pretty similar processwise but not the same urls (obviously) 
https://www.mediawiki.org/wiki/Gerrit/Tutorial


Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, May 30, 2017 9:40 AM
To: PLATANIA, MARCO 
Cc: Kapil Gupta (c) ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation


Hi Marco,



Thanks for the suggestion. I would also have done the same change as I checked 
it locally already.



For the patch I would like to do all the heavy-lifting for submission of patch 
as in that way I would get familiar with the commit process.

For it I would request you help for the following things:

1)  How to enable my user as contributor?

2)  Any User Story that I need to create (create where?) or mention in the 
commit logs?

3)  The Git repo URL for SDC, MSO and Robot

4)  Any URL which explains the whole code commit hygiene such as:

a.   GIT branching strategy to commit

b.  Pull request submission requirement

c.   Any specific info to add into comments like commit-ID, Commit length 
restriction etc



I will surely add you as a reviewer for it.



With Best Regards,

Arun Arora



From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, May 30, 2017 6:48 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



You can add sed -i "s/ens[0-9]*/eth0/g" 
/etc/udev/rules.d/70-persistent-net.rules to mso/robot/asdc_install.sh, in the 
block of code in which the interface name is changed.



Then, you can commit the changes, I’ll review them and merge.



If you prefer, I can make those changes by myself.



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 3:57 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:

OK thanks Arun and apologies for missing the latest email. I was starting my 
email stack from the bottom ☺



I’m glad you

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-30 Thread Arun Arora (c) 
Hi Marco,



Thanks for the suggestion. I would also have done the same change as I checked 
it locally already.



For the patch I would like to do all the heavy-lifting for submission of patch 
as in that way I would get familiar with the commit process.

For it I would request you help for the following things:

1)  How to enable my user as contributor?

2)  Any User Story that I need to create (create where?) or mention in the 
commit logs?

3)  The Git repo URL for SDC, MSO and Robot

4)  Any URL which explains the whole code commit hygiene such as:

a.   GIT branching strategy to commit

b.  Pull request submission requirement

c.   Any specific info to add into comments like commit-ID, Commit length 
restriction etc



I will surely add you as a reviewer for it.



With Best Regards,

Arun Arora



From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, May 30, 2017 6:48 PM
To: Arun Arora (c) 
Cc: onap-discuss@lists.onap.org; Kapil Gupta (c) ; Gaurav 
Gupta (c) ; Abhishek Saxena (c) 
; Suresh Babu Nekkalapudi ; 
Ramesh Tammana 
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



You can add sed -i "s/ens[0-9]*/eth0/g" 
/etc/udev/rules.d/70-persistent-net.rules to mso/robot/asdc_install.sh, in the 
block of code in which the interface name is changed.



Then, you can commit the changes, I’ll review them and merge.



If you prefer, I can make those changes by myself.



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 3:57 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:

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)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" mailto:gka...@vmware.com>>, "Gaurav 
Gupta (c)" mailto:guptagau...@vmware.com>>, "Abhishek 
Saxena (c)" mailto:abhisheksax...@vmware.com>>, 
Suresh Babu Nekkalapudi 
mailto:snekkalap...@vmware.com>>, Ramesh Tammana 
mailto: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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-30 Thread PLATANIA, MARCO (MARCO) 
You can add sed -i "s/ens[0-9]*/eth0/g" 
/etc/udev/rules.d/70-persistent-net.rules to mso/robot/asdc_install.sh, in the 
block of code in which the interface name is changed.

Then, you can commit the changes, I’ll review them and merge.

If you prefer, I can make those changes by myself.

Marco

From: "Arun Arora (c)" 
Date: Monday, May 29, 2017 at 3:57 PM
To: "PLATANIA, MARCO (MARCO)" 
Cc: "onap-discuss@lists.onap.org" , "Kapil Gupta 
(c)" , "Gaurav Gupta (c)" , 
"Abhishek Saxena (c)" , Suresh Babu Nekkalapudi 
, Ramesh Tammana 
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation


Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) 
Cc: onap-discuss@lists.onap.org; Kapil Gupta (c) ; Gaurav 
Gupta (c) ; Abhishek Saxena (c) 
; Suresh Babu Nekkalapudi ; 
Ramesh Tammana 
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:

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)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" mailto:gka...@vmware.com>>, "Gaurav 
Gupta (c)" mailto:guptagau...@vmware.com>>, "Abhishek 
Saxena (c)" mailto:abhisheksax...@vmware.com>>, 
Suresh Babu Nekkalapudi 
mailto:snekkalap...@vmware.com>>, Ramesh Tammana 
mailto: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> 
[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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) mailto:gka...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Hi Mar

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Lefevre, Catherine 
Good morning Arun,

You need submit your changes via Gerrit in the corresponding repos then the 
MSO, SDC, Testsuite ONAP Maintainers will review them and merge them.

Here is a summary of the review/merge process.

[cid:image001.jpg@01D2D919.66B16FC0]

Best regards
Catherine

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 9:57 PM
To: PLATANIA, MARCO 
Cc: Kapil Gupta (c) ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation


Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) mailto:aroraa...@vmware.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Kapil 
Gupta (c) mailto:gka...@vmware.com>>; Gaurav Gupta (c) 
mailto:guptagau...@vmware.com>>; Abhishek Saxena (c) 
mailto:abhisheksax...@vmware.com>>; Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>; Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:

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)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" mailto:gka...@vmware.com>>, "Gaurav 
Gupta (c)" mailto:guptagau...@vmware.com>>, "Abhishek 
Saxena (c)" mailto:abhisheksax...@vmware.com>>, 
Suresh Babu Nekkalapudi 
mailto:snekkalap...@vmware.com>>, Ramesh Tammana 
mailto: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> 
[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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) mail

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Arun Arora (c) 
Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) 
Cc: onap-discuss@lists.onap.org; Kapil Gupta (c) ; Gaurav 
Gupta (c) ; Abhishek Saxena (c) 
; Suresh Babu Nekkalapudi ; 
Ramesh Tammana 
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:

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)" mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" mailto:aroraa...@vmware.com>>, 
"PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" mailto:gka...@vmware.com>>, "Gaurav 
Gupta (c)" mailto:guptagau...@vmware.com>>, "Abhishek 
Saxena (c)" mailto:abhisheksax...@vmware.com>>, 
Suresh Babu Nekkalapudi 
mailto:snekkalap...@vmware.com>>, Ramesh Tammana 
mailto: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> 
[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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO) 
I think so…

Marco

From: "Arun Arora (c)" 
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
Cc: "onap-discuss@lists.onap.org" , "Kapil Gupta 
(c)" , "Gaurav Gupta (c)" , 
"Abhishek Saxena (c)" , Suresh Babu Nekkalapudi 
, Ramesh Tammana 
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?
Regards
Arun
On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:
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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Arun Arora (c) 
Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards
Arun
On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>> wrote:
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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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=0W0Iqz1

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO) 
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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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=659f94c93b9c5dfae02031

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO) 
Even these seems correct.

Can you verify these instructions instead?

sed -i "s/ens[0-9]*/eth0/g" /etc/network/interfaces.d/*.cfg
echo 'network: {config: disabled}' >> 
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

Please check if those files exist and if changes are applied correctly.

Thanks,
Marco

From: "Arun Arora (c)" 
Date: Monday, May 29, 2017 at 5:44 AM
To: "PLATANIA, MARCO (MARCO)" , 
"onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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/interfa

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO) 
Hi Arun,

These grub files seem OK to me. What images are you using, and what hypervisor?

My suggestion is to repeat the steps in the install file manually and see if 
some mistake arises.

Thanks,
Marco

From: "Arun Arora (c)" 
Date: Monday, May 29, 2017 at 3:25 AM
To: "PLATANIA, MARCO (MARCO)" , 
"onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
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) ; onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Arun Arora (c) 
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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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 e

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Arun Arora (c) 
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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) 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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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


mso.etc.default.grub
Description: mso.etc.default.grub


original.etc.default.grub
Description: original.etc.default.grub


robot.etc.default.grub
Description: robot.etc.default.grub


sdc.etc.default.grub
Description: sdc.etc.default.grub
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread Arun Arora (c) 
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) ; onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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 
_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: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
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>" 
mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" 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


sdc.grub.cfg
Description: sdc.grub.cfg


sdc.grub.cfg.modified
Description: sdc.grub.cfg.modified


mso.grub.cfg
Description: mso.grub.cfg


mso.grub.cfg.modified
Description: mso.grub.cfg.modified


robot.grub.cfg
Description: robot.grub.cfg


robot.grub.cfg.modified
Description: robot.grub.cfg.modified
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-26 Thread PLATANIA, MARCO (MARCO) 
Hello Arun,

Some components need to know their public IP address. This is retrieved in 
_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:  on behalf of "Arun Arora (c)" 

Date: Friday, May 26, 2017 at 8:15 AM
To: "onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
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

[onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-26 Thread Arun Arora (c) 
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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss