date:20170713

[onap-discuss] Invitation: [msb] Weekly Meeting @ Weekly from 8:30pm to 9:30pm on Monday (CST) (onap-discuss@lists.onap.org)

2017-07-13 Thread zhaohuabing

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Shanghai
X-LIC-LOCATION:Asia/Shanghai
BEGIN:STANDARD
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:CST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Shanghai:20170717T203000
DTEND;TZID=Asia/Shanghai:20170717T213000
RRULE:FREQ=WEEKLY;BYDAY=MO
DTSTAMP:20170714T020447Z
ORGANIZER;CN=ONAP:mailto:f26tu6tqeqou1li98n7uvq66d0@group.calendar.google.c
 om
UID:9snsbh2gs01l8t8ediu9fvj...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jf2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=amani...@att.com;X-NUM-GUESTS=0:mailto:amani...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=tian@amdocs.com;X-NUM-GUESTS=0:mailto:tian@amdocs.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=steven.blim...@amdocs.com;X-NUM-GUESTS=0:mailto:steven.blimkie@amdo
 cs.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
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=rx2...@att.com;X-NUM-GUESTS=0:mailto:rx2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=li.z...@zte.com.cn;X-NUM-GUESTS=0:mailto:li.z...@zte.com.cn
CREATED:20170714T020446Z
DESCRIPTION:Huabing is inviting you to a scheduled Zoom meeting. \n\nPrelim
 inary agenda\n* A MSB integration discussion\n\n\nJoin from PC\, Mac\, L
 inux\, iOS or Android: https://zoom.us/j/66\n\nOr iPhone one-tap (U
 S Toll):  +14086380968\,\,66# or +16465588656\,\,66#\n\nOr 
 Telephone:\n\nDial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US To
 ll)\n\nMeeting ID: 699 996 \n\nInternational numbers available:
  https://zoom.us/zoomconference?m=_5QAuX9O-wb43xJqoNQjTlyYurEIrnWK\n\n\n\nV
 iew your event at https://www.google.com/calendar/event?action=VIEW=OXN
 uc2JoMmdzMDFsOHQ4ZWRpdTlmdmpndWsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=N
 TIjZjI2dHU2dHFlcW91MWxpOThuN3V2cTY2ZDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbTMy
 NWJkY2YzY2VmY2QyMDFmZDBjNTVjNTk5YmFiNTM5YTc5OGI0MWY=Asia/Shanghai=en
 .
LAST-MODIFIED:20170714T020446Z
LOCATION:https://zoom.us/j/66
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[msb] Weekly Meeting
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] [holmes]Apply for a Timeslot for Holmes Weekly Meeting

2017-07-13 Thread fu.guangrong

Sorry I forgot to offer the timeslot.




The ad hoc weekly meeting for Holmes will be hold from 20:00 to 21:00 (UTC+8) 
Thursday.




Regards,

Guangrong 
















原始邮件



发件人：付光荣10144542
收件人：  
日 期 ：2017年07月14日 08:49
主 题 ：[holmes]Apply for a Timeslot for Holmes Weekly Meeting






Hi Kenny,





Could you please help to add the bridge info into the ONAP calendar for Holmes 
meeting? This would be an ad hoc meeting held on necessity.





We'll be using a private meeting room and the the ID is 
https://zoom.us/j/66.




Thanks.




Best Regards,

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

[onap-discuss] [holmes]Apply for a Timeslot for Holmes Weekly Meeting

2017-07-13 Thread fu.guangrong

Hi Kenny,





Could you please help to add the bridge info into the ONAP calendar for Holmes 
meeting? This would be an ad hoc meeting held on necessity.





We'll be using a private meeting room and the the ID is 
https://zoom.us/j/66.




Thanks.




Best Regards,

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

[onap-discuss] Invitation: JULY VIRTUAL DEVELOPERS EVENT @ Every 3 days from 5am to 9am 3 times (PDT) (onap-discuss@lists.onap.org)

2017-07-13 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:20170724T05
DTEND;TZID=America/Los_Angeles:20170724T09
RRULE:FREQ=DAILY;COUNT=3;INTERVAL=3
DTSTAMP:20170714T003454Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:hd7mogqeig5q1ph62je9ovj...@google.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
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-...@lists.onap.o
 rg
CREATED:20170714T003453Z
DESCRIPTION:Agenda (WIP) https://wiki.onap.org/display/DW/July+24-26+Virtua
 l+Developers+Event\nView your event at https://www.google.com/calendar/even
 t?action=VIEW=aGQ3bW9ncWVpZzVxMXBoNjJqZTlvdmpocGcgb25hcC1kaXNjdXNzQGxpc
 3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1
 mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tODEzYjgwODczY2VhY2FlNjkyMjViZG
 Y5OWNiNWYxZGQxYzFkNmJkMw=America/Los_Angeles=en.
LAST-MODIFIED:20170714T003453Z
LOCATION:info coming soon
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:JULY VIRTUAL DEVELOPERS EVENT
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] 答复: [Modeling][vfc] TOSCA Parser API Requirements

2017-07-13 Thread 杨艳

Hi Tom,

 

Thanks for your suggestion, I have uploaded the document to the wiki 
https://wiki.onap.org/display/DW/VF-C+R1+Deliverables, If there is any feedback 
that need to update the document, I will update to the wiki page.

 

Best Regards,

Yan

发件人: Thomas Nadeau [mailto:thomas.nad...@amdocs.com] 
发送时间: 2017年7月13日 19:14
收件人: 杨艳; 'denghui \\(L\\)'; onap-discuss
主题: RE: [onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements

 

Can you please post the document onto Jira somewhere rather than mailing it 
around?  That will allow everyone to look at the same version until its changed.

 

--Tom

 

 

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ??
Sent: Thursday, July 13, 2017 6:53 AM
To: 'denghui \\(L\\)' ; onap-discuss 

Subject: Re: [onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements

 

 

Very sorry,I forgot to add the attachment in last email.

 

Best Regards,

Yan

 

邮件原文
发件人："杨艳" 
收件人："'denghui \\(L\\)  '" ,onap-discuss 

抄　送: (无)
发送时间：2017-07-13 17:53:28
主题：[onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements

Dear Modeling Project PTL,

 

Please check the attachment about the API requirements of TOSCA Parser in VF-C 
for R1, which has been discussed within the VF-C project team. And now we want 
to submit it to the modeling project for evaluation and hope the modeling 
project recommends appropriate Parser that can meet these requirements.

 

Best Regards,

Yan

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] Please join the onap-lf-announce mailing list

2017-07-13 Thread Kenny Paul

I have created an outbound only mailing list named onap-lf-announce. It is 
highly recommended that all members of the TSC and Developer community join 
this mailing list. 

This distribution list for official communications from the Linux Foundation to 
the ONAP community and will be used for messages such as the Portland 
datacenter outage we experienced today.

Please do not select digest mode for this particular list. It is intended for 
real-time communications of status.

 https://lists.onap.org/mailman/listinfo/onap-lf-announce 



Best Regards, 
-kenny

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

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

[onap-discuss] Fwd: [The Linux Foundation status] Update : Outage at PDX datacenter

2017-07-13 Thread Kenny Paul


Best Regards, 
-kenny

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

> Begin forwarded message:
> 
> From: nore...@statuspage.io
> Subject: [The Linux Foundation status] Update : Outage at PDX datacenter
> Date: July 13, 2017 at 2:56:52 PM PDT
> To: '' 
> 
> Outage at PDX datacenter 
> Incident Report for The Linux Foundation
> An Incident Update Has Been Posted
> All systems are back online and functional. We are continuing to monitor the 
> situation and are working with our colocation provider to understand the root 
> cause of the outage and why so many of our systems were affected by it. 
> 
> A power outage occurred this morning which caused many of our non-redundant 
> and redundant systems to go offline. The order which these systems came back 
> online was important, as we lost access to core components of our 
> infrastructure (network, DNS, disk arrays, VPNs, 2FA, virtualization hosts, 
> etc). Because of the severity of the outage, restoring services took longer 
> than usual.
> Jul 13, 21:56 UTC
> PREVIOUS UPDATES
> Update
> We are continuing to troubleshoot the power issues at the data center by 
> working through our core services and bringing systems back online as quickly 
> as possible. Next update at 2:45pm.
> Jul 13, 20:53 UTC
> Update
> An LF staff member is now onsite at the Portland data center to triage and 
> trouble shoot issues. 
> As this situation is complex and mostly out of our control, the next update 
> will be at 1:45pm.
> Jul 13, 19:46 UTC
> Update
> We appear to have lost power to a number of out of band systems and servers 
> which is continuing to cause outages. We believe the power outage may have 
> affected core routing/switching in the datacenter as well as power to some of 
> our servers. We are investigating and will continue to identify additional 
> issues.
> Jul 13, 18:45 UTC
> Monitoring
> Our colo provider has confirmed that there are power issues at the PDX DC3 
> datacenter. They currently do not have an ETA for service restores or root 
> cause identified, but will update us as soon as they do. 
> 
> We appear to have many of our services back online at this time, and will be 
> monitoring the situation until we have confirmed things are all clear.
> Jul 13, 18:40 UTC
> Investigating
> We are investigating what we believe to be an issue with network/switching 
> equipment in the PDX datacenter. Atmosera is currently "performing 
> maintenance on the power systems at DC3, our downtown Portland datacenter" 
> which was not supposed to affect any running systems. We are investigating 
> and will update as soon as we learn more. 
> 
> This affects any sites and infrastructure which are hosted at, or depend on 
> services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
> Jul 13, 18:09 UTC
> View status page  or unsubscribe 
>  from these 
> emails. 
> Powered by StatusPage 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration] Jenkins jobs not updating Gerrit

2017-07-13 Thread Gary Wu

Hi helpdesk,

When Jenkins jobs are completing now, they are not updating the results in 
Gerrit.  Can you take a look?

Thanks,
Gary


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

[onap-discuss] Fwd: [The Linux Foundation status] Monitoring : Outage at PDX datacenter

2017-07-13 Thread Kenny Paul


Best Regards, 
-kenny

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

> Begin forwarded message:
> 
> From: nore...@statuspage.io
> Subject: [The Linux Foundation status] Monitoring : Outage at PDX datacenter
> Date: July 13, 2017 at 11:41:16 AM PDT
> To: '' 
> 
> Outage at PDX datacenter 
> Incident Report for The Linux Foundation
> New Incident Status: Monitoring
> Our colo provider has confirmed that there are power issues at the PDX DC3 
> datacenter. They currently do not have an ETA for service restores or root 
> cause identified, but will update us as soon as they do. 
> 
> We appear to have many of our services back online at this time, and will be 
> monitoring the situation until we have confirmed things are all clear.
> Jul 13, 18:40 UTC
> PREVIOUS UPDATES
> Investigating
> We are investigating what we believe to be an issue with network/switching 
> equipment in the PDX datacenter. Atmosera is currently "performing 
> maintenance on the power systems at DC3, our downtown Portland datacenter" 
> which was not supposed to affect any running systems. We are investigating 
> and will update as soon as we learn more. 
> 
> This affects any sites and infrastructure which are hosted at, or depend on 
> services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
> Jul 13, 18:09 UTC
> View status page  or unsubscribe 
>  from these 
> emails. 
> Powered by StatusPage 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #43020] ONAP wiki down

2017-07-13 Thread Gildas Lanilis

Systems are back operational.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Gildas Lanilis 
Sent: Thursday, July 13, 2017 11:31 AM
To: onap-discuss@lists.onap.org
Subject: FW: [ONAP Helpdesk #43020] ONAP wiki down

Hi,

FYI, ONAP Wiki, Jira and Gerrit are currently down.
Refer to ticket msg from LF below.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Thursday, July 13, 2017 11:18 AM
To: Gildas Lanilis 
Subject: Re: [ONAP Helpdesk #43020] ONAP wiki down

On 07/13/2017 11:13 AM, Andrew Grimberg wrote:
> On 07/13/2017 11:09 AM, Gildas Lanilis via RT wrote:
> 
>> Hi,
>>
>> Looks like onap wiki is down:
>> [cid:image001.png@01D2FBC8.6D54A320]
> 
> Greetings Gildas,
> 
> The site is definitely not responding for me either. We haven't gotten 
> any alarms though which is a bit troubling.
> 
> I'm poking into it now.

Greetings Gildas,

Just an update. Our systems administration team updated our general Linux 
Foundation status page [0] with the following information just a few minutes 
ago.

--[cut]--
Investigating - We are investigating what we believe to be an issue with 
network/switching equipment in the PDX datacenter. Atmosera is currently 
"performing maintenance on the power systems at DC3, our downtown Portland 
datacenter" which was not supposed to affect any running systems. We are 
investigating and will update as soon as we learn more.

This affects any sites and infrastructure which are hosted at, or depend on 
services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
--[/cut]--

So, the issue is with our DC provider.

[0] https://status.linuxfoundation.org/

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation


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

[onap-discuss] Fwd: [The Linux Foundation status] Investigating : Outage at PDX datacenter

2017-07-13 Thread Kenny Paul


Best Regards, 
-kenny

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

> Begin forwarded message:
> 
> From: nore...@statuspage.io
> Subject: [The Linux Foundation status] Investigating : Outage at PDX 
> datacenter
> Date: July 13, 2017 at 11:09:24 AM PDT
> To: kp...@linuxfoundation.org
> 
> Outage at PDX datacenter 
> Incident Report for The Linux Foundation
> Investigating
> We are investigating what we believe to be an issue with network/switching 
> equipment in the PDX datacenter. Atmosera is currently "performing 
> maintenance on the power systems at DC3, our downtown Portland datacenter" 
> which was not supposed to affect any running systems. We are investigating 
> and will update as soon as we learn more. 
> 
> This affects any sites and infrastructure which are hosted at, or depend on 
> services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
> Jul 13, 18:09 UTC
> View status page  or unsubscribe 
>  from these 
> emails. 
> Powered by StatusPage 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] FW: [ONAP Helpdesk #43020] ONAP wiki down

2017-07-13 Thread Gildas Lanilis

Hi,

FYI, ONAP Wiki, Jira and Gerrit are currently down.
Refer to ticket msg from LF below.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, July 13, 2017 11:18 AM
To: Gildas Lanilis 
Subject: Re: [ONAP Helpdesk #43020] ONAP wiki down

On 07/13/2017 11:13 AM, Andrew Grimberg wrote:
> On 07/13/2017 11:09 AM, Gildas Lanilis via RT wrote:
> 
>> Hi,
>>
>> Looks like onap wiki is down:
>> [cid:image001.png@01D2FBC8.6D54A320]
> 
> Greetings Gildas,
> 
> The site is definitely not responding for me either. We haven't gotten 
> any alarms though which is a bit troubling.
> 
> I'm poking into it now.

Greetings Gildas,

Just an update. Our systems administration team updated our general Linux 
Foundation status page [0] with the following information just a few minutes 
ago.

--[cut]--
Investigating - We are investigating what we believe to be an issue with 
network/switching equipment in the PDX datacenter. Atmosera is currently 
"performing maintenance on the power systems at DC3, our downtown Portland 
datacenter" which was not supposed to affect any running systems. We are 
investigating and will update as soon as we learn more.

This affects any sites and infrastructure which are hosted at, or depend on 
services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
--[/cut]--

So, the issue is with our DC provider.

[0] https://status.linuxfoundation.org/

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




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

[onap-discuss] [doc] Document Tool Chain & Example

2017-07-13 Thread BENNETT, RICH

Greetings!

The Documentation Project team has compared options for the tool chain, 
including two examples of how a representative subset of existing documentation 
(https://wiki.onap.org/display/DW/Release+Notes+1.0.0+draft) would be 
created/managed/published if the tool chain was based on either:

Markdown-Github-Jekyll 
(https://wiki.onap.org/display/DW/A+Sample+about+how+to+develop+documents+by+Markdown)
 or
ReStructured Text-Sphinx-Readthedocs 
(https://wiki.onap.org/display/DW/An+Example+of+Creating+Documents+with+ReStructured+Text-Sphinx-Readthedocs)

We are proceeding with the ReStructured Text option as described in the example 
above and recommended here

https://wiki.onap.org/display/DW/Comparison+and+Recommendation+of+Document+Tool+Chain#ComparisonandRecommendationofDocumentToolChain-recommendation

We will start by establishing the initial doc repository structure including 
the initial: top level index, templates, git submodule references to other 
project repositories, and guide for creating documentation.

Regards,

Rich

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

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

2017-07-13 Thread Gary Wu

I’ve not seen the Jenkins Checkstyle plugin used by LF before, but I’ll follow 
up with LF to see if they can set it up.

Thanks,
Gary

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Thursday, July 13, 2017 5:28 AM
To: Gary Wu ; Alexis de Talhouët 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Alexis, Gary,

We should also consider the following reference since ONAP is not only Java 
code base.

  *   Google Python Style Guideline: 
https://google.github.io/styleguide/pyguide.html
Here is another one concerning Check style Coverage.

  *   Google's Java Style Check style Coverage: 
http://checkstyle.sourceforge.net/google_style.html
These have been added as a comment to the ONAP wiki page
https://wiki.onap.org/display/DW/Java+code+style

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
Sent: Thursday, July 13, 2017 2:18 PM
To: Gary Wu >; Alexis de 
Talhouët >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Good morning Alexis, Gary,

I confirm that we can use CLAMP to do a pilot.
Will you also contact LF to integrate the Checkstyle plug-in to Jenkins as 
discussed during the Integration meeting?

Many thanks & regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Wednesday, July 12, 2017 7:31 PM
To: Alexis de Talhouët >
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Looks like the Java code style was already documented by Gildas here:

1.Developer 
Wiki
 > Getting 
Involved
 > Developer Best 
Practices
 > Java code style
https://wiki.onap.org/display/DW/Java+code+style

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, July 12, 2017 3:32 AM
To: Gary Wu >
Cc: Gildas Lanilis 
>; LEFEVRE, 
CATHERINE >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Ok, good. Thanks for the pointers. Google Java Style what is use as well in 
ODL, so I can say I'm already familiar with them :)
One we have a wiki for that, I strongly believe advertising this widly (through 
this mailing list) can be a good start to get devs onboard and/or familiar with 
the check styles rules that would be enforced.

Thanks,
Alexis

Le mardi 11 juillet 2017, Gary Wu 
> a écrit :
Currently we’re using what was defined for OPEN-O:  
https://wiki.open-o.org/display/GI/OPEN-O+Java+code+style,
 namely:

Google Java Style with some modifications:
4.2 Block indentation: +4 spaces
4.4 Column limit: 120

Gildas, any ideas where we should put this in the ONAP wiki?

Thanks,
Gary

From: Alexis de Talhouët

Re: [onap-discuss] VFW demo: APPC reports "Mount point does not exist" when a policy to change the packer rate should be sent to pgn

2017-07-13 Thread Tapan Majhi

Initially I was also getting the same , to bypass this I did the mounting 
manually

http:// 
{appc-ip}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/clfwl01pgn6201

Body :

 
clfwl01pgn6201 10.247.83.123 2831 admin admin false  false
 2
 0 
2000
 1.5  120 

Changing the relevant parameters(node-id and host) and APPC started processing 
the request.

Regards
Tapan M

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of MAHER, RANDA
Sent: Thursday, July 13, 2017 7:39 PM
To: Josef Reisinger ; onap-discuss 

Subject: Re: [onap-discuss] VFW demo: APPC reports "Mount point does not exist" 
when a policy to change the packer rate should be sent to pgn

Hi Josef,
Hector is looking into this. Looks like a step probably missed, investigating. 
He will provide updates in Jira.
Thanks, Randa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Josef Reisinger
Sent: Thursday, July 13, 2017 5:36 AM
To: onap-discuss 
>
Subject: [onap-discuss] VFW demo: APPC reports "Mount point does not exist" 
when a policy to change the packer rate should be sent to pgn

Folks,

we got ONAP up on vanilla openstack and are "so close" to finish the vFW demo 
scenario. We can see measurements being generated at the firewall node, trace 
the message flow through DCAE components and policy to APPC where an action 
should be triggered to increase/decrease the packet rate in the packet 
generator. In the last step, we can see this error message
{ "errors": 
{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount
 point does not exist."}]}}appearing in karaf log.

The request in question looks like:

http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.0.2.1:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn/yang-ext:mount/sample-plugin:sample-plugin/pg-streams/

I used to get node details if I shortened the url to
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.0.2.1:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn

Of course we did /opt/demo.sh APPC ... (often enough) on the robot VM, we could 
even see this generating a message to APPC. We also rebooted/restarted some of 
the components since the vFW stack was created - could this shave an impact on 
the mounted state too?

More details are to be found in 
https://jira.onap.org/browse/APPC-76

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:+49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  josef.reisin...@de.ibm.com





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 


Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partnership with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][sdc][so][sdnc] vCPE use case study

2017-07-13 Thread Kang Xi

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Kang Xi:MAILTO:kang...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='onap-disc
 u...@lists.onap.org':MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='danny.zho
 u...@intel.com':MAILTO:danny.z...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Yunxia Che
 n:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang Xu (Y
 ang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chong Li:M
 AILTO:chong...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jon Fannar
  Karlsson Taylor:MAILTO:jon.tay...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Lefevre, C
 atherine":MAILTO:cl6...@intl.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SPATSCHECK
 , OLIVER  (OLIVER)":MAILTO:spat...@research.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Lando,Mich
 ael":MAILTO:ml6...@intl.att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="ROSE, DANI
 EL V":MAILTO:dr6...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alla Goldn
 er:MAILTO:alla.gold...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="FREEMAN, B
 RIAN D":MAILTO:bf1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Yoav Kluge
 r:MAILTO:yoav.klu...@amdocs.com
DESCRIPTION;LANGUAGE=en-US:All\,\n\nWe will continue to analyze the vCPE us
 e case. This meeting will mainly focus on topics related to SDC\, SO\, and
  SDNC. Some important questions/answers are listed here: https://wiki.onap
 .org/display/DW/Use+Case+Related+Important+Questions+and+Answers\nWe will 
 use zoom:\nhttp://zoom.us/j/44\n\nThanks\,\nKang\n\n\n
SUMMARY;LANGUAGE=en-US:[integration][sdc][so][sdnc] vCPE use case study
DTSTART;TZID=Eastern Standard Time:20170713T11
DTEND;TZID=Eastern Standard Time:20170713T12
UID:04008200E00074C5B7101A82E00850FD7186B7FBD201000
 01000F09C331DC8148D4885651D79A1C1F734
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170713T130800Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:http://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2089646049
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] aai-instances installation

2017-07-13 Thread Kedar Ambekar

Ajay, we had to install AAI SSL certificate manually in few JRE key stores like 
VID, MSO etc.
You may try that.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
ajay.priyadar...@ril.com
Sent: Monday, July 3, 2017 6:37 PM
To: subhash.kumar.si...@huawei.com; arul.na...@amdocs.com; 
gino.frab...@amdocs.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] aai-instances installation

Hi,

I am getting following error while Search for Existing Service Instances or 
searching for subscriber on vid_vm:

2017-07-03 
12:18:43,207|6ae28f99-193f-45dc-81d6-42ae316930e7||http-apr-8080-exec-4||/aai_get_services|292b461a-2954-4b63-a3f9-f916c7ad3bc0|INFO|INFORMATIONAL|172.17.0.3|fa5ce1be4b6c||org.openecomp.vid.controller.AaiController||
 12:18:43:0207<== .getSubscriberListjavax.ws.rs.ProcessingException: 
javax.net.ssl.SSLHandshakeException: SSLHandshakeException invoking 
https://aai.api.simpledemo.openecomp.org:8443/aai/v8/service-design-and-creation/services?depth=0:
 sun.security.validator.ValidatorException: PKIX path building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path to requested target

2017-07-03 
12:18:43,211|432dea23-f505-430c-bc4e-54f245591f0a||http-apr-8080-exec-8||/aai_get_full_subscribers|292b461a-2954-4b63-a3f9-f916c7ad3bc0|INFO|INFORMATIONAL|172.17.0.3|fa5ce1be4b6c||org.openecomp.vid.controller.AaiController||
 12:18:43:0211<== .getSubscriberListjavax.ws.rs.ProcessingException: 
javax.net.ssl.SSLHandshakeException: SSLHandshakeException invoking 
https://aai.api.simpledemo.openecomp.org:8443/aai/v8/business/customers?subscriber-type=INFRA=all:
 sun.security.validator.ValidatorException: PKIX path building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
valid certification path to requested target

Is something missed during installation, I checked everything on AAI. All seems 
fines in log. Any suggestions.

Regards,
Ajay Priyadarshi

From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com]
Sent: 30 June 2017 11:14
To: Arul Nambi; Gino Fraboni; 
onap-discuss@lists.onap.org
Cc: Ajay Priyadarshi; Kanagaraj Manickam
Subject: RE: aai-instances installation

Thank you Arul and Gino for the response.

I've updated the `deploy_vm1.sh` for `data-router` docker image and pushed the 
patch [1].

[1] https://gerrit.onap.org/r/#/c/5609/

--
Regards,
Subhash Kumar Singh

From: Arul Nambi [mailto:arul.na...@amdocs.com]
Sent: Tuesday, June 27, 2017 7:44 PM
To: Gino Fraboni >; 
Subhash Kumar Singh 
>; 
onap-discuss@lists.onap.org
Cc: ajay.priyadar...@ril.com
Subject: RE: aai-instances installation

Hey Subash,
The docker image names is wrong for sparky; I will create a PR to fix that. The 
version is right value in the scripts but I did notice that it is not available 
in the nexus3 repo. I am looking into it. In the meantime to unblock you can 
you change the scripts to
docker pull ${DOCKER_REGISTRY}/openecomp/sparky-be:1.1-STAGING-latest;
docker tag $DOCKER_REGISTRY/openecomp/sparky-be:1.1-STAGING-latest 
$DOCKER_REGISTRY/openecomp/sparky-be:latest;
regards
Arul
Arul Nambi MASc
Software Developer
Open Network Division

Amdocs Technology
[cid:image010.png@01D2C9B5.447E30F0]
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gino Fraboni
Sent: Tuesday, June 27, 2017 9:04 AM
To: Subhash Kumar Singh 
>; 
onap-discuss@lists.onap.org
Cc: ajay.priyadar...@ril.com
Subject: Re: [onap-discuss] aai-instances installation

For the Data Router microservice, the artifact name is data-router, not 
datarouter-service.

Hope this is helpful...

Gino Fraboni
Senior Software Developer
Data Experience

[amdocs-2017-brand-mark-rgb]
A Platinum member of 
ONAP
Read the latest on Amdocs.com and the Amdocs blog 
network - and follow us on 
Facebook, Twitter, 
LinkedIn and 
YouTube.

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Subhash Kumar Singh
Sent: Tuesday, June 27, 2017 4:36 AM
To: onap-discuss@lists.onap.org
Cc: ajay.priyadar...@ril.com
Subject: Re: [onap-discuss] aai-instances installation

Hello

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

2017-07-13 Thread Lefevre, Catherine

Alexis, Gary,

We should also consider the following reference since ONAP is not only Java 
code base.

  *   Google Python Style Guideline: 
https://google.github.io/styleguide/pyguide.html
Here is another one concerning Check style Coverage.

  *   Google's Java Style Check style Coverage: 
http://checkstyle.sourceforge.net/google_style.html
These have been added as a comment to the ONAP wiki page
https://wiki.onap.org/display/DW/Java+code+style

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
Sent: Thursday, July 13, 2017 2:18 PM
To: Gary Wu ; Alexis de Talhouët 
; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Good morning Alexis, Gary,

I confirm that we can use CLAMP to do a pilot.
Will you also contact LF to integrate the Checkstyle plug-in to Jenkins as 
discussed during the Integration meeting?

Many thanks & regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Wednesday, July 12, 2017 7:31 PM
To: Alexis de Talhouët >
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Looks like the Java code style was already documented by Gildas here:

1. Developer 
Wiki
 > Getting 
Involved
 > Developer Best 
Practices
 > Java code style
https://wiki.onap.org/display/DW/Java+code+style

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, July 12, 2017 3:32 AM
To: Gary Wu >
Cc: Gildas Lanilis 
>; LEFEVRE, 
CATHERINE >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Ok, good. Thanks for the pointers. Google Java Style what is use as well in 
ODL, so I can say I'm already familiar with them :)
One we have a wiki for that, I strongly believe advertising this widly (through 
this mailing list) can be a good start to get devs onboard and/or familiar with 
the check styles rules that would be enforced.

Thanks,
Alexis

Le mardi 11 juillet 2017, Gary Wu 
> a écrit :
Currently we’re using what was defined for OPEN-O:  
https://wiki.open-o.org/display/GI/OPEN-O+Java+code+style,
 namely:

Google Java Style with some modifications:
4.2 Block indentation: +4 spaces
4.4 Column limit: 120

Gildas, any ideas where we should put this in the ONAP wiki?

Thanks,
Gary

From: Alexis de Talhouët 
[mailto:adetalhoue...@gmail.com]
Sent: Tuesday, July 11, 2017 2:11 PM
To: Gary Wu 
>
Cc: LEFEVRE, CATHERINE 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

On Jul 11, 2017, at 2:27 PM, Gary Wu 
> 
wrote:

Hi Catherine,

In

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

2017-07-13 Thread Lefevre, Catherine

Good morning Alexis, Gary,

I confirm that we can use CLAMP to do a pilot.
Will you also contact LF to integrate the Checkstyle plug-in to Jenkins as 
discussed during the Integration meeting?

Many thanks & regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Wednesday, July 12, 2017 7:31 PM
To: Alexis de Talhouët 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Looks like the Java code style was already documented by Gildas here:

1. Developer 
Wiki
 > Getting 
Involved
 > Developer Best 
Practices
 > Java code style
https://wiki.onap.org/display/DW/Java+code+style

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, July 12, 2017 3:32 AM
To: Gary Wu >
Cc: Gildas Lanilis 
>; LEFEVRE, 
CATHERINE >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Ok, good. Thanks for the pointers. Google Java Style what is use as well in 
ODL, so I can say I'm already familiar with them :)
One we have a wiki for that, I strongly believe advertising this widly (through 
this mailing list) can be a good start to get devs onboard and/or familiar with 
the check styles rules that would be enforced.

Thanks,
Alexis

Le mardi 11 juillet 2017, Gary Wu 
> a écrit :
Currently we’re using what was defined for OPEN-O:  
https://wiki.open-o.org/display/GI/OPEN-O+Java+code+style,
 namely:

Google Java Style with some modifications:
4.2 Block indentation: +4 spaces
4.4 Column limit: 120

Gildas, any ideas where we should put this in the ONAP wiki?

Thanks,
Gary

From: Alexis de Talhouët 
[mailto:adetalhoue...@gmail.com]
Sent: Tuesday, July 11, 2017 2:11 PM
To: Gary Wu 
>
Cc: LEFEVRE, CATHERINE 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

On Jul 11, 2017, at 2:27 PM, Gary Wu 
> 
wrote:

Hi Catherine,

In today’s Integration meeting, we discussed having CLAMP pilot trials around 
coding styles.  In OPEN-O we centrally defined coding styles in the oparent 
project/repo, and it would be great if we can do likewise for ONAP so we can 
avoid duplicate or conflicting definitions across projects.  Do you think we 
can have CLAMP do a pilot run on inheriting from oparent as well?

Is there an place where the code style rules have been explained? I believe a 
wiki page to explain what are the agreed rules could help, similar to what ODL 
has here: 
https://wiki.opendaylight.org/view/BestPractices/Coding_Guidelines#General_Code_Style

At any

[onap-discuss] VFW demo: APPC reports "Mount point does not exist" when a policy to change the packer rate should be sent to pgn

2017-07-13 Thread Josef Reisinger

Folks,

we got ONAP up on vanilla openstack and are "so close" to finish the vFW 
demo scenario. We can see measurements being generated at the firewall 
node, trace the message flow through DCAE components and policy to APPC 
where an action should be triggered to increase/decrease the packet rate 
in the packet generator. In the last step, we can see this error message
{ "errors": 
{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount
 
point does not exist."}]}} appearing in karaf log.

The request in question looks like: 

http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.0.2.1:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn/yang-ext:mount/sample-plugin:sample-plugin/pg-streams/
 


I used to get node details if I shortened the url to
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.0.2.1:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/demofwl01pgn
 


Of course we did /opt/demo.sh APPC ... (often enough) on the robot VM, we 
could even see this generating a message to APPC. We also 
rebooted/restarted some of the components since the vFW stack was created 
- could this shave an impact on the mounted state too?

More details are to be found in https://jira.onap.org/browse/APPC-76

Mit freundlichen Grüßen / Kind regards 
Josef Reisinger 
When wisdom comes to call, there's nobody listening at all - Pendragon / 
Man Of Nomadic Traits 
IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius
IBM Deutschland 
Godesberger Allee 127 
53175 Bonn Beuel
Phone:+49 151 1426 4559 
Mobile:  +49-(0) 151 1426 4559 
E-Mail:  josef.reisin...@de.ibm.com 


 


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

[onap-discuss] 答复: [usecaseui] ONAP Usecase UI ZOOM Meeting

2017-07-13 Thread shentao

Hi, Kenny

 

The weekly meeting time is ok.

But we can't get into meeting room (651540147).

My screen was always waiting status that like attachment.

Sorry about my system language is Chinese. The information of attachment is " 
the meeting host is attending another meeting ". 

So our team can't use zoom-id 651540147 to hold meetings.

 

Tao

 

发件人: Kenny Paul [mailto:kp...@linuxfoundation.org] 
发送时间: 2017年7月13日 1:36
收件人: shentao
抄送: Casey Cain; zhanghao; onap-discuss@lists.onap.org
主题: Re: [onap-discuss] [usecaseui] ONAP Usecase UI ZOOM Meeting

 

Hi Tao,

 

The original request (below) for the meeting was Friday AM Beijing time:

Usecase UI is scheduled at Friday:

 

10:00 AM~11:00 AM (Beijing Time CST) < wrote:

 

Hi, Kenny

 

I’ve tried to hold Usecase UI weekly meeting by zoom 651540147.

But zoom system has always show information “the meeting host is attending 
another meeting” and I can’t enter Usecase UI’s meeting.

Do I have to login with username/password? Or should I change my configuration?

 

Best regards,

Tao

 

 

发件人: Kenny Paul [  
mailto:kp...@linuxfoundation.org] 
发送时间: 2017年6月30日 5:36
收件人: shentao
抄送: Casey Cain; zhanghao;   
onap-discuss@lists.onap.org
主题: Re: [onap-discuss] ONAP Usecase UI ZOOM Meeting

 

Done.

 

ONAP Meeting 6 is inviting you to a scheduled Zoom meeting. 

 

Join from PC, Mac, Linux, iOS or Android:   
https://zoom.us/j/651540147

 

Or iPhone one-tap (US Toll):  +16465588656,,651540147# or 
+14086380968,,651540147#

 

Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

+1 855 880 1246 (US Toll Free)

+1 877 369 0926 (US Toll Free)

Meeting ID: 651 540 147

International numbers available:  
 
https://zoom.us/zoomconference?m=C9ggkJxYGu7XRCrYIoinZfTJg-7jDSyH

 

 

Best Regards, 
-kenny

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

 

On Jun 28, 2017, at 3:23 PM, shentao <  
shen...@chinamobile.com> wrote:

 

Hi, Casey

 

Could you help me confirm if zoom meeting of Usecase UI has been created.

The first time is scheduled on June 30 (this Friday).

 

Best regards,

Tao Shen

 

发件人: shentao [  mailto:shen...@chinamobile.com] 
发送时间: 2017年6月21日 11:15
收件人: 'Casey Cain'
抄送: 'Lingli Deng'; 'zhanghao'
主题: ONAP Usecase UI ZOOM Meeting

 

Hi, Casey

 

Usecase UI is scheduled at Friday:

 

10:00 AM~11:00 AM (Beijing Time CST)

8:00 PM~9:00 PM (Central Standard Time CST)

3:00 AM~4:00 AM (GMT)

6:00PM~7:00PM (PST)

7:00AM~8:00AM (IST)

 

Could you kindly help to book a zoom bridge for us?

 

 

Best regards,

Tao Shen

 

 

-

沈涛

中国移动通信有限公司研究院网络技术研究所

中国北京市西城区宣武门西大街32号（100053）

 

Shen Tao

China Mobile Research Institute

No.32 Xuanwumen west street,Xicheng District, Beijing 100053, China

 

Tel: +86 15801696688-34070

Mobile: +86 13521591389

Email:    shen...@chinamobile.com

-

 

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

 

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

[onap-discuss] 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from CLI

2017-07-13 Thread 杨艳

Hi Kanagaraj,

 

I read the wiki page you mentioned, for the External Resource Management
part, VFC has been listed in the VNFM and EMS management, I’m not very
clear what the meaning of the projects list here, but I would like to
clarify that VF-C will only use the  information of VNFM and  EMS as a
consumer, such as url, user name, etc.

 

 

Regards,

Yan

发件人: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.
org] 代表 Kanagaraj Manickam
发送时间: 2017年7月12日 21:02
收件人: onap-discuss@lists.onap.org
抄送: rk5...@att.com; ah0...@intl.att.com; gg2...@att.com; es4...@att.com;
sw3...@att.com; onap-...@lists.onap.org
主题: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from CLI

 

Dear PTLs,

 

>From ONAP wiki, I have gone thru the Use-cases defined for release A and
based on my understanding, 

captured the minimum-required-top level functionalities in the wiki
https://wiki.onap.org/display/DW/CLI+Functionalities

 

For each of the functionality, I tried to match them with respective
project.

Could you please review them, provide your approvals/feedbacks. Thank you.

 

Regards

Kanagaraj M

 

 


***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群
组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散
发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！

**


***
This e-mail and its attachments contain confidential information from
HUAWEI, which is intended only for the person  or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not   limited to, total or partial disclosure, reproduction,
or dissemination) by persons other than the intended recipient(s) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

***

 

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

[onap-discuss] Invitation: [msb] Weekly Meeting @ Weekly from 8:30pm to 9:30pm on Monday (CST) (onap-discuss@lists.onap.org)

Re: [onap-discuss] [holmes]Apply for a Timeslot for Holmes Weekly Meeting

[onap-discuss] [holmes]Apply for a Timeslot for Holmes Weekly Meeting

[onap-discuss] Invitation: JULY VIRTUAL DEVELOPERS EVENT @ Every 3 days from 5am to 9am 3 times (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] 答复: [Modeling][vfc] TOSCA Parser API Requirements

[onap-discuss] Please join the onap-lf-announce mailing list

[onap-discuss] Fwd: [The Linux Foundation status] Update : Outage at PDX datacenter

[onap-discuss] [integration] Jenkins jobs not updating Gerrit

[onap-discuss] Fwd: [The Linux Foundation status] Monitoring : Outage at PDX datacenter

Re: [onap-discuss] [ONAP Helpdesk #43020] ONAP wiki down

[onap-discuss] Fwd: [The Linux Foundation status] Investigating : Outage at PDX datacenter

[onap-discuss] FW: [ONAP Helpdesk #43020] ONAP wiki down

[onap-discuss] [doc] Document Tool Chain & Example

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Re: [onap-discuss] VFW demo: APPC reports "Mount point does not exist" when a policy to change the packer rate should be sent to pgn

[onap-discuss] [integration][sdc][so][sdnc] vCPE use case study

Re: [onap-discuss] aai-instances installation

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

Re: [onap-discuss] [integration] Refactor CLAMP to inherit from oparent

[onap-discuss] VFW demo: APPC reports "Mount point does not exist" when a policy to change the packer rate should be sent to pgn

[onap-discuss] 答复: [usecaseui] ONAP Usecase UI ZOOM Meeting

[onap-discuss] 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from CLI

22 matches

Site Navigation

Mail list logo

Footer information