Re: [onap-discuss] VVP-devkit : Problem

2017-11-21 Thread Binshtok, Edan
Vagrant destroy –f doesn’t help?
Also please repull master from devkit repo. You should have the roles dir now.

On 22/11/2017, 9:26, "Moshe Hoadley"  wrote:

Hi

Unfortunately, I couldn't solve it. My conclusion is that it is a centos7 
issue.

A work-around:

- Kill the vagrant process once it's stuck and run it again. 

- Vagrant will see that the VM is already up and will skip to the next VM.

- Vagrant will again be stuck on the second VM, repeat the kill and re run 
procedure.

- Vagrant will see that 2 VMs are already up and will skip to the third VM.

- The 3rd VM is of COREOS and it doesn't get stuck.



At this point ansible starts running and fails on the missing roles folder.



Thanks

Moshe Hoadley

M 972-9-77-62712





-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Binshtok, Edan

Sent: Tuesday, November 21, 2017 8:26 PM

To: Karthik ; onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] VVP-devkit : Problem



Hi Karthik, Happy to meet you.

I’ll be glad if you can share in a couple of words who you are and from 
what company, just so we all get to know each other ☺ I’m Edan Binshtok from 
AT and I was one of the original developer which seeded the code.



Looks like a bad network issue.



  1.  Can you check there isn’t a problematic network adapter in virtualbox 
?

  2.  Did you add the “# 10.252.0.12 
coreos-01.development.vvp.example.com”
 to your known hosts?



Moshe, Sandeep, Paul, something else you can think of?



From: Karthik 

Date: Tuesday, 21 November 2017 at 17:28

To: "onap-discuss@lists.onap.org" , "Binshtok, 
Edan" 

Subject: VVP-devkit : Problem



Hi Team ,



I am using VVP/devkit project . I have all setups in my Linux environment 
(Ubuntu 16).

I followed the 
READ.ME
 file as mentioned below; # update your hosts file with the line # 10.252.0.12 
coreos-01.development.vvp.example.com

. setenv

# select the envirionment yout want from the list vagrant up watch -n5 
"kubectl get po -n kube-system"

# once all pods are running status

`bin/vvp-deploy`



When I launched vagrant up , It keeps hanging at the below line

"ops-01: Configuring and enabling network interfaces".Please refer pic1.



kubectl is fails with the below error :

Unable to connect to the server: dial tcp: lookup localhost on 
8.8.8.8:53:
 no such host



Am I missing anything ? . Can anyone help in this issue?.



___

onap-discuss mailing list

onap-discuss@lists.onap.org


https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=DzkTVPD1Equt2dF02x9f6FSCI-UPAH4TN6LMeECNRRU=gScNmxBqwre-yO4c9WBWBclNGe2qBy36JsCAwAdQtZQ=
 

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=DzkTVPD1Equt2dF02x9f6FSCI-UPAH4TN6LMeECNRRU=Jgyo1hn3WdIR2TnxsudBmbL9-5e6Fz_KNFBOGMT85ts=
  

Re: [onap-discuss] VVP-devkit : Problem

2017-11-21 Thread Moshe Hoadley
Hi
Unfortunately, I couldn't solve it. My conclusion is that it is a centos7 issue.
A work-around:
- Kill the vagrant process once it's stuck and run it again. 
- Vagrant will see that the VM is already up and will skip to the next VM.
- Vagrant will again be stuck on the second VM, repeat the kill and re run 
procedure.
- Vagrant will see that 2 VMs are already up and will skip to the third VM.
- The 3rd VM is of COREOS and it doesn't get stuck.

At this point ansible starts running and fails on the missing roles folder.

Thanks
Moshe Hoadley
M 972-9-77-62712    


-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Binshtok, Edan
Sent: Tuesday, November 21, 2017 8:26 PM
To: Karthik ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] VVP-devkit : Problem

Hi Karthik, Happy to meet you.
I’ll be glad if you can share in a couple of words who you are and from what 
company, just so we all get to know each other ☺ I’m Edan Binshtok from AT 
and I was one of the original developer which seeded the code.

Looks like a bad network issue.

  1.  Can you check there isn’t a problematic network adapter in virtualbox ?
  2.  Did you add the “# 10.252.0.12 
coreos-01.development.vvp.example.com”
 to your known hosts?

Moshe, Sandeep, Paul, something else you can think of?

From: Karthik 
Date: Tuesday, 21 November 2017 at 17:28
To: "onap-discuss@lists.onap.org" , "Binshtok, 
Edan" 
Subject: VVP-devkit : Problem

Hi Team ,

I am using VVP/devkit project . I have all setups in my Linux environment 
(Ubuntu 16).
I followed the 
READ.ME
 file as mentioned below; # update your hosts file with the line # 10.252.0.12 
coreos-01.development.vvp.example.com
. setenv
# select the envirionment yout want from the list vagrant up watch -n5 "kubectl 
get po -n kube-system"
# once all pods are running status
`bin/vvp-deploy`

When I launched vagrant up , It keeps hanging at the below line
"ops-01: Configuring and enabling network interfaces".Please refer pic1.

kubectl is fails with the below error :
Unable to connect to the server: dial tcp: lookup localhost on 
8.8.8.8:53:
 no such host

Am I missing anything ? . Can anyone help in this issue?.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [E] Re: VVP-devkit : Problem

2017-11-21 Thread Binshtok, Edan
Great, Happy to have you guys onboard.
Welcome to the Team.

Edan



From: "Kumar Skand Priya, Viswanath V" 
Date: Tuesday, 21 November 2017 at 20:47
To: "Binshtok, Edan" 
Cc: Karthik , "onap-discuss@lists.onap.org" 

Subject: Re: [E] Re: [onap-discuss] VVP-devkit : Problem

Hi Edan,

Good Day!

Karthik works in my team and we are from Verizon. We are currently exploring 
VVP in isolated lab, which isn't connected to our corporate network. Hence he 
would be using gmail to clarify his queries. Thanks for your help & glad to 
meet you.

BR,
Viswa


[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Tue, Nov 21, 2017 at 11:56 PM, Binshtok, Edan 
> wrote:
Hi Karthik, Happy to meet you.

I’ll be glad if you can share in a couple of words who you are and from what 
company, just so we all get to know each other ☺

I’m Edan Binshtok from AT and I was one of the original developer which 
seeded the code.



Looks like a bad network issue.



  1.  Can you check there isn’t a problematic network adapter in virtualbox ?

  2.  Did you add the “# 10.252.0.12 
coreos-01.development.vvp.example.com”
 to your known hosts?



Moshe, Sandeep, Paul, something else you can think of?



From: Karthik >

Date: Tuesday, 21 November 2017 at 17:28

To: "onap-discuss@lists.onap.org" 
>, "Binshtok, 
Edan" >

Subject: VVP-devkit : Problem



Hi Team ,



I am using VVP/devkit project . I have all setups in my Linux environment 
(Ubuntu 16).

I followed the 
READ.ME
 file as mentioned below;

# update your hosts file with the line

# 10.252.0.12 
coreos-01.development.vvp.example.com

. setenv

# select the envirionment yout want from the list

vagrant up

watch -n5 "kubectl get po -n kube-system"

# once all pods are running status

`bin/vvp-deploy`



When I launched vagrant up , It keeps hanging at the below line

"ops-01: Configuring and enabling network interfaces".Please refer pic1.



kubectl is fails with the below error :

Unable to connect to the server: dial tcp: lookup localhost on 
8.8.8.8:53:
 no such host



Am I missing anything ? . Can anyone help in this issue?.



___
onap-discuss mailing list
onap-discuss@lists.onap.org

Re: [onap-discuss] Service distribution WorkFlow across various sdc/mso/aai/sdnc/v Containers via SDC Gui by Ops user

2017-11-21 Thread Michael O'Brien
Gaurav,
Reviewing some mails - I noticed that myself and the rest of us did not 
respond to this one yet - I am trying not to work anymore today.
Yes, there are calls either via robot-SDC or SDC-UI-manually into AAI and 
SDNC - 1-12 and redone in 13-14 - I need to reverify MSO - the diagram is 1.0.0 
- it also need to be Gliffied for just-in-time editing
Normally I would either rerun the vFW at this point to re-verify and tail 
the logs - but I have not run the distribute fully for 2 months so beyond the 
last time I ran the full vFW 4 months ago I cannot verify (however we are 
getting very good info on the vFW reproduction so I am hoping for a trace in 
the next 144 hours.   The other re-verification would be a manual robot trace 
through the calls in InteliJ - I will verify this tomorrow as I would like to 
review some good changes new to demo.robot anyway and get back to you and 
either re-run it or trace it.  SDC had an issue 2 days ago but was fixed.

Your diligence in helping trace the vFW flow is appreciated.
Thank you
/michael

From: Gaurav Gupta (c) [mailto:guptagau...@vmware.com]
Sent: Wednesday, November 15, 2017 10:03
To: onap-discuss@lists.onap.org; Michael O'Brien 
Cc: Ramki Krishnan ; Arun Arora (c) ; 
Arunkumar Kodagi Ramachandra ; Sumit Verdi 
; Kapil Gupta (c) 
Subject: Service distribution WorkFlow across various sdc/mso/aai/sdnc/v 
Containers via SDC Gui by Ops user


 All , Michael



While chasing the issue of Service distribution via SDC Gui and using VID to 
Deploy Service failing .

There are certain dots that are missing while trying to establish due to which 
ONAP Container that issues is coming .



For example in Distribution Flow



Following are the Docker container that plays a role in Service Onboarding 
workFlow . Can this be confirmed ? .



sdc-fe container -> msotestlab_1

sdc-fe container ->  aai_resource

sdc-fe container  ->  sdnc-ueblistener



Please note that is based on the information on the below links .

https://wiki.onap.org/pages/viewpage.action?pageId=3246170

https://wiki.onap.org/display/DW/Tutorial%3A+Verifying+and+Observing+a+deployed+Service+Instance#Tutorial:VerifyingandObservingadeployedServiceInstance-vFirewallFlow
Tutorial: Verifying and Observing a deployed Service 
...
wiki.onap.org
How many of the 10 TG streams is running is TBD? TBD: the exact nature of what 
enabling 5 of the 10 TGs is? TBD: what exactly is the correlation between the 
SEC ...


thanks in advance for helping on this  .



thanks and regards

gaurav
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [ONAP Helpdesk #45257] [integration] Issue-ID check

2017-11-21 Thread Jessica Wagantall via RT
This is now in place. 

thanks!
Jess

On Tue Nov 21 13:22:26 2017, jwagantall wrote:
> This change is scheduled to be merged today at 2:00pm PDT
> 
> Thanks!
> Jess
> 
> On Mon Oct 23 19:37:02 2017, jwagantall wrote:
> > We were trying to implement it quite few time ago, but it conflicted
> > with the peak of the time in which the devs were doing their changes
> > before the code freeze at a very rapid flow.
> > 
> > I synced with Gildas and he suggested we move this improvement to Nov
> > 16 and for now to start educating the devs about this restriction by
> > adding comments in their gerrit changes.
> > 
> > I agree with Gildas that this enforcement could have caused quite a
> > bit of frustration to developers during this time, but this could be
> > welcomed after Nov 16.
> > 
> > On Mon Oct 23 11:07:04 2017, gary.i...@huawei.com wrote:
> > > I thought that this in fact had already been implemented (the
> > > capitalization-sensitive check for "Issue-ID").
> > >
> > > Thanks,
> > > Gary
> > >
> > > -Original Message-
> > >  From: Kenny Paul via RT [mailto:onap-
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Sunday, October 22, 2017 7:51 PM
> > > To: Gary Wu 
> > > Cc: onap-discuss@lists.onap.org
> > > Subject: [ONAP Helpdesk #45257] [integration] Issue-ID check
> > >
> > > Gary, looking for conformation that this is in fact something that
> > > you
> > > want to put on hold until after the release.
> > >
> > > Thanks!
> > > -kenny
> > >
> > >
> > >
> > > On Thu Oct 12 15:53:22 2017, jwagantall wrote:
> > > > Dear Team,
> > > >
> > > > just a small update on this. After discussing with Gildas, we
> > > > thought
> > > > that this enforcement will create a little bit of obstacles for
> > > > developers since we are so close to our release goals.
> > > >
> > > > We are planning to merge this change after Nov 16 when we have more
> > > > flexibility.
> > > >
> > > > Thanks!
> > > > Jess
> > > >
> > > > On Thu Sep 21 16:21:38 2017, agrimberg wrote:
> > > > > On Sat Sep 02 11:19:32 2017, frank.obr...@amdocs.com wrote:
> > > > > > Gary,
> > > > > > Good point, the pre-commit script is cAP agnostic but the
> > > > > > links
> > > > > > are not.
> > > > > > I have also noticed that periodically some jiras will not
> > > > > > show
> > > > > > their gerrit reviews - even though they were previously linked.
> > > > > > The linking between confluence and jira is also currently
> > > > > >  broken in the jira-to-confluence direction but not the reverse
> > > > > > since April.
> > > > >
> > > > > Greetings folks,
> > > > >
> > > > > If you see that JIRA is not showing you any changes that you know
> > > > > exist try doing the following when looking at the JIRA issue:
> > > > >
> > > > > --[cut]--
> > > > >  Select the down arrow next to the Gerrit Reviews Make sure that
> > > > >  'Show All Reviews' is selected If it is, switch it to 'Show Open
> > > > > Reviews' and then back
> > > > > --[cut]--
> > > > >
> > > > > What happens is that sometimes the Gerrit plugin disconnects from
> > > > > the Gerrit server and toggling those settings generally forces it
> > > > > to
> > > > > reconnect and refresh any caches that it has.
> > > > >
> > > > > > Sent this to the group on the 18th
> > > > > >Watch your commit message case for JIRA links - the "Issue-
> > > > > > ID"
> > > > > > is
> > > > > > case sensitive
> > > > > > Only a "Issue-ID:" prefix will link gerrit reviews to jira
> > > > > > -
> > > > > >  cases like "issue-id, Issue-Id" will fail to link until the LF
> > > > > > makes their pre-commit check case-insensitive
> > > > > >
> > > > > > https://wiki.onap.org/display/DW/Commit+Messages#CommitMessages-
> > > > > > CommitStructure
> > > > >
> > > > > I now have a change in for review, which will require a Gerrit
> > > > > restart to take effect when it's rolled out, which will enforce
> > > > > the
> > > > > following regex for the JIRA check:
> > > > >
> > > > > ^Issue-ID: ([A-Z][A-Z0-9]{1-9}-\d+)
> > > > >
> > > > > This means that it will _enforce_ that JIRA issues start with
> > > > > 'Issue-
> > > > > ID: ', yes a _single_ space will be required. NOTE: we tell folks
> > > > > that this needs to be in the footer, but technically it can be
> > > > > anywhere and pass as we have no ability to the check to only
> > > > > operate
> > > > > on the footer, but honestly, it looks tacky if it isn't properly
> > > > > in
> > > > > the footer ;)
> > > > >
> > > > > When this change rolls out, another comment linking change will
> > > > > also
> > > > > roll out which will enable Gerrit change IDs to be relinked back
> > > > > into Gerrit meaning that people will be able to leave notes in
> > > > > the
> > > > > comments such as:
> > > > >
> > > > > --[cut]--
> > > > >  This change requires I4937bfdbecc4aec2363497aba12b9c0389cf2c90
> > > > > from
> > > > > repo foo to work correctly.
> > > > > --[cut]--
> > > > >
> > > > > And the 

Re: [onap-discuss] [AAI] Modelling physical hardware in ONAP AAI

2017-11-21 Thread Michael Still
Thanks so much to both of you for your very helpful comments. I'm going to
take some time today to digest them and then will come back with further
questions.

Thanks again,
Michael

On Tue, Nov 21, 2017 at 5:29 AM, FORSYTH, JAMES  wrote:

> Hi, Michael,
>
>
>
> According to AAI SMEs, this is the way to do it:
>
>
>
> 1. SDN switch by Pnf
>
> 2. SDN switch port by p-interface and l-interface(s)
>
> 3. Physical links and logical links between SDN port switches by
> physicallinks and logicallinks
>
> 4. SDN switch locations by complexes.
>
> 5. If the SDN control plane is segmented (partitioned, sharded), perhaps
> cloud-region can be used to represent the segments. Cloud-region is meant
> to represent the segmentation of the cloud management plane, so if the
> boundaries of SDN control and cloud management plane do not coincide, we
> may need some further modeling.
>
> 6. Since the ONAP model can change in the future, it would be good if the
> modelers of the SDN switches  network bring their solution to ONAP.
>
>
>
> Thanks,
>
> jimmy
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Michael Still
> *Sent:* Sunday, November 19, 2017 11:29 PM
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] [AAI] Modelling physical hardware in ONAP AAI
>
>
>
> Hi,
>
>
>
> I have a use case where we are managing a network of SDN switches. We
> would like to use ONAP AAI to handle the inventory management for ports on
> these switches, as well as modelling which switches are in what locations
> (and how they interconnect with each other).
>
>
>
> I haven't been able to find any examples of how I would do such a thing in
> AAI, although its entirely possible that I've missed something obvious.
> Does the team have any pointers on getting started?
>
>
>
> Thanks,
>
> Michael
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [integration]Please reschedule Integration Weekly meeting

2017-11-21 Thread Yunxia Chen
Sorry, I mean:

Wednesday 6:30AM to 7:30AM PST.

Regards,

Helen Chen

From:  on behalf of Helen Chen 00725961 

Date: Tuesday, November 21, 2017 at 2:52 PM
To: Kenny Paul , onap-discuss 

Subject: [onap-discuss] [integration]Please reschedule Integration Weekly 
meeting

Hi, Kenny,
Please help reschedule Integration weekly meeting to Wednesday 6:30 PM to 
7:30PM from next week.

Regards,
Helen Chen

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [integration]Please reschedule Integration Weekly meeting

2017-11-21 Thread Yunxia Chen
Hi, Kenny,
Please help reschedule Integration weekly meeting to Wednesday 6:30 PM to 
7:30PM from next week.

Regards,
Helen Chen

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [it-infrastructure-alerts] ONAP Gerrit 15 min downtime 2017-11-21 @ 14:00 PDT (22:00 UTC)

2017-11-21 Thread Jessica Wagantall
Dear ONAP team,

This is now completed successfully.

Thanks!
Jess

On Tue, Nov 21, 2017 at 10:17 AM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> What: The Linux Foundation will be performing a brief Gerrit restart.
> Jenkins
> will be set into quiet mode during that time to avoid clone failures.
>
> When: Tuesday, November 21st @ 14:00 (2017-11-21 @ 22:00 UTC)
>
> Why: LF will be enabling more stringent JIRA linking in gerrit.
> (Specifically, enforcing the usage of "Issue-ID: " to link a JIRA in the
> commit message)
>
> Impact: Jenkins will be set into quiet mode to avoid failed jobs due to
> gerrit not being
> accessible. Any jobs in the queue will be paused for a brief time until
> the gerrit restart is
> completed. Gerrit will be down for about 15 minutes.
>
> Notices will be posted to the mailing lists at the start and end of the
> maintenance.
>
> Jess
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [vnfrqts] project meeting notes posted

2017-11-21 Thread WRIGHT, STEVEN A
Today's VNFRQTS project meeting notes posted at: 
https://wiki.onap.org/pages/viewpage.action?pageId=10783616


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com
www.linkedin.com/in/drstevenawright/

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Invitation: [coe] Weekly @ Weekly from 6pm to 7pm on Thursday (PST) (onap-discuss@lists.onap.org)

2017-11-21 Thread kpaul
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171130T18
DTEND;TZID=America/Los_Angeles:20171130T19
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171121T214313Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:20l550o454u673n8qit0g4t...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=isaku yamahata;X-NUM-GUESTS=0:mailto:isaku.yamah...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20171121T214312Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 5 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/961993336\n\nOr iPhone one-tap :\nUS: +16465588656\,\,961993336#  o
 r +16699006833\,\,961993336# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location):\nUS: +1 646 558 865
 6  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (T
 oll Free)\nMeeting ID: 961 993 336\nInternational numbers available
 : https://zoom.us/zoomconference?m=NyDGIiAbPmpKt_zpBGMCPXUZ8OTi9LqS\n\n\n\n
 -::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~::~:~::-\nPlease do not edit this section of the description.\n\nView y
 our event at https://www.google.com/calendar/event?action=VIEW=MjBsNTUw
 bzQ1NHU2NzNuOHFpdDBnNHRucDAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbG
 ludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlb
 mRhci5nb29nbGUuY29tZmMxZTE2OTBmZmEzMWNjMTYwZjU3ZjQwN2Q3NTJjZWM3ZWUyYmZlZA
 tz=America/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20171121T214313Z
LOCATION:https://zoom.us/j/961993336
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[coe] Weekly
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Canceled event: [aai] Weekly @ Thu Nov 23, 2017 6am - 7am (PST) (onap-discuss@lists.onap.org)

2017-11-21 Thread kpaul
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171123T06
DTEND;TZID=America/Los_Angeles:20171123T07
DTSTAMP:20171121T212608Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:n2l5brkbr8kmetnn8a5k0s77ek_r20170810t130...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jf
 2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20171123T06
CREATED:20170628T235038Z
DESCRIPTION:Hi there\, \n\nUTC: 1:00AM\, Bejing: 09:00 PM\, Eastern: 09:00 
 AM\, Pacific: 06:00 AM\n\nONAP Meeting 2 is inviting you to a scheduled Zoo
 m meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us
 /j/403219274\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,403219274# or
  +16465588656\,\,403219274#\n\nOr Telephone:\nDial: +1 408 638 0968 (US
  Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n  
   +1 877 369 0926 (US Toll Free)\nMeeting ID: 403 219 274\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=0tliieyuLYiDQ83E-
 kQHw86QJZABgcPF\n\n
LAST-MODIFIED:20171121T212608Z
LOCATION:https://zoom.us/j/403219274
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[aai] Weekly
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] SDNC VM & Docker Containers Unstable

2017-11-21 Thread FREEMAN, BRIAN D
Remove unknown.log and restart docker container - the disk is full on the VM 
from unknown.log growing out of bounds.
We are trying to figure out what triggers it.

Brian

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Tuesday, November 21, 2017 3:09 PM
To: onap-discuss ; aroraa...@vmware.com
Subject: Re: [onap-discuss] SDNC VM & Docker Containers Unstable

What's your env look like?
Helen Chen


Sent from HUAWEI AnyOffice
From: Arun Arora (c)
To: onap-discuss;
Cc: Michael O'Brien; Ramki Krishnan; Ramesh Tammana; Yunxia Chen;
Subject: SDNC VM & Docker Containers Unstable
Time: 2017-11-21 05:59:44


Hi All,

We are working to bring up the vFW demo. For that we are using demo.sh init to 
create customer and distribute service. After that using VID for further steps.

While doing so we have seen the below 3 issues.
1. Space of SDNC VM's '/' mount point fills completely at some point
2. Docker containers are exiting randomly. We see mysql, dgbuilder and 
admportal containers exiting at varied instances

3. admportal becomes unreachable

1. Received "refused to connect" error

2. On debugging further found that start_portal.sh is stuck at the 
following, which was not seen before (Please see start_install.png):

+ cd /opt/onap/sdnc/admportal
+ npm install
npm WARN deprecated node-uuid@1.4.8: Use uuid module 
instead
loadDep:type-is > networ / 
|---|

Has anyone seen these issues before? Really appreciate any pointers to solve 
these issues.

Following JIRA ticket is raised for the same:
https://jira.onap.org/browse/SDNC-203


Thanks,
Arun




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Canceled event: [policy] Weekly @ Wed Nov 22, 2017 5am - 6am (PST) (onap-discuss@lists.onap.org)

2017-11-21 Thread kpaul
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171122T05
DTEND;TZID=America/Los_Angeles:20171122T06
DTSTAMP:20171121T204603Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:3peha7dllj5vnqu92u70qjoq10_r20170809t120...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=pd
 rag...@research.att.com;X-NUM-GUESTS=0:mailto:pdrag...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20171122T05
CLASS:PUBLIC
CREATED:20170601T195143Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 3 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/463561265\n\nOr iPhone one-tap (US Toll):  +16465588656\,463561265# or 
 +14086380968\,463561265#\n\nOr Telephone:\nDial: +1 646 558 8656 (US To
 ll) or +1 408 638 0968 (US Toll)\nMeeting ID: 463 561 265\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=g-6zp_3xtuteVvzJy
 DLRVKWXKdzg-VTA\n\n
LAST-MODIFIED:20171121T204602Z
LOCATION:https://zoom.us/j/463561265
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[policy] Weekly
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] SDNC VM & Docker Containers Unstable

2017-11-21 Thread Yunxia Chen
What’s your env look like?
Helen Chen


Sent from HUAWEI AnyOffice
From: Arun Arora (c)
To: onap-discuss;
Cc: Michael O'Brien; Ramki Krishnan; Ramesh Tammana; Yunxia Chen;
Subject: SDNC VM & Docker Containers Unstable
Time: 2017-11-21 05:59:44



Hi All,

We are working to bring up the vFW demo. For that we are using demo.sh init to 
create customer and distribute service. After that using VID for further steps.

While doing so we have seen the below 3 issues.

  1.  Space of SDNC VM's '/' mount point fills completely at some point
  2.  Docker containers are exiting randomly. We see mysql, dgbuilder and 
admportal containers exiting at varied instances
  3.  admportal becomes unreachable

1. Received "refused to connect" error

2. On debugging further found that start_portal.sh is stuck at the 
following, which was not seen before (Please see start_install.png):

+ cd /opt/onap/sdnc/admportal
+ npm install
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
loadDep:type-is > networ / 
|---|

Has anyone seen these issues before? Really appreciate any pointers to solve 
these issues.

Following JIRA ticket is raised for the same:
https://jira.onap.org/browse/SDNC-203


Thanks,
Arun




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [ONAP Helpdesk #48446] ONAP Meeting Cancelation request for DCAE Weekly meeting 11/23

2017-11-21 Thread Kenny Paul via RT
11/23 meeting cxld.
-kenny

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Canceled event: [dcaegen2] Weekly Meeting @ Thu Nov 23, 2017 6am - 7am (PST) (onap-discuss@lists.onap.org)

2017-11-21 Thread kpaul
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171123T06
DTEND;TZID=America/Los_Angeles:20171123T07
DTSTAMP:20171121T192415Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:nor7q8ipbsespapn486pkrtta4_r20170810t130...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lj
 i...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
RECURRENCE-ID;TZID=America/Los_Angeles:20171123T06
CLASS:PUBLIC
CREATED:20170616T164806Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/824147956\n\nOr iPhone one-tap (US Toll):  +14086380968\,824147956# or 
 +16465588656\,824147956#\n\nOr Telephone:\nDial: +1 408 638 0968 (US To
 ll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n+
 1 877 369 0926 (US Toll Free)\nMeeting ID: 824 147 956\nInternation
 al numbers available: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmek
 dG0WHlAnv3Zp\n\n
LAST-MODIFIED:20171121T192415Z
LOCATION:https://zoom.us/j/824147956
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[dcaegen2] Weekly Meeting
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] Canceled event: [ccsdk] Weekly Meeting @ Tue Nov 21, 2017 6pm - 7pm (PST) (onap-discuss@lists.onap.org)

2017-11-21 Thread kpaul
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171121T18
DTEND;TZID=America/Los_Angeles:20171121T19
DTSTAMP:20171121T192027Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:lu2gvbgp4nmn6ado92d026l1cc_r20170809t010...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jf
 lu...@research.att.com;X-NUM-GUESTS=0:mailto:jflu...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lp
 ar...@amdocs.com;X-NUM-GUESTS=0:mailto:lpar...@amdocs.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=hu
 an.liny...@zte.com.cn;X-NUM-GUESTS=0:mailto:huan.liny...@zte.com.cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ma
 rcus.willi...@intel.com;X-NUM-GUESTS=0:mailto:marcus.willi...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ri
 tu.s...@intel.com;X-NUM-GUESTS=0:mailto:ritu.s...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=hg
 4...@att.com;X-NUM-GUESTS=0:mailto:hg4...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=zh
 ang.maope...@zte.com.cn;X-NUM-GUESTS=0:mailto:zhang.maope...@zte.com.cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=dt
 imo...@att.com;X-NUM-GUESTS=0:mailto:dtimo...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ar
 un.ye...@huawei.com;X-NUM-GUESTS=0:mailto:arun.ye...@huawei.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=fe
 ng.j...@zte.com.cn;X-NUM-GUESTS=0:mailto:feng.j...@zte.com.cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ch
 eng.l...@huawei.com;X-NUM-GUESTS=0:mailto:cheng.l...@huawei.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jh
 2...@att.com;X-NUM-GUESTS=0:mailto:jh2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ya
 ngyan...@chinamobile.com;X-NUM-GUESTS=0:mailto:yangyan...@chinamobile.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=wu
 .li...@zte.com.cn;X-NUM-GUESTS=0:mailto:wu.li...@zte.com.cn
RECURRENCE-ID;TZID=America/Los_Angeles:20171121T18
CLASS:PUBLIC
CREATED:20170626T163301Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 6 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/826248894\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,826248894# o
 r +16465588656\,\,826248894#\n\nOr Telephone:\nDial: +1 408 638 0968 (U
 S Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 826 248 894\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=NVGUf0EROBhf9FVP
 H4nxUC0b1KnSta53\n\n
LAST-MODIFIED:20171121T192026Z
LOCATION:https://zoom.us/j/826248894
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[ccsdk] Weekly Meeting
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [ccsdk] Meeting cancelled 11/21

2017-11-21 Thread TIMONEY, DAN
CCSDK team,

I would like to cancel this week’s CCSDK project meeting.  We’ll meet again 
next week at the usual time/bridge.

Thanks!
Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [E] Re: VVP-devkit : Problem

2017-11-21 Thread Kumar Skand Priya, Viswanath V via onap-discuss
Hi Edan,

Good Day!

Karthik works in my team and we are from Verizon. We are currently
exploring VVP in isolated lab, which isn't connected to our corporate
network. Hence he would be using gmail to clarify his queries. Thanks for
your help & glad to meet you.

BR,
Viswa




Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Tue, Nov 21, 2017 at 11:56 PM, Binshtok, Edan 
wrote:

> Hi Karthik, Happy to meet you.
>
> I’ll be glad if you can share in a couple of words who you are and from
> what company, just so we all get to know each other ☺
>
> I’m Edan Binshtok from AT and I was one of the original developer which
> seeded the code.
>
>
>
> Looks like a bad network issue.
>
>
>
>   1.  Can you check there isn’t a problematic network adapter in
> virtualbox ?
>
>   2.  Did you add the “# 10.252.0.12 coreos-01.development.vvp.example.com
>  development.vvp.example.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_
> QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=D1Kpn0JKEKYKQ4Uw-
> 5KS9O0Z8LdD2ncTKA3PFYjaFUw=L9rX6Yxf2t4-5P_6m3kkUL07s1PPdilymlMduXpMu6E&
> e=>” to your known hosts?
>
>
>
> Moshe, Sandeep, Paul, something else you can think of?
>
>
>
> From: Karthik 
>
> Date: Tuesday, 21 November 2017 at 17:28
>
> To: "onap-discuss@lists.onap.org" ,
> "Binshtok, Edan" 
>
> Subject: VVP-devkit : Problem
>
>
>
> Hi Team ,
>
>
>
> I am using VVP/devkit project . I have all setups in my Linux environment
> (Ubuntu 16).
>
> I followed the READ.ME 3A__READ.ME=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_
> QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=D1Kpn0JKEKYKQ4Uw-
> 5KS9O0Z8LdD2ncTKA3PFYjaFUw=lN1oK148aBEhzeXklpDtPQiGggRitZ
> 9NKQcinRUbJ94=> file as mentioned below;
>
> # update your hosts file with the line
>
> # 10.252.0.12 coreos-01.development.vvp.example.com urldefense.proofpoint.com/v2/url?u=http-3A__coreos-2D01.
> development.vvp.example.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_
> QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=D1Kpn0JKEKYKQ4Uw-
> 5KS9O0Z8LdD2ncTKA3PFYjaFUw=L9rX6Yxf2t4-5P_6m3kkUL07s1PPdilymlMduXpMu6E&
> e=>
>
> . setenv
>
> # select the envirionment yout want from the list
>
> vagrant up
>
> watch -n5 "kubectl get po -n kube-system"
>
> # once all pods are running status
>
> `bin/vvp-deploy`
>
>
>
> When I launched vagrant up , It keeps hanging at the below line
>
> "ops-01: Configuring and enabling network interfaces".Please refer pic1.
>
>
>
> kubectl is fails with the below error :
>
> Unable to connect to the server: dial tcp: lookup localhost on 8.8.8.8:53<
> https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__8.8.8.8-3A53=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_
> QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=D1Kpn0JKEKYKQ4Uw-
> 5KS9O0Z8LdD2ncTKA3PFYjaFUw=jM_p20wLvmpqvlSFgjcA3xKruCrGdJp1q
> EIiJVUagks=>: no such host
>
>
>
> Am I missing anything ? . Can anyone help in this issue?.
>
>
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=
> udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=9F3pNUkzjE-
> 2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ=b3kuQL-
> kk0YFKp3nSEQvT28jtUqhVi_elPutPsQ29go=hEkzkA9aVtmJZqD15PDaq2IyUYxRpS
> iCEX8MxHuhWpY=
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [ONAP Helpdesk #45257] [integration] Issue-ID check

2017-11-21 Thread Jessica Wagantall via RT
This change is scheduled to be merged today at 2:00pm PDT

Thanks!
Jess

On Mon Oct 23 19:37:02 2017, jwagantall wrote:
> We were trying to implement it quite few time ago, but it conflicted
> with the peak of the time in which the devs were doing their changes
> before the code freeze at a very rapid flow.
> 
> I synced with Gildas and he suggested we move this improvement to Nov
> 16 and for now to start educating the devs about this restriction by
> adding comments in their gerrit changes.
> 
> I agree with Gildas that this enforcement could have caused quite a
> bit of frustration to developers during this time, but this could be
> welcomed after Nov 16.
> 
> On Mon Oct 23 11:07:04 2017, gary.i...@huawei.com wrote:
> > I thought that this in fact had already been implemented (the
> > capitalization-sensitive check for "Issue-ID").
> >
> > Thanks,
> > Gary
> >
> > -Original Message-
> >  From: Kenny Paul via RT [mailto:onap-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Sunday, October 22, 2017 7:51 PM
> > To: Gary Wu 
> > Cc: onap-discuss@lists.onap.org
> > Subject: [ONAP Helpdesk #45257] [integration] Issue-ID check
> >
> > Gary, looking for conformation that this is in fact something that
> > you
> > want to put on hold until after the release.
> >
> > Thanks!
> > -kenny
> >
> >
> >
> > On Thu Oct 12 15:53:22 2017, jwagantall wrote:
> > > Dear Team,
> > >
> > > just a small update on this. After discussing with Gildas, we
> > > thought
> > > that this enforcement will create a little bit of obstacles for
> > > developers since we are so close to our release goals.
> > >
> > > We are planning to merge this change after Nov 16 when we have more
> > > flexibility.
> > >
> > > Thanks!
> > > Jess
> > >
> > > On Thu Sep 21 16:21:38 2017, agrimberg wrote:
> > > > On Sat Sep 02 11:19:32 2017, frank.obr...@amdocs.com wrote:
> > > > > Gary,
> > > > > Good point, the pre-commit script is cAP agnostic but the
> > > > > links
> > > > > are not.
> > > > > I have also noticed that periodically some jiras will not
> > > > > show
> > > > > their gerrit reviews - even though they were previously linked.
> > > > > The linking between confluence and jira is also currently
> > > > >  broken in the jira-to-confluence direction but not the reverse
> > > > > since April.
> > > >
> > > > Greetings folks,
> > > >
> > > > If you see that JIRA is not showing you any changes that you know
> > > > exist try doing the following when looking at the JIRA issue:
> > > >
> > > > --[cut]--
> > > >  Select the down arrow next to the Gerrit Reviews Make sure that
> > > >  'Show All Reviews' is selected If it is, switch it to 'Show Open
> > > > Reviews' and then back
> > > > --[cut]--
> > > >
> > > > What happens is that sometimes the Gerrit plugin disconnects from
> > > > the Gerrit server and toggling those settings generally forces it
> > > > to
> > > > reconnect and refresh any caches that it has.
> > > >
> > > > > Sent this to the group on the 18th
> > > > >Watch your commit message case for JIRA links - the "Issue-
> > > > > ID"
> > > > > is
> > > > > case sensitive
> > > > > Only a "Issue-ID:" prefix will link gerrit reviews to jira
> > > > > -
> > > > >  cases like "issue-id, Issue-Id" will fail to link until the LF
> > > > > makes their pre-commit check case-insensitive
> > > > >
> > > > > https://wiki.onap.org/display/DW/Commit+Messages#CommitMessages-
> > > > > CommitStructure
> > > >
> > > > I now have a change in for review, which will require a Gerrit
> > > > restart to take effect when it's rolled out, which will enforce
> > > > the
> > > > following regex for the JIRA check:
> > > >
> > > > ^Issue-ID: ([A-Z][A-Z0-9]{1-9}-\d+)
> > > >
> > > > This means that it will _enforce_ that JIRA issues start with
> > > > 'Issue-
> > > > ID: ', yes a _single_ space will be required. NOTE: we tell folks
> > > > that this needs to be in the footer, but technically it can be
> > > > anywhere and pass as we have no ability to the check to only
> > > > operate
> > > > on the footer, but honestly, it looks tacky if it isn't properly
> > > > in
> > > > the footer ;)
> > > >
> > > > When this change rolls out, another comment linking change will
> > > > also
> > > > roll out which will enable Gerrit change IDs to be relinked back
> > > > into Gerrit meaning that people will be able to leave notes in
> > > > the
> > > > comments such as:
> > > >
> > > > --[cut]--
> > > >  This change requires I4937bfdbecc4aec2363497aba12b9c0389cf2c90
> > > > from
> > > > repo foo to work correctly.
> > > > --[cut]--
> > > >
> > > > And the I4937bfdbecc4aec2363497aba12b9c0389cf2c90 would be
> > > > properly
> > > > linked to the other change. This makes those sorts of comments
> > > > more
> > > > bullet proof to change should we have to do rebuilds of the
> > > > Gerrit
> > > > system or migrate repositories to a different one in the future
> > > > where the short change number would end up changing.
> > > >

Re: [onap-discuss] [vvp] - missing roles directory

2017-11-21 Thread Binshtok, Edan
Weird .gitignore behavior.
Try now should be OK, the repo is devkit btw.

Here is the commit that fixed it - 
https://gerrit.onap.org/r/#/c/24741/
its already merged.

for some reason this gitignore rules didn’t work:
```
ansible/roles/*
 !ansible/roles/ansible-ice-templates/
 !ansible/roles/ansible-ice-volumes/
 !ansible/roles/ansible-vvp-bootstrap/
```
it didn’t catch the ! rules and ignored all dirs..
Can you guys see something I’m missing?
In the end i created a new rule for “ansible/roles/ceph*” but still, I’m 
wondering what I did wrong.

Also I’ve added a demo .vault_password file which needs to be changed on each 
deployment.

On 21/11/2017, 18:21, "Moshe Hoadley"  wrote:

Hi

The ' ansible-vvp-volumes' folder is still not there.



Thanks

Moshe Hoadley

M 972-9-77-62712







-Original Message-

From: Binshtok, Edan [mailto:eb5...@intl.att.com] 

Sent: Tuesday, November 21, 2017 1:49 PM

To: Moshe Hoadley ; Sandeep Shah2 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - missing roles directory



Hi Moshe nice find I’ve upload the missing dir.

Please repull from repo and try again.



On 20/11/2017, 16:29, "Moshe Hoadley"  wrote:



Hi



The folder 'ansible-vvp-voluems' is missing in the 'devkit' project.



Expected under:



../vvp/devkit/ansible/roles







Note that a different folder named 'ansible-vvp-bootstrap' is present 
in this location.







Thanks



Moshe Hoadley



972-9-77-62712







This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,



you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=81E_5Q_Vgr6eKk1rlxu-8C0b1-OxHnw8e3nmxa8Yw0M=6OCgugsDMm9arbhzP-zrS6tP-3THDsF-XErUykcDpFM=
  






This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=PvweXeyDedvD-kb5T4BZ04kRFtGUe3sZc5mNoUNEH2o=iga52LBkP4gFW9Nc0wdRZLDYI7aipavG2SQ0Q1OJUOU=
  



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [it-infrastructure-alerts] ONAP Gerrit 15 min downtime 2017-11-21 @ 14:00 PDT (22:00 UTC)

2017-11-21 Thread Jessica Wagantall
What: The Linux Foundation will be performing a brief Gerrit restart.
Jenkins
will be set into quiet mode during that time to avoid clone failures.

When: Tuesday, November 21st @ 14:00 (2017-11-21 @ 22:00 UTC)

Why: LF will be enabling more stringent JIRA linking in gerrit.
(Specifically, enforcing the usage of "Issue-ID: " to link a JIRA in the
commit message)

Impact: Jenkins will be set into quiet mode to avoid failed jobs due to
gerrit not being
accessible. Any jobs in the queue will be paused for a brief time until the
gerrit restart is
completed. Gerrit will be down for about 15 minutes.

Notices will be posted to the mailing lists at the start and end of the
maintenance.

Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] ONAP Meeting Cancelation request for DCAE Weekly meeting 11/23

2017-11-21 Thread JI, LUSHENG (LUSHENG)
Dear ONAP Helpdesk,

Please cancel DCAE Weekly meeting on Nov 23, 2017 at 2-3PM GMT (9-10AM US EST, 
6-7AM US PST, 10-11PM China CST…) due to major holiday observed.

Thanks,
Lusheng Ji
DCAE PTL

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] [policy] Policy weekly meeting on 11/22/2017 is cancelled

2017-11-21 Thread DRAGOSH, PAMELA L (PAM)
Request submitted through wiki – but still waiting for the calendar 
cancellation to be sent.

We will resume after a week of holiday and begin planning the Beijing Release.

Thanks!

Pam Dragosh
ONAP Policy PTL
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [vvp] - missing roles directory

2017-11-21 Thread Moshe Hoadley
Hi
The ' ansible-vvp-volumes' folder is still not there.

Thanks
Moshe Hoadley
M 972-9-77-62712    



-Original Message-
From: Binshtok, Edan [mailto:eb5...@intl.att.com] 
Sent: Tuesday, November 21, 2017 1:49 PM
To: Moshe Hoadley ; Sandeep Shah2 
; onap-discuss@lists.onap.org
Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 
Subject: Re: [onap-discuss] [vvp] - missing roles directory

Hi Moshe nice find I’ve upload the missing dir.
Please repull from repo and try again.

On 20/11/2017, 16:29, "Moshe Hoadley"  wrote:

Hi

The folder 'ansible-vvp-voluems' is missing in the 'devkit' project.

Expected under:

../vvp/devkit/ansible/roles



Note that a different folder named 'ansible-vvp-bootstrap' is present in 
this location.



Thanks

Moshe Hoadley

972-9-77-62712



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=81E_5Q_Vgr6eKk1rlxu-8C0b1-OxHnw8e3nmxa8Yw0M=6OCgugsDMm9arbhzP-zrS6tP-3THDsF-XErUykcDpFM=
  



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [vvp] - missing roles directory

2017-11-21 Thread Sandeep Shah2
Hi Edan - which repo do I need to pull form? I do not see a missing directory 
that you have uploaded to master in gerrit? Or I need to wait till your update 
gets merged into master repo?


Thanks!

-Original Message-
From: Binshtok, Edan [mailto:eb5...@intl.att.com] 
Sent: Tuesday, November 21, 2017 5:49 AM
To: Moshe Hoadley; Sandeep Shah2; onap-discuss@lists.onap.org
Cc: SUNDELOF, ERIK; MCGOLDRICK, PAUL
Subject: Re: [onap-discuss] [vvp] - missing roles directory

Hi Moshe nice find I’ve upload the missing dir.
Please repull from repo and try again.

On 20/11/2017, 16:29, "Moshe Hoadley"  wrote:

Hi

The folder 'ansible-vvp-voluems' is missing in the 'devkit' project.

Expected under:

../vvp/devkit/ansible/roles



Note that a different folder named 'ansible-vvp-bootstrap' is present in 
this location.



Thanks

Moshe Hoadley

972-9-77-62712



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=81E_5Q_Vgr6eKk1rlxu-8C0b1-OxHnw8e3nmxa8Yw0M=6OCgugsDMm9arbhzP-zrS6tP-3THDsF-XErUykcDpFM=
  





Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] Request to consider reschedule the weekly calls for DST time changes

2017-11-21 Thread Kenny Paul
Hi Lingli,

that is on my action item list from last week’s meeting.

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Nov 20, 2017, at 5:45 PM, Lingli Deng  wrote:
> 
> Hi Kenny and Mazin,
>  
> As a result of the DST time change, the current time slot for ONAP calls are 
> technically one-hour later for regions that does not follow the practice in 
> winter, like China.
> Hence a lot of them, including TSC weekly call, are now spanning after 
> mid-night.
> As we requested last week on the TSC call, would it be possible to reschedule 
> the weekly calls 30 minutes earlier, so that people could share the burden of 
> accommodating the change?
>  
> Thanks,
> Lingli

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


[onap-discuss] SDNC VM & Docker Containers Unstable

2017-11-21 Thread Arun Arora (c)
Hi All,

We are working to bring up the vFW demo. For that we are using demo.sh init to 
create customer and distribute service. After that using VID for further steps.

While doing so we have seen the below 3 issues.

  1.  Space of SDNC VM's '/' mount point fills completely at some point
  2.  Docker containers are exiting randomly. We see mysql, dgbuilder and 
admportal containers exiting at varied instances
  3.  admportal becomes unreachable

1. Received "refused to connect" error

2. On debugging further found that start_portal.sh is stuck at the 
following, which was not seen before (Please see start_install.png):

+ cd /opt/onap/sdnc/admportal
+ npm install
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
loadDep:type-is > networ / 
|---|

Has anyone seen these issues before? Really appreciate any pointers to solve 
these issues.

Following JIRA ticket is raised for the same:
https://jira.onap.org/browse/SDNC-203


Thanks,
Arun




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [vvp] - deployment

2017-11-21 Thread Binshtok, Edan
BTW: We had a similar problem and after closing the other VM and making sure 
/etc/hosts file is updated with “10.252.0.12 
coreos-01.development.vvp.example.com” it worked fine.
Also make sure you are not blocking any network traffic which is needed to 
downloads .

On 21/11/2017, 13:49, "Binshtok, Edan"  wrote:

Hi Moshe did you get pass this?
Please share.

On 20/11/2017, 15:24, "Moshe Hoadley"  wrote:

More info:

This is the command vagrant gets stuck on:

INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth2 >> 
/etc/sysconfig/network-scripts/ifcfg-eth2



if command -v nmcli &>/dev/null; then

  if command -v systemctl &>/dev/null && systemctl -q is-enabled 
NetworkManager &>/dev/null; then

nmcli c reload eth2

  elif command -v service &>/dev/null && service NetworkManager status 
&>/dev/null; then

nmcli c reload eth2

  fi

fi



/sbin/ifdown eth2

/sbin/ifup eth2



rm -f /tmp/vagrant-network-entry_eth2

 (sudo=true)



Thanks

Moshe Hoadley

M 972-9-77-62712







-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley

Sent: Monday, November 20, 2017 3:19 PM

To: Binshtok, Edan ; Sandeep Shah2 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - deployment



Hi

My dev env is Ubuntu 16. The virtualization framework is virtualbox.



The current status is that when running 'vagrant up', it is able to 
boot  the vm ' pxe_ops_01...'.

At this point vagrant gets stuck on network configuration:

devel@devel:~/dev/onap/vvp/devkit$ vagrant up Bringing machine 'ops-01' 
up with 'virtualbox' provider...

Bringing machine 'ceph-01' up with 'virtualbox' provider...

Bringing machine 'coreos-01' up with 'virtualbox' provider...

==> ops-01: Importing base box 'centos/7'...

==> ops-01: Matching MAC address for NAT networking...

==> ops-01: Setting the name of the VM: pxe_ops-01_1511190177841_48331 
==> ops-01: Clearing any previously set network interfaces...

==> ops-01: Preparing network interfaces based on configuration...

ops-01: Adapter 1: nat

ops-01: Adapter 2: hostonly

ops-01: Adapter 3: hostonly

==> ops-01: Forwarding ports...

ops-01: 22 (guest) => 2502 (host) (adapter 1) ==> ops-01: Running 
'pre-boot' VM customizations...

==> ops-01: Booting VM...

==> ops-01: Waiting for machine to boot. This may take a few minutes...

ops-01: SSH address: 127.0.0.1:2502

ops-01: SSH username: vagrant

ops-01: SSH auth method: private key

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

==> ops-01: Machine booted and ready!

==> ops-01: Configuring and enabling network interfaces...



From my investigation I see that the command for restarting the 
networks 'eth1' and 'eth2' is not returning.



Can't get passed this issue. Did anyone encounter this?



Thanks

Moshe Hoadley

M 972-9-77-62712





-Original Message-

From: Binshtok, Edan [mailto:eb5...@intl.att.com]

Sent: Thursday, November 16, 2017 10:12 PM

To: Sandeep Shah2 ; Moshe Hoadley 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - documentation



On what setup are you guys running the project?

Which version of Linux for example.



Edan

   

Re: [onap-discuss] [vvp] - deployment

2017-11-21 Thread Moshe Hoadley
Did not get passed this.
It seems that this issue happens only in centos7. The coreos vm passes this 
point successfully.

Thanks
Moshe Hoadley
M 972-9-77-62712    



-Original Message-
From: Binshtok, Edan [mailto:eb5...@intl.att.com] 
Sent: Tuesday, November 21, 2017 1:50 PM
To: Moshe Hoadley ; Sandeep Shah2 
; onap-discuss@lists.onap.org
Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 
Subject: Re: [onap-discuss] [vvp] - deployment

Hi Moshe did you get pass this?
Please share.

On 20/11/2017, 15:24, "Moshe Hoadley"  wrote:

More info:

This is the command vagrant gets stuck on:

INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth2 >> 
/etc/sysconfig/network-scripts/ifcfg-eth2



if command -v nmcli &>/dev/null; then

  if command -v systemctl &>/dev/null && systemctl -q is-enabled 
NetworkManager &>/dev/null; then

nmcli c reload eth2

  elif command -v service &>/dev/null && service NetworkManager status 
&>/dev/null; then

nmcli c reload eth2

  fi

fi



/sbin/ifdown eth2

/sbin/ifup eth2



rm -f /tmp/vagrant-network-entry_eth2

 (sudo=true)



Thanks

Moshe Hoadley

M 972-9-77-62712







-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley

Sent: Monday, November 20, 2017 3:19 PM

To: Binshtok, Edan ; Sandeep Shah2 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - deployment



Hi

My dev env is Ubuntu 16. The virtualization framework is virtualbox.



The current status is that when running 'vagrant up', it is able to boot  
the vm ' pxe_ops_01...'.

At this point vagrant gets stuck on network configuration:

devel@devel:~/dev/onap/vvp/devkit$ vagrant up Bringing machine 'ops-01' up 
with 'virtualbox' provider...

Bringing machine 'ceph-01' up with 'virtualbox' provider...

Bringing machine 'coreos-01' up with 'virtualbox' provider...

==> ops-01: Importing base box 'centos/7'...

==> ops-01: Matching MAC address for NAT networking...

==> ops-01: Setting the name of the VM: pxe_ops-01_1511190177841_48331 ==> 
ops-01: Clearing any previously set network interfaces...

==> ops-01: Preparing network interfaces based on configuration...

ops-01: Adapter 1: nat

ops-01: Adapter 2: hostonly

ops-01: Adapter 3: hostonly

==> ops-01: Forwarding ports...

ops-01: 22 (guest) => 2502 (host) (adapter 1) ==> ops-01: Running 
'pre-boot' VM customizations...

==> ops-01: Booting VM...

==> ops-01: Waiting for machine to boot. This may take a few minutes...

ops-01: SSH address: 127.0.0.1:2502

ops-01: SSH username: vagrant

ops-01: SSH auth method: private key

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

==> ops-01: Machine booted and ready!

==> ops-01: Configuring and enabling network interfaces...



From my investigation I see that the command for restarting the networks 
'eth1' and 'eth2' is not returning.



Can't get passed this issue. Did anyone encounter this?



Thanks

Moshe Hoadley

M 972-9-77-62712





-Original Message-

From: Binshtok, Edan [mailto:eb5...@intl.att.com]

Sent: Thursday, November 16, 2017 10:12 PM

To: Sandeep Shah2 ; Moshe Hoadley 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - documentation



On what setup are you guys running the project?

Which version of Linux for example.



Edan



From: Sandeep Shah2 

Date: Thursday, 16 November 2017 at 18:18

To: Moshe Hoadley , "Binshtok, Edan" 
, "onap-discuss@lists.onap.org" 


Cc: "SUNDELOF, ERIK" , "Binshtok, Edan" 
, "MCGOLDRICK, PAUL" 

Subject: RE: [onap-discuss] [vvp] - 

Re: [onap-discuss] [vvp] - missing roles directory

2017-11-21 Thread Binshtok, Edan
Hi Moshe nice find I’ve upload the missing dir.
Please repull from repo and try again.

On 20/11/2017, 16:29, "Moshe Hoadley"  wrote:

Hi

The folder 'ansible-vvp-voluems' is missing in the 'devkit' project.

Expected under:

../vvp/devkit/ansible/roles



Note that a different folder named 'ansible-vvp-bootstrap' is present in 
this location.



Thanks

Moshe Hoadley

972-9-77-62712



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=-Wgjy_QbAZDtB3l21FCjkRKybEA8OoPoYJKt261T6Ec=81E_5Q_Vgr6eKk1rlxu-8C0b1-OxHnw8e3nmxa8Yw0M=6OCgugsDMm9arbhzP-zrS6tP-3THDsF-XErUykcDpFM=
  



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [vvp] - deployment

2017-11-21 Thread Binshtok, Edan
Hi Moshe did you get pass this?
Please share.

On 20/11/2017, 15:24, "Moshe Hoadley"  wrote:

More info:

This is the command vagrant gets stuck on:

INFO ssh: Execute: cat /tmp/vagrant-network-entry_eth2 >> 
/etc/sysconfig/network-scripts/ifcfg-eth2



if command -v nmcli &>/dev/null; then

  if command -v systemctl &>/dev/null && systemctl -q is-enabled 
NetworkManager &>/dev/null; then

nmcli c reload eth2

  elif command -v service &>/dev/null && service NetworkManager status 
&>/dev/null; then

nmcli c reload eth2

  fi

fi



/sbin/ifdown eth2

/sbin/ifup eth2



rm -f /tmp/vagrant-network-entry_eth2

 (sudo=true)



Thanks

Moshe Hoadley

M 972-9-77-62712







-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Moshe Hoadley

Sent: Monday, November 20, 2017 3:19 PM

To: Binshtok, Edan ; Sandeep Shah2 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - deployment



Hi

My dev env is Ubuntu 16. The virtualization framework is virtualbox.



The current status is that when running 'vagrant up', it is able to boot  
the vm ' pxe_ops_01...'.

At this point vagrant gets stuck on network configuration:

devel@devel:~/dev/onap/vvp/devkit$ vagrant up Bringing machine 'ops-01' up 
with 'virtualbox' provider...

Bringing machine 'ceph-01' up with 'virtualbox' provider...

Bringing machine 'coreos-01' up with 'virtualbox' provider...

==> ops-01: Importing base box 'centos/7'...

==> ops-01: Matching MAC address for NAT networking...

==> ops-01: Setting the name of the VM: pxe_ops-01_1511190177841_48331 ==> 
ops-01: Clearing any previously set network interfaces...

==> ops-01: Preparing network interfaces based on configuration...

ops-01: Adapter 1: nat

ops-01: Adapter 2: hostonly

ops-01: Adapter 3: hostonly

==> ops-01: Forwarding ports...

ops-01: 22 (guest) => 2502 (host) (adapter 1) ==> ops-01: Running 
'pre-boot' VM customizations...

==> ops-01: Booting VM...

==> ops-01: Waiting for machine to boot. This may take a few minutes...

ops-01: SSH address: 127.0.0.1:2502

ops-01: SSH username: vagrant

ops-01: SSH auth method: private key

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

ops-01: Warning: Remote connection disconnect. Retrying...

==> ops-01: Machine booted and ready!

==> ops-01: Configuring and enabling network interfaces...



From my investigation I see that the command for restarting the networks 
'eth1' and 'eth2' is not returning.



Can't get passed this issue. Did anyone encounter this?



Thanks

Moshe Hoadley

M 972-9-77-62712





-Original Message-

From: Binshtok, Edan [mailto:eb5...@intl.att.com]

Sent: Thursday, November 16, 2017 10:12 PM

To: Sandeep Shah2 ; Moshe Hoadley 
; onap-discuss@lists.onap.org

Cc: SUNDELOF, ERIK ; MCGOLDRICK, PAUL 

Subject: Re: [onap-discuss] [vvp] - documentation



On what setup are you guys running the project?

Which version of Linux for example.



Edan



From: Sandeep Shah2 

Date: Thursday, 16 November 2017 at 18:18

To: Moshe Hoadley , "Binshtok, Edan" 
, "onap-discuss@lists.onap.org" 


Cc: "SUNDELOF, ERIK" , "Binshtok, Edan" 
, "MCGOLDRICK, PAUL" 

Subject: RE: [onap-discuss] [vvp] - documentation





Hi Moshe – this is what I have tried so far and at this time, I am running 
into SSH authentication issues…











  1.  Update Vagrantfile in devkit/vagrant/pxe/Vagrantfile – add

 *   Require ‘yaml’

  2.  Change IDE to IDE Controller in pxe/Vagrantfile



I am running into the below issue at this time:





An error occurred in the underlying SSH library that Vagrant uses. The 
error message 

[onap-discuss] Usecase subcommittee 20/11/2017 meeting - the summary

2017-11-21 Thread Alla Goldner
Hi all,

Thanks to all meeting's participants!

Here is the summary:


1.   Alla thanked all Usecase subcommittee members and Integration team 
members greatly contributed to the success of Amsterdam Release!!!

 2.   R2 requirements
a.E-vCPE requirements were presented by Luman. This will follow by 
email discussion which Luman will initiate ASAP, describing the problem the 
requirements are resolving, and high level description, in addition to the 
presentation.

b.Centralized Parsers Distribution requirements were presented by  
Atul. Some questions were raised. The next step is to include the requirements 
into merged requirements table, including all needed information and also 
present it to Architecture subcommittee

c. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:


i.Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links

ii.  Community members will provide comments what is missing 
(if something is missing), target date is next Monday, 27/11/2017

d.VNF Scaling - next level of details - this task force 
representatives didn't attend the call. Steve/team - please also issue email as 
described above for the VNF scaling related requirements to see if ONAP 
community is satisfied with the level of definition

e.External Controller - status of the discussions (Ramesh). There 
was no progress on the related discussions. Ramesh will update us next week on 
the progress achieved by then


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D362BB.0306CCA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss