date:20170810

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="Yang Xu (Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Friday\, August 11\, 2017 10:00 AM-11:00 A
 M (UTC-05:00) Eastern Time (US & Canada).\nWhere: https://zoom.us/j/409365
 333\n\nNote: The GMT offset above does not reflect daylight saving time ad
 justments.\n\n*~*~*~*~*~*~*~*~*~*\n\nUpdating the meeting bridge info.\n--
 --
 ---\nAll\,\n\nAs we agreed in today’s SO/SDNC meetin
 g\, we will continue the discussion of WAN service definition for SDC/SO/S
 DNC.\n\nThanks\,\n-Yang\n\nWhere   https://zoom.us/j/409365333 (ma
 p)\nCalendaron
 ap-disc...@lists.onap.org\nWho •
 \nkp...@linuxfoundation.org - cr
 eator\n\n•\nonap-discuss@lists.onap.org\n\n•\ndtimo...@att.com\n\n\
 nHi there\,\n\nONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
 \nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/409365333
 \nOr iPhone one-tap (US Toll):
  +16465588656\,\,409365333# or +14086380968\,\,409365333#\nOr Telephone:\n
 Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\n+1 855 880 1
 246 (US Toll Free)\n+1 877 369 0926 (US Toll Free)\nMeeting ID: 409 365 33
 3\nInternational numbers available: https://zoom.us/zoomconference?m=vklJm
 4NMf3IDA0T8F3U6PB6gzd_9L9W7\n\n\n
SUMMARY;LANGUAGE=en-US:[sdc][so][sdnc] VoLTE WAN service definition 
DTSTART;TZID=Eastern Standard Time:20170811T10
DTEND;TZID=Eastern Standard Time:20170811T11
UID:04008200E00074C5B7101A82E008C057A736F611D301000
 010004541E9E33C7A3C428303C7D29965AD13
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170811T042702Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:4
LOCATION;LANGUAGE=en-US:https://zoom.us/j/409365333
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:1688897505
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

[onap-discuss] 答复: 答复：答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

Hi david, micheal




   Email Summary is as following, please check it.   If I am wrong, please 
correct me. Please PTL(yangyan,micheal) arrange a virtual meeting to discuss 
these issues,  thanks.




   1.  Now the things confirmed:

   1.1. In ONAP R1, the SDC will add the openo tosca type. The types’ 
namespace would follow OpenECOMP convention

   Note: the final node type definition still need to be cleared.

   1.2. controllerinfo in the service level will be supported via new 
parameter servicetype and serviceRole.




2.  There are still following questoins needed to be clear from SDC side.

 2.1.  VF level need the vnfminfo, for VFC suggests add a new parameter 
for VF.  what's the advices from SDC team?

  vnfminfo is used by vf-c to identify which vendor vnfm driver 
to choose. The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc. hope 
the description can clear the vnfminfo parameter. 

 2.2. Whether to support ELAN VL, which can be shared among VNFs.


  [Maopeng ] now the SDC supports VL, but it is automatically 
produced.  Now I can design the Eline type VL, but for the VoLTE case , we need 
   multiple VNFs share one VL.


  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.   


  [Michael: David can you respond?]


 2.3. About Service /VNF package


 2.3.1  In the wiki page, SDC_TOSCA_AID_1710 document has no 
nodes definitions, please provide it in the wiki.


   [David] @Michael – Could you please make sure we the 
node type definition file(s) for VF and Service exist in the wiki?


 2.3.2  We want to know the VNF CSAR package format exported 
from SDC, can you give us an example, we want to confirm whether the package 
has some format restrictions.


   [Maopeng ] In the R1,  VNFSDK bundles a VNF package, and 
import to the SDC. VFC get the VNF package from theSDC catalog. 
   


   Is theVNF package defined in the VNFSDK or SDC for R1? 
What's the VNF package format for VFC in R1?
 


[Michael] since we are now still developing the 
Tosca onboarding I cannot provide you the exact output. I can   share an 
example of the CSAR we currently create  for the vFW/vDNS use case.   


[Maopeng] The service package and vnf package 
CSAR in the SDC catalog, please share them. Thanks


This is really a block issuse for VFC if the 
service and VF package format can not be provided specifically in time.






2.4. About the parser, VFC written in python can not use the java lib  
directly.


  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1


  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?


  


Best Regards

Maopeng



原始邮件



发件人：张茂鹏10030173
收件人： 
抄送人：  
日 期 ：2017年08月10日 21:43
主 题 ：[onap-discuss] 答复： 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C





hi, 
 
The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc. 
hope the description can clear the vnfminfo parameter. 
 
thanks. 
 
 






发件人:   张茂鹏10030173  
收件人:ds2...@att.com
抄送:er4...@intl.att.com onap-discuss@lists.onap.org
日期:   2017-08-10 21:29:59  
主题:[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C  


hi, 
 
vnfminfo is used by vf-c to identify which vendor vnfm driver to choose. 
 
thanks 
maopeng 
 
 




发件人:   SHADMI,DAVID  
收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN
抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org
日期:   2017-08-10 20:57:55  
主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C  




  




Hi,


 


My comments are embedded.


 


@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser?


 


Thanks,


David


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C


 

hi david

 

thanks, david. a few

[onap-discuss] about disscuss in VoLTE [SO] / [SDNC] Interface discussion (8/11, 10:00 pm UTC8 / 10:00 am EST )

2017-08-10 Thread huang.zhuoyao

Hi, Dan


May I ask what's the topic gonna to be disscussed in VoLTE [SO] / [SDNC] 
Interface discussion (8/11, 10:00 pm UTC8 / 10:00 am EST )? 


Thank you!



















黄卓垚huangzhuoyao






职位position 
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.









深圳市南山区科技南路55号中兴通讯研发大楼33楼 
33/F, R Building, ZTE Corporation Hi-tech Road South, 
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057 
T: +86 755    F: +86 755  
M: +86 xxx 
E: huang.zhuo...@zte.com.cn 
www.zte.com.cn___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] [SDNC] [SO] Hi, Here is the remain questions// summary and proposed action for SPTN WAN Model and implementation

2017-08-10 Thread yuan.yue

Hi all,

We have had a pretty good discussion on WAN connection of volte use case this
morning/last evening. Many thanks to all who help to clear the sequence,
interface among SO, SDNC, 3rd party controller also inside the SDNC. I believe
we can move forward now.

May I propose next step actions as:

1. ZhouYoa Huang submit the SDNC southband API payload for reference and
confirm northband GENERIC RESOURCE API payload with SDNC team.

2. ZTE prepare TOSCA WAN Descriptor and the content of the Descriptor should be
align with the payload of SDNC northband GENERIC RESOURCE API.

3. Discuss the WAN Descriptor with SDC/SO/SDNC teams in modeling subcommittee
to freeze the WAN Descriptor for volte usecase.

Best Regards,

Yuan Yue

袁越 yuanyue

资深战略规划师 Senior Strategy Planner

技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System
Product

南京市雨花区软件大道50号中兴通讯3号楼1/F,Building 3, ZTE Nanjing R Center II, No.50, Software
Avenue,YuHua District,Nanjing,P.R.China 210012
T: +025 88013478

M: +86 13851446442
E: yuan@zte.com.cn
www.zte.com.cn

原始邮件

发件人：黄卓垚10112215
收件人：

抄送人：
日 期 ：2017年08月10日 21:12
主 题 ：[onap-tsc] Hi, Here is the remain questions

Hi,

First l'd like to confirm with SDNC team on several keypoints about the
release1 volte use case WAN orchestration procedure both in design stage and
runtime:

We should use Directed Graphs portal to design WAN(L3VPN in volte use case)
orchestration graghs for SDNC and keep the design align with the L3VPN model in
Domain controllers(here 3rd party SPTN or IPRAN controller in volte usecase ).
If the original model is not expressed with DG graphs, we have no tools to
import it automatically into the SDNC.

We should design WAN descriptor in TOSCA with SDC independently and keep align
with the model in SDNC. Since the data model in SDNC is not TOSCA file nor yang
file, SDC can not import WAN model like importing VNF Descriptor in VNF case.

When instantiate volte service, SO will decompose the E2E Service Descriptor to
vIMS Descriptor, WAN Descriptor, vEPC Descriptor and send vIMS and vEPC to VFC.
There should be a module handle the WAN Descriptor. Where we intent to put this
module? in SO or SDNC? If the seed code of this module is ready or not?

After the module parse the WAN Descriptor, the parameters of L3VPN and
corresponding DG name will be extracted from the TOSCA package and send to SDNC
to trigger the DG excution of the pre-designed dericted gragh.

The pre-designed dericted gragh will call corresponding adaptors then the
adaptor will construct request with the parameters deliveried from SDNC DG, and
send request to 3rd party controller.

If my understanding is not correct, please point it out.

In summary, we have three key questions:

What kind of information should WAN Descriptor contain? L3vpn info? DG name
of SDN-C? Something else?

Which project, SO or SDNC, parse the TOSCA template?

Who will be responsible on this part of code(parse tosca template then
mapping to existing SDNC northband API)?

Best regards!

黄卓垚huangzhuoyao

职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.

深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755 F: +86 755
M: +86 xxx
E: huang.zhuo...@zte.com.cn
www.zte.com.cn___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Update] ONAP workflow design and executiondiscussion

2017-08-10 Thread zhao.huabing

Hi,




Meeting recording has been uploaded to this 
page:https://wiki.onap.org/display/DW/SDC+2017-8-11+ONAP+workflow+design+and+execution+discussion
 




@Michael, If you don't mind, I put the recording under the SDC weekly meeting 
page because workflow designer is part of SDC.




Thanks,

Huabing









Original Mail



Sender:  
To:    

Date: 2017/08/09 21:13
Subject: [onap-discuss] [Update] ONAP workflow design and executiondiscussion






This meeting is rescheduled to Thursday due to conflicts. Sorry for the late 
notification and inconvenience caused.

Hi there,

Huabing is inviting you to a scheduled Zoom meeting.

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

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

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 699 996 
International numbers available: 
https://zoom.us/zoomconference?m=_5QAuX9O-wb43xJqoNQjTlyYurEIrnWK



ONAP workflow design and execution discussion
This meeting is rescheduled to Thursday due to conflicts. Sorry for the late 
notification and inconvenience caused.Hi there,

Huabing is inviting you to a scheduled Zoom meeting.

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

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

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 699 996 
International numbers available: 
https://zoom.us/zoomconference?m=_5QAuX9O-wb43xJqoNQjTlyYurEIrnWK














When
Thu 2017-08-10 9pm – 10pm China Time - BeijingWhere
https://zoom.us/j/66 (map)Who
•
Huabing Zhao - creator

•
onap-discuss@lists.onap.org

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

[onap-discuss] Runtime artifacts

2017-08-10 Thread DeWayne Filppi

Does ONAP at runtime include repos for things such as Docker images. Python
packages or Ruby gems?  Or does every project have deal with such issues in
their own way?

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

[onap-discuss] 答复: [linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

2017-08-10 Thread fu.jinhua

Hi Andrew,Jess and Gary:

Thanks for your help, I can see the node for redis in Jenkins now.

But unit test for vfc-nfvo-lcm still can not passed, from the log in jenkins, I 
think redis is not started in the redis node, can you help me to check it?

Thanks,

Jinhua










原始邮件



发件人： 
收件人：张茂鹏10030173
抄送人：傅锦华10108953  
日 期 ：2017年08月11日 02:09
主 题 ：[linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP 
Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About CI job 
Script for python project in ONAP





Gary's changes have been merged in and the redis image has been built.
I've added a new minion template to allow the image to come online.

-Andy-

On 08/10/2017 09:55 AM, Gary Wu via RT wrote:
> 
> Sorry about that.  I’ve submitted a fix into ci-management: 
> https://gerrit.onap.org/r/#/c/7229/
> 
> Thanks,
> Gary
> 
> From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
> Sent: Wednesday, August 09, 2017 5:54 PM
> To: onap-helpd...@rt.linuxfoundation.org
> Cc: zhang.maope...@zte.com.cn Gary Wu  
> onap-discuss@lists.onap.org
> Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] 
> RE: About CI job Script for python project in ONAP
> 
> 
> Hi Jess,
> 
> I think Gary's script has some mistakes, you can see the following log
> 
> 18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
> such file or directory
> 
> Gary's Scripts(Path of redis-server and redis.conf are wrong)
> 
># 2. set conf file and init script
> 
> mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server
> 
> chmod +x /etc/init.d/redis-server
> 
> mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf
> 
> 
> 
> Thanks,
> 
> Jinhua
> 
> 
> 
> 
> 
> 
> 原始邮件
> 发件人： 
> >
> 收件人：张茂鹏10030173
> 抄送人：傅锦华10108953 > 
> >
> 日 期 ：2017年08月10日 07:01
> 主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
> CI job Script for python project in ONAP
> 
> 
> Dear Maopeng,
> 
> I am currently working on this.
> Looking at the current failures found here:
> https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console
> 
> Will let you know once I get this resolved
> 
> Thanks!
> Jess
> 
> 
> 
> 
> 

-- 
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] [ci-management] Where are python build products/packages

2017-08-10 Thread DeWayne Filppi

Is Nexus configured to host a pypi repo?  If not, here will python packages
fetch their references from?  If so, I don't see an python repo in Nexus.

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

[onap-discuss] Invitation: VoLTE [SO] / [SDNC] Interface discussion @ Fri Aug 11, 2017 7am - 8am (PDT) (onap-discuss@lists.onap.org)

2017-08-10 Thread kpaul

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20170811T14Z
DTEND:20170811T15Z
DTSTAMP:20170810T211624Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:1hqc0lhedng8rmakg4j5vm3...@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=dtimo...@att.com;X-NUM-GUESTS=0:mailto:dtimo...@att.com
CREATED:20170810T211624Z
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/409365333\n\nOr iPhone one-tap (US Toll):  +16465588656\,\,409365333# o
 r +14086380968\,\,409365333#\n\nOr Telephone:\nDial: +1 646 558 8656 (U
 S Toll) or +1 408 638 0968 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 409 365 333\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=vklJm4NMf3IDA0T8
 F3U6PB6gzd_9L9W7\n\n\n\nView your event at https://www.google.com/calendar/
 event?action=VIEW=MWhxYzBsaGVkbmc4cm1ha2c0ajV2bTNybmggb25hcC1kaXNjdXNzQ
 Gxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc
 2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNGU2Y2JmNGRlZTJjZmFiYTcyZT
 QzNDgzNTBlNmY5MTgyZTliYjg4Mw=America/Los_Angeles=en.
LAST-MODIFIED:20170810T211624Z
LOCATION:https://zoom.us/j/409365333
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY: VoLTE [SO] / [SDNC] Interface discussion
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] [sdc][so][sdnc] VoLTE WAN service definition

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="Yang Xu (Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SHADMI, DA
 VID":MAILTO:ds2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="LANDO, MIC
 HAEL":MAILTO:ml6...@intl.att.com
DESCRIPTION;LANGUAGE=en-US:When: Friday\, August 11\, 2017 10:00 AM-11:00 A
 M (UTC-05:00) Eastern Time (US & Canada).\nWhere: https://zoom.us/j/423860
 8129\n\nNote: The GMT offset above does not reflect daylight saving time a
 djustments.\n\n*~*~*~*~*~*~*~*~*~*\n\nAll\,\n\nAs we agreed in today’s S
 O/SDNC meeting\, we will continue the discussion of WAN service definition
  for SDC/SO/SDNC.\n\nThanks\,\n-Yang\n\n\nJoin from PC\, Mac\, Linux\, iOS
  or Android: https://zoom.us/j/4238608129\n\nOr iPhone one-tap (US Toll): 
  +16465588656\,\,4238608129# or +14086380968\,\,4238608129#\n\nOr Telephon
 e:\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\n
 Meeting ID: 423 860 8129\nInternational numbers available: https://zoo
 m.us/zoomconference?m=wv9nsPjYiqxhUXAV_XO2NUX9o0bEGNxN\n\n\n
SUMMARY;LANGUAGE=en-US:[sdc][so][sdnc] VoLTE WAN service definition 
DTSTART;TZID=Eastern Standard Time:20170811T10
DTEND;TZID=Eastern Standard Time:20170811T11
UID:04008200E00074C5B7101A82E008C057A736F611D301000
 010004541E9E33C7A3C428303C7D29965AD13
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170810T205223Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:https://zoom.us/j/4238608129
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:1688897505
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] vCPE: Consider multi-cloud support in R2

2017-08-10 Thread Kang Xi

Hi Yoav,

The statement is certainly valid within the context of the assumption. I'm 
pleased that there is no changes needed for the R1 deliverables.

Regards,
Kang

From: Yoav Kluger [mailto:yoav.klu...@amdocs.com]
Sent: Wednesday, August 09, 2017 18:23
To: Kang Xi ; onap-discuss@lists.onap.org
Cc: Yunxia Chen ; Pawłowski Michał 1 - Korpo 
; FREEMAN, BRIAN D 
Subject: RE: vCPE: Consider multi-cloud support in R2

Kang, all,

Sorry could not attend the meeting (which collided with the ARC meeting).

I would propose to not view the connectivity between clouds as a problem, or 
use case, ONAP needs to solve. Service provides who have deployed multiple 
clouds have typically also established connectivity between them, in most cases 
via some type of a L2 VPN. When ONAP instantiates VNFs there is an assumption 
that it can then communicate with them, e.g. for configuration or closed loop 
operations, over an OAM overlay network. We do not bother showing how this OAM 
network is routed, and in particular how SDNC, as an example, can communicate 
with a VNF which happens to be instantiated in a remote DC. We assume whatever 
underlay is need is in place which allows communicating with all VNFs over the 
one OAM network.

Similarly, if two VNFs are assumed to communicate over regular IP networking 
(not to be confused with service chaining), then, without loss of generality, 
we can showcase them in one DC, assuming that if in real life they were to be 
instantiated in two DCs, then the inter-dc connectivity already in place would 
enable them to communicate just as well.

The other alternative would be that we would have to showcase each VNF in a 
separate DC - to "make sure" the use case works under any deployment scenario. 
This obviously does not make sense, and fortunately is also not needed for the 
reasons sated above.

I would therefore submit that the vCPE use case, which instantiates all its 
VNFs in a single DC, is sufficient to showcase ONAP's capability to instantiate 
and manage a vCPE use case under any deployment.

Thanks,
Yoav Kluger
Amdocs Technology
+1(201)912-7294
+972-54-4850278
[amdocs-a]

From: Kang Xi [mailto:kang...@huawei.com]
Sent: Tuesday, August 08, 2017 11:37 AM
To: onap-discuss@lists.onap.org
Cc: Yunxia Chen >; 
Pawłowski Michał 1 - Korpo 
>; Yoav 
Kluger >; FREEMAN, BRIAN 
D >
Subject: vCPE: Consider multi-cloud support in R2

Hi All,

During the meeting "[integration] vCPE for R1: Support multiple clouds or not?" 
(Aug. 8 11:00-11:25am EST), the attendees unanimously concluded to leave the 
support for multiple clouds to the next release. For R1, the release 
implementation will only target a single cloud set up.

The rationale behind the above conclusion is that multi-cloud support, while 
technically feasible, would need quite some discussions to decide on multiple 
issues including lab set up, network set up, work flow design, etc. Adding it 
to R1 would further tighten the R1 schedule.

The list of attendees is shown below:

[cid:image002.jpg@01D311F8.BD2163C0]
Regards,
Kang

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] [sdc][so][sdnc]

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="Yang Xu (Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SHADMI, DA
 VID":MAILTO:ds2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="LANDO, MIC
 HAEL":MAILTO:ml6...@intl.att.com
DESCRIPTION;LANGUAGE=en-US:When: Friday\, August 11\, 2017 10:00 AM-11:00 A
 M (UTC-05:00) Eastern Time (US & Canada).\nWhere: https://zoom.us/j/423860
 8129\n\nNote: The GMT offset above does not reflect daylight saving time a
 djustments.\n\n*~*~*~*~*~*~*~*~*~*\n\nAll\,\n\nAs we agreed in today’s S
 O/SDNC meeting\, we will continue the discussion of WAN service definition
  for SDC/SO/SDNC.\n\nThanks\,\n-Yang\n\n\nJoin from PC\, Mac\, Linux\, iOS
  or Android: https://zoom.us/j/4238608129\n\nOr iPhone one-tap (US Toll): 
  +16465588656\,\,4238608129# or +14086380968\,\,4238608129#\n\nOr Telephon
 e:\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\n
 Meeting ID: 423 860 8129\nInternational numbers available: https://zoo
 m.us/zoomconference?m=wv9nsPjYiqxhUXAV_XO2NUX9o0bEGNxN\n\n\n
SUMMARY;LANGUAGE=en-US:[sdc][so][sdnc]
DTSTART;TZID=Eastern Standard Time:20170811T10
DTEND;TZID=Eastern Standard Time:20170811T11
UID:04008200E00074C5B7101A82E008C057A736F611D301000
 010004541E9E33C7A3C428303C7D29965AD13
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170810T203739Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/4238608129
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1688897505
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

[onap-discuss] [ONAP Helpdesk #44169] [integration] Mandatory Jira ID in Gerrit change submissions

2017-08-10 Thread Jessica Wagantall via RT

Thanks Gary, 

I am adding the recording of this approval too:

http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-08-10-13.53.html
AGREED: TSC approve the Upstream development guidelines identified on slides 4 
& 5 "ONAP Upstream Discussion Version 2.0 (kennypaul, 14:47:20)

I will look into it. 
Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

2017-08-10 Thread Jessica Wagantall via RT

Thanks so much for this Andy!

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

[onap-discuss] [integration] Mandatory Jira ID in Gerrit change submissions

Hi helpdesk,

This morning the TSC has approved making Jira IDs mandatory in Gerrit change 
submissions.  Can you make the change?

Thanks,
Gary


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

Re: [onap-discuss] vCPE: Consider multi-cloud support in R2

2017-08-10 Thread Yoav Kluger

Gaurav,

Performance and latency KPIs have not been defined for this use case, these 
will depend on the specific VNFs selected by each operator rather than ONAP as 
the MANO system.

But I do not see a reason why multiple instances of the vCPE service cannot be 
brought up. They will all be instantiated in the same DC, but will run 
separately.

Thanks,
Yoav Kluger
Amdocs Technology
+1(201)912-7294
+972-54-4850278
[amdocs-a]

From: Gaurav Gupta (c) [mailto:guptagau...@vmware.com]
Sent: Wednesday, August 09, 2017 11:50 PM
To: Yoav Kluger ; Kang Xi 
Cc: onap-discuss@lists.onap.org
Subject: Re: vCPE: Consider multi-cloud support in R2


Yoav , Kang Xi



if the below two are not goal



a.1- If performance  or latency on VxLAN is not being monitored and not the 
goal for individual  vCPE

a.2 - Also if multiple Instances of vCPE existing at the same time  is not to 
be supported



Then whether vCPE is  deployed across  multiple DC or single DC it makes no 
difference .Hence I would agree  to what is described below .



with best regards

gaurav




From: 
onap-discuss-boun...@lists.onap.org 
>
 on behalf of Yoav Kluger 
>
Sent: 10 August 2017 03:52:41
To: Kang Xi; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] vCPE: Consider multi-cloud support in R2


Kang, all,



Sorry could not attend the meeting (which collided with the ARC meeting).



I would propose to not view the connectivity between clouds as a problem, or 
use case, ONAP needs to solve. Service provides who have deployed multiple 
clouds have typically also established connectivity between them, in most cases 
via some type of a L2 VPN. When ONAP instantiates VNFs there is an assumption 
that it can then communicate with them, e.g. for configuration or closed loop 
operations, over an OAM overlay network. We do not bother showing how this OAM 
network is routed, and in particular how SDNC, as an example, can communicate 
with a VNF which happens to be instantiated in a remote DC. We assume whatever 
underlay is need is in place which allows communicating with all VNFs over the 
one OAM network.



Similarly, if two VNFs are assumed to communicate over regular IP networking 
(not to be confused with service chaining), then, without loss of generality, 
we can showcase them in one DC, assuming that if in real life they were to be 
instantiated in two DCs, then the inter-dc connectivity already in place would 
enable them to communicate just as well.



The other alternative would be that we would have to showcase each VNF in a 
separate DC - to "make sure" the use case works under any deployment scenario. 
This obviously does not make sense, and fortunately is also not needed for the 
reasons sated above.



I would therefore submit that the vCPE use case, which instantiates all its 
VNFs in a single DC, is sufficient to showcase ONAP's capability to instantiate 
and manage a vCPE use case under any deployment.



Thanks,

Yoav Kluger

Amdocs Technology

+1(201)912-7294

+972-54-4850278

[amdocs-a]



From: Kang Xi [mailto:kang...@huawei.com]
Sent: Tuesday, August 08, 2017 11:37 AM
To: onap-discuss@lists.onap.org
Cc: Yunxia Chen >; 
Pawłowski Michał 1 - Korpo 
>; Yoav 
Kluger >; FREEMAN, BRIAN 
D >
Subject: vCPE: Consider multi-cloud support in R2



Hi All,



During the meeting "[integration] vCPE for R1: Support multiple clouds or not?" 
(Aug. 8 11:00-11:25am EST), the attendees unanimously concluded to leave the 
support for multiple clouds to the next release. For R1, the release 
implementation will only target a single cloud set up.



The rationale behind the above conclusion is that multi-cloud support, while 
technically feasible, would need quite some discussions to decide on multiple 
issues including lab set up, network set up, work flow design, etc. Adding it 
to R1 would further tighten the R1 schedule.



The list of attendees is shown below:



[cid:image005.jpg@01D311E7.A317A630]

Regards,

Kang


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
This message and the information contained herein is

Re: [onap-discuss] [integration] [bootstrap] vagrant-onap project available into Integration repo

2017-08-10 Thread Morales, Victor

Thanks for this great explanation Erick, I double-checked to my computer and I 
don’t have that plugin installed and it’s using Guest Additions Version: 
4.3.36.  So apparently this is an issue in the way that Vagrant masks mounted 
directories, isn’t it? I only think about two possible alternatives for solving 
this error


1.   Ensuring that vagrant-vbguest is installed but disable its auto update 
feature and report that to vagrant to solve that issue. The code into the 
Vagrantfile should be something like:

if not Vagrant.has_plugin?('vagrant-vbguest')
  system 'vagrant plugin install vagrant-vbguest'
  raise 'vagrant-vbguest was installed but it requires to execute again'
end
config.vbguest.auto_update = false


2.   Raise an error when the plugin is installed and force its uninstall

if Vagrant.has_plugin?('vagrant-vbguest')
  system 'vagrant plugin uninstall vagrant-vbguest'
  raise 'vagrant-vbguest was uninstalled but it requires to execute again'
end

I would be nice to have a way to restrict the Guest Additions Version,

Thanks
Victor Morales

From: "Multanen, Eric W" 
Date: Thursday, August 10, 2017 at 12:25 PM
To: Victor Morales , "onap-discuss@lists.onap.org" 

Subject: RE: [onap-discuss] [integration] [bootstrap] vagrant-onap project 
available into Integration repo

Here’s a summary of the issue and how I resolved / worked around it:


1.  On the ‘vagrant up’, Guest Additions Version of the guest box is listed 
as 4.3.36

2.  My host virtual box version is 5.1.26

3.  The vagrant-vbguest plugin was installed on the host, so it would mount 
a newer version of the guest additions iso in the guest and install it (I 
presume because it detected the older guest version).

a.  The guest additions are installed in the guest /opt directory and then 
links to /opt subdirectories are made for files and binaries in /sbin, etc. to 
install.

4.  Then, the host ./opt directory is mounted onto the guest /opt 
directory.  This succeeds - /opt on the guest is now shared with ./opt on the 
host.

5.  But, now the guest additions installed in /opt are masked by the 
mounted ./opt directory from the host.  Subsequent syncing (/lib, .m2, …) fails.

a.  And the vagrant up fails at this point – the vm is up, but process of 
bringing up mthe onap project fails

By uninstalling the vagrant-vbguest plugin on the host, a newer version of the 
guest additions is not installed, so the masking of /opt in the guest does not 
occur, all directories needing to sync are synced, and the bring up process is 
able to continue.


From: Morales, Victor
Sent: Thursday, August 10, 2017 9:47 AM
To: Multanen, Eric W ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
project available into Integration repo

Hi Eric,

Adding more documentation is always welcome so if you find something that helps 
to clarify the usage of this tool I encourage to submit the patch (I submitted 
a patch to generate html documentation and it also includes an installation 
guide[1]).  For submitting a bug, I’d need more information about it, like

Do you the log of the error messages?
Did you only have issues syncing /opt folder? What about /lib and /.m2?
What version of Guest Additions did you have?
Once that you uninstall the guest additions, are the environments provisioned 
without any error?

Thanks
Victor Morales

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


From: "Multanen, Eric W" 
>
Date: Thursday, August 10, 2017 at 10:43 AM
To: Victor Morales >, 
"onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
project available into Integration repo

Hello,

I’ve been trying this out (Windows 10 host, virtualbox, individual projects) 
for the past couple weeks.

I ultimately found out that the source of the problems I encountered getting 
synced folders/directories to work was a conflict between
the virtual box guest additions using the /opt directory of the guest and this 
project syncing the /opt directory with the host.  I got things to work
by uninstalling the vagrant guest additions plugin.

I’d be happy to either write up a bug report, or alternatively, add some 
documentation for best known methods or tips on usage.

Any preference?

Eric



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Wednesday, July 26, 2017 3:58 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [all] [integration]

[onap-discuss] [linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

2017-08-10 Thread Andrew Grimberg via RT

Gary's changes have been merged in and the redis image has been built.
I've added a new minion template to allow the image to come online.

-Andy-

On 08/10/2017 09:55 AM, Gary Wu via RT wrote:
> 
> Sorry about that.  I’ve submitted a fix into ci-management: 
> https://gerrit.onap.org/r/#/c/7229/
> 
> Thanks,
> Gary
> 
> From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
> Sent: Wednesday, August 09, 2017 5:54 PM
> To: onap-helpd...@rt.linuxfoundation.org
> Cc: zhang.maope...@zte.com.cn; Gary Wu ; 
> onap-discuss@lists.onap.org
> Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] 
> RE: About CI job Script for python project in ONAP
> 
> 
> Hi Jess,
> 
> I think Gary's script has some mistakes, you can see the following log
> 
> 18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
> such file or directory
> 
> Gary's Scripts(Path of redis-server and redis.conf are wrong)
> 
># 2. set conf file and init script
> 
> mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server
> 
> chmod +x /etc/init.d/redis-server
> 
> mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf
> 
> 
> 
> Thanks,
> 
> Jinhua
> 
> 
> 
> 
> 
> 
> 原始邮件
> 发件人： 
> >;
> 收件人：张茂鹏10030173;
> 抄送人：傅锦华10108953; >; 
> >;
> 日 期 ：2017年08月10日 07:01
> 主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
> CI job Script for python project in ONAP
> 
> 
> Dear Maopeng,
> 
> I am currently working on this.
> Looking at the current failures found here:
> https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console
> 
> Will let you know once I get this resolved
> 
> Thanks!
> Jess
> 
> 
> 
> 
> 

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




bin0XKCAnBr98.bin
Description: application/rt-original-message
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to review

2017-08-10 Thread Andrew Grimberg

On 08/10/2017 10:31 AM, DRAGOSH, PAMELA L (PAM) wrote:
> My understanding was that when someone submits code for review, that
> committers automatically get email notification for it and also
> automatically get added to the list of reviewers. However, this has been
> inconsistent.

The ONAP Gerrit is not configured in any way to automatically add
reviewers to a change.

There are two plugins available for doing this sort of work:

reviewers - which won't work because we use and LDAP backend for
accounts and it requires the defined auto-reviewers to be local accounts
and groups

maintainers - which the fd.io community, and Cisco in explicit,
developed for their Gerrit which utilizes a MAINTAINERS file in the repo
for managing the automatic reviewer setup. I don't recommend this one
(yet) as they're still working out the bugs in it ;)

If you've been getting added "automatically" then it would be from
someone adding you as a reviewer. If, however, you leave a review then
you're automatically added as a watcher for any future changes.

> Being a committer, I have noticed that sometimes I am added as a
> reviewer automatically, while other times I am not. Not sure why not. I
> do utilize the “watch” projects functionality so that I don’t miss
> something because of this inconsistency.

I recommend that committers aways setup watches on projects that they're
a commit for. I, and the more active LF RE's for ONAP do this for the
ci-management project.

-Andy-

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

signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to review

To my knowledge, Gerrit doesn’t automatically add reviewers to changes on 
submission.  However, if you add a comment/reply to a change, then it 
automatically adds you as a reviewer to that change, and will notify you of any 
future amendments thereof.

Thanks,
Gary

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Thursday, August 10, 2017 10:31 AM
To: Gary Wu ; eric.deb...@orange.com; 
onap-...@lists.onap.org; onap-discuss@lists.onap.org
Cc: RICHOMME Morgan IMT/OLN 
Subject: Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to 
review

My understanding was that when someone submits code for review, that committers 
automatically get email notification for it and also automatically get added to 
the list of reviewers. However, this has been inconsistent.

Being a committer, I have noticed that sometimes I am added as a reviewer 
automatically, while other times I am not. Not sure why not. I do utilize the 
“watch” projects functionality so that I don’t miss something because of this 
inconsistency.

Can someone from LF clarify the consistency? Or is my understanding incorrect?

Thanks,

Pam


From: 
>
 on behalf of Gary Wu >
Date: Thursday, August 10, 2017 at 1:20 PM
To: "eric.deb...@orange.com" 
>, 
"onap-...@lists.onap.org" 
>, 
"onap-discuss@lists.onap.org" 
>
Cc: RICHOMME Morgan IMT/OLN 
>
Subject: Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to 
review

On notifications:  Gerrit has built-in support to send email notifications on 
code changes.  There are two methods:


1.   The contributor can explicitly add a list of reviewers to the proposed 
change, which will trigger a notification to those individuals.  This should 
ideally be done after all expected amendments to the change are completed, and 
after Jenkins has verified the change.

2.   Anyone can subscribe to be notified of changes in any particular repo, 
via the “Watched Projects” section in their profile settings.

I would recommend that all committers subscribe to watch changes to the 
projects for which they are committers for.

Thanks,
Gary

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com
Sent: Thursday, August 10, 2017 6:30 AM
To: onap-...@lists.onap.org
Cc: RICHOMME Morgan IMT/OLN 
>
Subject: [onap-tsc] Code Review: how to avoid long delay to review

Hello

There was a code review pending since 5 days due to a lack of reviewers. I 
think we should adopt some best practices to avoid such delay.
A committer should inform the PTL and a list of reviewers by mail (typically 
the project committers and other people involved in the project)


OPNFV is listing all the committers (they can provide a +2 code review) in a 
dedicated file INFO for each repo:

https://git.opnfv.org/functest/tree/INFO

https://git.opnfv.org/promise/tree/INFO



OPNFV also defined some rules for committers promotions and removal that should 
inspire us.

https://wiki.opnfv.org/display/DEV/Committer+Promotions

https://wiki.opnfv.org/display/DEV/Committer+Removal

Thanks @Morgan (OPNFV Ambassador & TSC Member) for the links

Regards

Eric

Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to review

2017-08-10 Thread DRAGOSH, PAMELA L (PAM)

My understanding was that when someone submits code for review, that committers 
automatically get email notification for it and also automatically get added to 
the list of reviewers. However, this has been inconsistent.

Being a committer, I have noticed that sometimes I am added as a reviewer 
automatically, while other times I am not. Not sure why not. I do utilize the 
“watch” projects functionality so that I don’t miss something because of this 
inconsistency.

Can someone from LF clarify the consistency? Or is my understanding incorrect?

Thanks,

Pam


From:  on behalf of Gary Wu 

Date: Thursday, August 10, 2017 at 1:20 PM
To: "eric.deb...@orange.com" , 
"onap-...@lists.onap.org" , 
"onap-discuss@lists.onap.org" 
Cc: RICHOMME Morgan IMT/OLN 
Subject: Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to 
review

On notifications:  Gerrit has built-in support to send email notifications on 
code changes.  There are two methods:


1.   The contributor can explicitly add a list of reviewers to the proposed 
change, which will trigger a notification to those individuals.  This should 
ideally be done after all expected amendments to the change are completed, and 
after Jenkins has verified the change.

2.   Anyone can subscribe to be notified of changes in any particular repo, 
via the “Watched Projects” section in their profile settings.

I would recommend that all committers subscribe to watch changes to the 
projects for which they are committers for.

Thanks,
Gary

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: Thursday, August 10, 2017 6:30 AM
To: onap-...@lists.onap.org
Cc: RICHOMME Morgan IMT/OLN 
Subject: [onap-tsc] Code Review: how to avoid long delay to review

Hello

There was a code review pending since 5 days due to a lack of reviewers. I 
think we should adopt some best practices to avoid such delay.
A committer should inform the PTL and a list of reviewers by mail (typically 
the project committers and other people involved in the project)


OPNFV is listing all the committers (they can provide a +2 code review) in a 
dedicated file INFO for each repo:

https://git.opnfv.org/functest/tree/INFO

https://git.opnfv.org/promise/tree/INFO



OPNFV also defined some rules for committers promotions and removal that should 
inspire us.

https://wiki.opnfv.org/display/DEV/Committer+Promotions

https://wiki.opnfv.org/display/DEV/Committer+Removal

Thanks @Morgan (OPNFV Ambassador & TSC Member) for the links

Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

Re: [onap-discuss] [integration] [bootstrap] vagrant-onap project available into Integration repo

2017-08-10 Thread Multanen, Eric W

Here’s a summary of the issue and how I resolved / worked around it:


1.  On the ‘vagrant up’, Guest Additions Version of the guest box is listed 
as 4.3.36

2.  My host virtual box version is 5.1.26

3.  The vagrant-vbguest plugin was installed on the host, so it would mount 
a newer version of the guest additions iso in the guest and install it (I 
presume because it detected the older guest version).

a.  The guest additions are installed in the guest /opt directory and then 
links to /opt subdirectories are made for files and binaries in /sbin, etc. to 
install.

4.  Then, the host ./opt directory is mounted onto the guest /opt 
directory.  This succeeds - /opt on the guest is now shared with ./opt on the 
host.

5.  But, now the guest additions installed in /opt are masked by the 
mounted ./opt directory from the host.  Subsequent syncing (/lib, .m2, …) fails.

a.  And the vagrant up fails at this point – the vm is up, but process of 
bringing up mthe onap project fails

By uninstalling the vagrant-vbguest plugin on the host, a newer version of the 
guest additions is not installed, so the masking of /opt in the guest does not 
occur, all directories needing to sync are synced, and the bring up process is 
able to continue.


From: Morales, Victor
Sent: Thursday, August 10, 2017 9:47 AM
To: Multanen, Eric W ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
project available into Integration repo

Hi Eric,

Adding more documentation is always welcome so if you find something that helps 
to clarify the usage of this tool I encourage to submit the patch (I submitted 
a patch to generate html documentation and it also includes an installation 
guide[1]).  For submitting a bug, I’d need more information about it, like

Do you the log of the error messages?
Did you only have issues syncing /opt folder? What about /lib and /.m2?
What version of Guest Additions did you have?
Once that you uninstall the guest additions, are the environments provisioned 
without any error?

Thanks
Victor Morales

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


From: "Multanen, Eric W" 
>
Date: Thursday, August 10, 2017 at 10:43 AM
To: Victor Morales >, 
"onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
project available into Integration repo

Hello,

I’ve been trying this out (Windows 10 host, virtualbox, individual projects) 
for the past couple weeks.

I ultimately found out that the source of the problems I encountered getting 
synced folders/directories to work was a conflict between
the virtual box guest additions using the /opt directory of the guest and this 
project syncing the /opt directory with the host.  I got things to work
by uninstalling the vagrant guest additions plugin.

I’d be happy to either write up a bug report, or alternatively, add some 
documentation for best known methods or tips on usage.

Any preference?

Eric



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Wednesday, July 26, 2017 3:58 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project 
available into Integration repo

ONAPers,

The vagrant-onap project started as an alternative to deploy ONAP services in 
Virtual Machines hosted locally without the need of an OpenStack deployment.  
After several changes and additions to this project, its goal has changed to 
provision a Development Environment.  Its current implementation support 
different providers (like VirtualBox, Libvirt and OpenStack) and has been 
tested in some OS(like Ubuntu, Mac OS).  This is an ongoing effort to collect 
instructions and standardize the methods to build and compile ONAP artifacts, 
as you can expect there are many things that are still missed so I encourage to 
everyone to take a look of the scripts placed into lib folder[1] and improve 
the documentation[2][3]. We have plans to add more Unit Tests to this 
project[4] to validate any change.

Thanks
Victor Morales
irc: electrocucaracha

[1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib
[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md
[3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source
[4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Code Review: how to avoid long delay to review

On notifications:  Gerrit has built-in support to send email notifications on 
code changes.  There are two methods:


1.   The contributor can explicitly add a list of reviewers to the proposed 
change, which will trigger a notification to those individuals.  This should 
ideally be done after all expected amendments to the change are completed, and 
after Jenkins has verified the change.

2.   Anyone can subscribe to be notified of changes in any particular repo, 
via the "Watched Projects" section in their profile settings.

I would recommend that all committers subscribe to watch changes to the 
projects for which they are committers for.

Thanks,
Gary

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of eric.deb...@orange.com
Sent: Thursday, August 10, 2017 6:30 AM
To: onap-...@lists.onap.org
Cc: RICHOMME Morgan IMT/OLN 
Subject: [onap-tsc] Code Review: how to avoid long delay to review

Hello

There was a code review pending since 5 days due to a lack of reviewers. I 
think we should adopt some best practices to avoid such delay.
A committer should inform the PTL and a list of reviewers by mail (typically 
the project committers and other people involved in the project)


OPNFV is listing all the committers (they can provide a +2 code review) in a 
dedicated file INFO for each repo:

https://git.opnfv.org/functest/tree/INFO

https://git.opnfv.org/promise/tree/INFO



OPNFV also defined some rules for committers promotions and removal that should 
inspire us.

https://wiki.opnfv.org/display/DEV/Committer+Promotions

https://wiki.opnfv.org/display/DEV/Committer+Removal

Thanks @Morgan (OPNFV Ambassador & TSC Member) for the links

Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

[onap-discuss] [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

2017-08-10 Thread Gary Wu via RT

Sorry about that.  I’ve submitted a fix into ci-management: 
https://gerrit.onap.org/r/#/c/7229/

Thanks,
Gary

From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
Sent: Wednesday, August 09, 2017 5:54 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: zhang.maope...@zte.com.cn; Gary Wu ; 
onap-discuss@lists.onap.org
Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: 
About CI job Script for python project in ONAP


Hi Jess,

I think Gary's script has some mistakes, you can see the following log

18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
such file or directory

Gary's Scripts(Path of redis-server and redis.conf are wrong)

   # 2. set conf file and init script

mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server

chmod +x /etc/init.d/redis-server

mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf



Thanks,

Jinhua






原始邮件
发件人： 
>;
收件人：张茂鹏10030173;
抄送人：傅锦华10108953; >; 
>;
日 期 ：2017年08月10日 07:01
主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
CI job Script for python project in ONAP


Dear Maopeng,

I am currently working on this.
Looking at the current failures found here:
https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console

Will let you know once I get this resolved

Thanks!
Jess





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

Re: [onap-discuss] [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

Sorry about that.  I’ve submitted a fix into ci-management: 
https://gerrit.onap.org/r/#/c/7229/

Thanks,
Gary

From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
Sent: Wednesday, August 09, 2017 5:54 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: zhang.maope...@zte.com.cn; Gary Wu ; 
onap-discuss@lists.onap.org
Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: 
About CI job Script for python project in ONAP


Hi Jess,

I think Gary's script has some mistakes, you can see the following log

18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
such file or directory

Gary's Scripts(Path of redis-server and redis.conf are wrong)

   # 2. set conf file and init script

mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server

chmod +x /etc/init.d/redis-server

mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf



Thanks,

Jinhua






原始邮件
发件人： 
>;
收件人：张茂鹏10030173;
抄送人：傅锦华10108953; >; 
>;
日 期 ：2017年08月10日 07:01
主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
CI job Script for python project in ONAP


Dear Maopeng,

I am currently working on this.
Looking at the current failures found here:
https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console

Will let you know once I get this resolved

Thanks!
Jess




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

Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project available into Integration repo

2017-08-10 Thread Morales, Victor

Hi Eric,

Adding more documentation is always welcome so if you find something that helps 
to clarify the usage of this tool I encourage to submit the patch (I submitted 
a patch to generate html documentation and it also includes an installation 
guide[1]).  For submitting a bug, I’d need more information about it, like

Do you the log of the error messages?
Did you only have issues syncing /opt folder? What about /lib and /.m2?
What version of Guest Additions did you have?
Once that you uninstall the guest additions, are the environments provisioned 
without any error?

Thanks
Victor Morales

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


From: "Multanen, Eric W" 
Date: Thursday, August 10, 2017 at 10:43 AM
To: Victor Morales , "onap-discuss@lists.onap.org" 

Subject: RE: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
project available into Integration repo

Hello,

I’ve been trying this out (Windows 10 host, virtualbox, individual projects) 
for the past couple weeks.

I ultimately found out that the source of the problems I encountered getting 
synced folders/directories to work was a conflict between
the virtual box guest additions using the /opt directory of the guest and this 
project syncing the /opt directory with the host.  I got things to work
by uninstalling the vagrant guest additions plugin.

I’d be happy to either write up a bug report, or alternatively, add some 
documentation for best known methods or tips on usage.

Any preference?

Eric



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Wednesday, July 26, 2017 3:58 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project 
available into Integration repo

ONAPers,

The vagrant-onap project started as an alternative to deploy ONAP services in 
Virtual Machines hosted locally without the need of an OpenStack deployment.  
After several changes and additions to this project, its goal has changed to 
provision a Development Environment.  Its current implementation support 
different providers (like VirtualBox, Libvirt and OpenStack) and has been 
tested in some OS(like Ubuntu, Mac OS).  This is an ongoing effort to collect 
instructions and standardize the methods to build and compile ONAP artifacts, 
as you can expect there are many things that are still missed so I encourage to 
everyone to take a look of the scripts placed into lib folder[1] and improve 
the documentation[2][3]. We have plans to add more Unit Tests to this 
project[4] to validate any change.

Thanks
Victor Morales
irc: electrocucaracha

[1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib
[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md
[3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source
[4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project available into Integration repo

2017-08-10 Thread Multanen, Eric W

Hello,

I’ve been trying this out (Windows 10 host, virtualbox, individual projects) 
for the past couple weeks.

I ultimately found out that the source of the problems I encountered getting 
synced folders/directories to work was a conflict between
the virtual box guest additions using the /opt directory of the guest and this 
project syncing the /opt directory with the host.  I got things to work
by uninstalling the vagrant guest additions plugin.

I’d be happy to either write up a bug report, or alternatively, add some 
documentation for best known methods or tips on usage.

Any preference?

Eric



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Wednesday, July 26, 2017 3:58 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap project 
available into Integration repo

ONAPers,

The vagrant-onap project started as an alternative to deploy ONAP services in 
Virtual Machines hosted locally without the need of an OpenStack deployment.  
After several changes and additions to this project, its goal has changed to 
provision a Development Environment.  Its current implementation support 
different providers (like VirtualBox, Libvirt and OpenStack) and has been 
tested in some OS(like Ubuntu, Mac OS).  This is an ongoing effort to collect 
instructions and standardize the methods to build and compile ONAP artifacts, 
as you can expect there are many things that are still missed so I encourage to 
everyone to take a look of the scripts placed into lib folder[1] and improve 
the documentation[2][3]. We have plans to add more Unit Tests to this 
project[4] to validate any change.

Thanks
Victor Morales
irc: electrocucaracha

[1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib
[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md
[3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source
[4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Register Now - ONAP Face To Face Developer Event in Paris-Saclay France

2017-08-10 Thread Phil Robb

Ah.  Thank you very much Nagesha for pointing this out.

Best,

Phil.

On Thu, Aug 10, 2017 at 5:02 AM, Subramanya, Nagesha (Nokia - IN/Bangalore)
 wrote:

> Below mail requires correction in terms of dates …
>
>
>
> Monday, Sept. 25th, 13:00 - 17:00:  Early Bird Sessions (Optional) for
> those able to arrive on Monday
>
> Tuesday, Sept. 26th, 09:00 - 17:00: Main Developer Forum
>
> Wednesday, Sept. 27th, 09:00 - 17:00: Main Developer Forum
>
> Thursday, Sept 28th, 09:00 - 15:00: Follow-on Unconference Sessions
>
>
>
>
>
> Regards,
>
> Nagesha
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] *On Behalf Of *Phil Robb
> *Sent:* Wednesday, August 09, 2017 2:39 AM
> *To:* onap-discuss@lists.onap.org
> *Cc:* Lara Taback ; onap-tsc <
> onap-...@lists.onap.org>
> *Subject:* [onap-tsc] Register Now - ONAP Face To Face Developer Event in
> Paris-Saclay France
>
>
>
> Hello ONAP Community Members:
>
>
>
> We have confirmed the following high level agenda for the next ONAP
> Developer Face to Face meeting to be held at the Nokia facility in
> Paris-Saclay, France.
>
>
>
> Monday, Sept. 25th, 13:00 - 17:00:  Early Bird Sessions (Optional) for
> those able to arrive on Monday
>
> Tuesday, Sept. 25th, 09:00 - 17:00: Main Developer Forum
>
> Wednesday, Sept. 26th, 09:00 - 17:00: Main Developer Forum
>
> Thursday, Sept 27th, 09:00 - 15:00: Follow-on Unconference Sessions
>
>
>
> A detailed agenda will be provided as the event nears.  We are soliciting
> topics for the event on the following wiki page:  https://wiki.onap.org/
> display/DW/September+26-28+Topics
>
>
>
> Please review this page, and put your name down for sessions you would
> like to participate in, and also add any session(s) you would like to lead
> or see discussed.
>
>
>
> Please register for the event at your earliest convenience here:
> https://www.regonline.com/ONAPDeveloperParis
>
>
>
> Details on the venue, local hotels and how to receive Visa Invitation
> letters will be mailed to you along with your Registration Confirmation.
> For your convenience, that information is also provided below
>
>
>
>
>
> Venue
>
> Nokia Paris-Saclay
>
> Route de Villejust
>
> 91620 Nozay
>
> France
>
> Phone: +33 01 60 40 60 40 <+33%201%2060%2040%2060%2040>
>
>
>
> Nearby Hotels
>
> Below is a list of hotels within 7km of the Nokia facility
>
> Best Western Hotel L'Oree, Saulx Les Chartreux
>
> Route de Montlhery
>
> 91160 Saulx Les Chartreux , France
>
>
>
> Hotel Mercure Paris Sud Les Ulis Courtaboeuf
>
> 3 Rue Rio Solado
>
> 91952 Les Ulis, France
>
> +33 1 69 07 63 96 <+33%201%2069%2007%2063%2096>
>
>
>
> Meals
>
> Nokia and ONAP will be hosting beverages and breaks throughout the
> conference. Please be sure to have breakfast prior to arriving each
> morning. The group will be eating in the cafeteria on campus each day, at
> your own expense.
>
>
>
> Cancellation/No-Show Fee
>
> There is no cost to participate in the ONAP Developer Event. You will only
> be charged a cancellation/no-show fee of $50.00 USD if you do not cancel by
> 08:00 PST on Tuesday, September 19 or do not attend the event.
>
>
>
> Visa Information
>
> Please visit http://events.linuxfoundation.org/visa-request to request a
> visa letter.
>
>
>
> Thanks in advance for participating in this event.  It will be our last
> opportunity for face to face work during our 1st release cycle.
>
>
>
> If you have any questions or concerns regarding this event, please contact
> the ONAP Events team at eve...@onap.org
>
>
>
> Best,
>
>
>
> Phil.
>
> --
>
> Phil Robb
>
> Executive Director, OpenDaylight Project
>
> VP Operations - Networking & Orchestration, The Linux Foundation
>
> (O) 970-229-5949 <(970)%20229-5949>
>
> (M) 970-420-4292 <(970)%20420-4292>
>
> Skype: Phil.Robb
>



-- 
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [sdc][vfc] SDC questions from VF-C

Hi David,

Thanks for updating the table to include SDNC controller.

Regarding the WAN service, as I pointed to you before, in the TOSCA example 
from Open-O sent by Huabin a while ago, there is a folder in that zip file 
called underlayL3VPN_2017_03_24/Definitions/. You can see a couple yaml files 
there for type definition.  Please let us know if that’s good enough for you to 
design WAN service in SDC.

We will have a meeting tomorrow (8/11) 10am EST, I’ll forward you the invite 
and hope you can help us solving the blocking issue.

Thanks,
-Yang

From: SHADMI, DAVID [mailto:ds2...@att.com]
Sent: Thursday, August 10, 2017 8:42 AM
To: Yang Xu (Yang, Fixed Network); zhang.maope...@zte.com.cn; LANDO, MICHAEL
Cc: onap-discuss@lists.onap.org; ROZIN, EDEN
Subject: RE: [onap-discuss] [sdc][vfc] SDC questions from VF-C

Hi Yang,

I still haven’t seen the WAN service information and therefore can’t provide 
any comments about it.

Here is the updated table based. See enclosed email for additional information.

Service

Type

Category

Controller

Comment

VoLTE

Service

Service

No controller

vIMS

Service

NS

VFC

New imperative BPMN flow which uses VFC

vEPC

Service

NS

VFC

New imperative BPMN flow which uses VFC

vFW/vLB, vCPE, WAN

Service

Service

SDNC/HEAT

Retain the existing OpenECOMP BPMN flow



Thanks,
David


From: Yang Xu (Yang, Fixed Network) [mailto:yang@huawei.com]
Sent: Wednesday, August 09, 2017 11:44 PM
To: SHADMI, DAVID ; zhang.maope...@zte.com.cn; LANDO, MICHAEL 

Cc: onap-discuss@lists.onap.org; ROZIN, EDEN 
Subject: RE: [onap-discuss] [sdc][vfc] SDC questions from VF-C

Hi David,

I missed Wednesday’s meeting due to some other conflict. Has WAN service been 
defined in SDC? I don’t see SDNC (the controller for WAN service) listed in the 
table:

Service

Type

Category

Orchestrator/Controller

VoLTE

Service

E2E Service

SO VFC

vIMS

Service

NS

VFC

vEPC

Service

NS

VFC

vFW/vLB demo

Service

Service

Heat

vCPE or other service designed by SDC using declarative flow.

Service

All other Service

Business as usual from SO perspective: SO is doing service and resource 
orchestration interfacing with SDNC/APPC/PO as needed  APPC


Could you finalize the WAN service details in SDC (i.e. how PNFs and WAN 
service defined in SDC)? Other modules are blocked by it.

Thanks,
-Yang

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SHADMI, DAVID
Sent: Thursday, August 10, 2017 12:04 AM
To: zhang.maope...@zte.com.cn; LANDO, MICHAEL
Cc: onap-discuss@lists.onap.org; ROZIN, EDEN
Subject: Re: [onap-discuss] [sdc][vfc] SDC questions from VF-C

Hello,

#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.
#5 – Please see enclosed email.


Thanks,
David


From: zhang.maope...@zte.com.cn 
[mailto:zhang.maope...@zte.com.cn]
Sent: Wednesday, August 09, 2017 9:15 PM
To: LANDO, MICHAEL >; SHADMI, 
DAVID >
Cc: yangya...@chinamobile.com; 
denglin...@chinamobile.com; 
meng.zhaoxi...@zte.com.cn; 
onap-discuss@lists.onap.org; ROZIN, EDEN 
>
Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C


hi micheal & david



 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng
原始邮件
发件人： >;
收件人：张茂鹏10030173;
抄送人： >; 
>; 
>;孟照星10024238;

[onap-discuss] 答复: Re: [integration]Jenkins Build Failure

2017-08-10 Thread fu.guangrong

Hi Gary,






Thank you for your feedback. I have removed those jobs from the yaml file. 
Let's see whether this will be solved.






Thanks again and have a nice day.






Regards,


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

[onap-discuss] [integration][holmes] How to Get Dependencies like MySQL during the Building of the Dockers?

2017-08-10 Thread fu.guangrong

Hi all,




While making dockers, we want to integrate MySQL as a part of our components. 
Do we have to pull it directly from the internet or is it stored in some place 
of ONAP so that we could fetch it from within?




Thanks.




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

[onap-discuss] TSC topic - branching/tagging for stable development/integration

2017-08-10 Thread Michael O'Brien

TSC,
   In your meeting today could you discuss (I would normally attend 
- but have a parallel meet)

1)  how to ensure the stability of the 1.1/master branch as we add new R1 
content - need E2E integration daily tests - we then deploy to 
Rackspace/Openstack only TAGGED-OK builds

2)  Allow developers to create feature branches on the fly

   Issue: 1.1/master is sensitive to the following

-Cross repo breaking changes - like REST schema changes (these won't be 
picked up in

-No ability to create shared developer branches

-Tagging known/verified working builds - across all repos (this would 
require a functional test like https://jira.onap.org/browse/AAI-58 for each 
team - and an integration test
The integration test will require bringing up ONAP's docker containers/volumes 
(likely not on Openstack, but some sort of K8S, docker-compose/vagrant setup) - 
in a Jenkins job
Work with Integration team on this - I am going to look into an integration 
test.

Upcoming Scenario: (Tian Lee raised this in the AA meet today) Amsterdam 
release cut - while Bejing.
In the past and during that last open source project I worked at for Oracle 
(EclipseLink RI for JPA 2.0) we created release branches prior to release when 
we verified the build was very stable (no commits for 48h) - once we branched 
then we patched the release branch with cherry-picks from master as required.


Thank you
/michael



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] {URGENT} RE: [so] Weekly Meeting

2017-08-10 Thread Seshu m

Thanks for the resolution provided.
Could you also provide the access rights to record the meetings.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Kenny Paul [kp...@linuxfoundation.org]
Sent: Wednesday, August 09, 2017 11:29 PM
To: Seshu m
Cc: Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); Andrew 
Philip; Yang, Bin; zhanganb...@chinamobile.com; Ethan Lynn; CHOMA, JOHN S; 
DeWayne Filppi; Byung-Woo Jun; wangchen...@chinamobile.com; 
zhonghe...@boco.com.cn; zhang.zh...@zte.com.cn; Chenchuanyu; 
yangyan...@chinamobile.com; DAUGHERTY, ROBERT E; Lingli Deng; 
wu.li...@zte.com.cn; yangyuan...@boco.com.cn; BULLARD, GIL; denghui (L); 
Christopher Donley (Chris); alex@intel.com; Vijaykumar S; 
onap-discuss@lists.onap.org; Praveen Krishnamurthy P
Subject: Re: {URGENT} RE: [so] Weekly Meeting

Hi Seshu,

Again my apologies for the inconvenience. The LF has added an additional Zoom 
host account to accommodate moving your meeting from Mondays to Wednesdays and 
I have made the necessary changes.  Please verify that the information in G-cal 
and on your meeting's wiki page are both correct.  As mentioned in my other 
email, please let me know the ticket number that was issued for your change 
request so that I can do some RCA. I do not want something similar happening to 
someone else.

Thanks.

Best Regards,
-kenny

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

On Aug 9, 2017, at 6:37 AM, Seshu m 
> wrote:

Hi Kenny

As is discussed over the call, we are getting an issue in initiating the call,
We are getting the error
"The HOST has another meeting in progress"


I had been sending remainders and requests to re-schedule the bridge to 
wednesday, but that dint happen.
Kindly help us resolve this issue at the earliest possible time.
We are waiting

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Seshu m [seshu.kuma...@huawei.com]
Sent: Wednesday, August 09, 2017 7:35 PM
To: Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); Andrew 
Philip; Yang, Bin; 
zhanganb...@chinamobile.com; Ethan Lynn; 
CHOMA, JOHN S; DeWayne Filppi; Byung-Woo Jun; 
wangchen...@chinamobile.com; 
zhonghe...@boco.com.cn; 
zhang.zh...@zte.com.cn; Chenchuanyu; 
yangyan...@chinamobile.com; DAUGHERTY, 
ROBERT E; Lingli Deng; wu.li...@zte.com.cn; 
yangyuan...@boco.com.cn; BULLARD, GIL; denghui 
(L); Christopher Donley (Chris); alex@intel.com; 
Vijaykumar S; onap-discuss@lists.onap.org; 
Praveen Krishnamurthy P
Subject: [onap-discuss] [so] Weekly Meeting
When: Wednesday, August 09, 2017 9:30 PM-10:30 PM.
Where: Zoom

When: Wednesday, August 09, 2017 7:00 PM-8:00 PM (UTC+05:30) Chennai, Kolkata, 
Mumbai, New Delhi.
Where: Zoom

Note: The GMT offset above does not reflect daylight saving time adjustments.

*~*~*~*~*~*~*~*~*~*

[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# Or 
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 309 416 964

[onap-discuss] 邀请：ONAP Holmes Weekly Meeting @ 2017-08-10 (周四) 20:00 - 21:00 (CST) (onap-discuss@lists.onap.org)

2017-08-10 Thread Guangrong Fu

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:20170810T20
DTEND;TZID=Asia/Shanghai:20170810T21
DTSTAMP:20170810T004616Z
ORGANIZER;CN=Guangrong Fu:mailto:steven20...@gmail.com
UID:4b62j73lq9s0d9m0skkum0a...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jh2...@att.com;X-NUM-GUESTS=0:mailto:jh2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhao.huab...@zte.com.cn;X-NUM-GUESTS=0:mailto:zhao.huab...@zte.com.
 cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=l...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=joh...@att.com;X-NUM-GUESTS=0:mailto:joh...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Guangrong Fu;X-NUM-GUESTS=0:mailto:steven20...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fu.guangr...@zte.com.cn;X-NUM-GUESTS=0:mailto:fu.guangr...@zte.com.
 cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=yang@huawei.com;X-NUM-GUESTS=0:mailto:yang@huawei.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ramesh.a.nagara...@accenture.com;X-NUM-GUESTS=0:mailto:ramesh.a.nag
 ara...@accenture.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=du.jiaqi...@zte.com.cn;X-NUM-GUESTS=0:mailto:du.jiaqi...@zte.com.cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=david.sauvag...@bell.ca;X-NUM-GUESTS=0:mailto:david.sauvageau@bell.
 ca
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=liuyuan...@chinamobile.com;X-NUM-GUESTS=0:mailto:liuyuanyjy@chinamo
 bile.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
RECURRENCE-ID;TZID=Asia/Shanghai:20170810T20
CREATED:20170720T102725Z
DESCRIPTION:Hi there\, \n\nZTE Open Source is inviting you to a scheduled Z
 oom meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.
 us/j/66\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,66
 # or +16465588656\,\,66#\n\nOr Telephone:\nDial: +1 408 638 096
 8 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 699 996 \n   
  International numbers available: https://zoom.us/zoomconference?m=_5QAuX9O
 -wb43xJqoNQjTlyYurEIrnWK\n\n\n\n在 https://www.google.com/calendar/event?act
 ion=VIEW=NGI2Mmo3M2xxOXMwZDltMHNra3VtMGE3ZmNfMjAxNzA4MTBUMTIwMDAwWiBvbm
 FwLWRpc2N1c3NAbGlzdHMub25hcC5vcmc=MjEjc3RldmVuMjAwMjdAZ21haWwuY29tMTk5N
 jJmMmU0Y2VmODAyMWUyNGE3M2I3ZDk3NmIxMTQ5ZjBlZGMzOQ=Asia/Shanghai=zh_C
 N 查看您的活动。
LAST-MODIFIED:20170810T004614Z
LOCATION:https://zoom.us/j/66
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:ONAP Holmes 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

[onap-discuss] 答复：答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

hi,



The vnfminfo is a string, such as gvnfm,juju,zte,HUAWEI,etc.

hope the description can clear the vnfminfo parameter.



thanks.






 

 原始邮件 
 
 
 
 
 
 
 
 
 
 发件人: 
 张茂鹏10030173 
 
 
 
 收件人:ds2...@att.com 
 
 
 
 抄送:er4...@intl.att.com onap-discuss@lists.onap.org 
 
 
 
 日期: 
 2017-08-10 21:29:59 
 
 
 
 主题:[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 
 
 
 
 
 hi, 
 
vnfminfo is used by vf-c to identify which vendor vnfm driver to choose. 
 
thanks 
maopeng 
 
 

 
 
 
 
 
 
 
 
 发件人: 
 SHADMI,DAVID 
 
 
 
 收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN 
 
 
 
 抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org 
 
 
 
 日期: 
 2017-08-10 20:57:55 
 
 
 
 主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
Hi, 
 

 
 
 
 
   
 

 
 
My comments are embedded. 
 

 
 
 
 
   
 

 
 
@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser? 
 

 
 
 
 
   
 

 
 
Thanks, 
 

 
 
David 
 

 
 
 
 
   
 

 
 
 
 
   
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 

 
 
 
 
   
 

 
 
 hi david 
 

 
 
 
   
 

 
 thanks, david. a few questions below. 
 

 
 
 
   
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types. 
 

 
 
[Maopeng]does the SDC plan to add open-o TOSCA Type in R1? [David] Yes. 
That is the plan. The types’ namespace would follow OpenECOMP convention. 
 

 
 
#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add. 
 

 
 
 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.   
 

 
 
#5 – Please see enclosed email. 
 

 
 
 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks. [David] What information the vnfminfo has? 
 

 
 
 
   
 

 
 
 
   
 

 
These questions still need your advices. 
 

 
 
   1\ Whether to support ELAN VL, which can be shared among VNFs. 
 

 
 
  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL. 
 

 
 
  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks. 
 

 
 
[Michael: David can you respond?] 
 

 
2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks 
 

 
 
   3\ About the parser, VFC written in python can not use the java lib  
directly. 
 

 
 
  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1 
 

 
 
  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1? 
 

 
 
 
 
   
 

 
 Best Regards 
 

 
 Maopeng 
 

 
 
 
 
 原始邮件 
 

 
 
 
 
 
 
 
发件人：  
 

 
 
 
 
 
收件人：张茂鹏10030173  
 

 
 
 
 
 
抄送人：  孟照星10024238 
  
 

 
 
 
 
 
日 期 ：2017年08月10日 12:07 
 

 
 
 
 
 
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C 
 

 
 
 
 
 
 
 
 
   
 

 
 
 
 
Hello, 
 

 
 
  
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types. 
 

 
 
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add. 
 

 
 
#5 – Please see enclosed email. 
 

 
 
  
 

 
 
  
 

 
 
Thanks, 
 

 
 
David 
 

 
 
  
 

 
 
  
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN

[onap-discuss] 答复：RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C

2017-08-10 Thread Subramanya, Nagesha (Nokia - IN/Bangalore)

hi,



vnfminfo is used by vf-c to identify which vendor vnfm driver to choose.



thanks

maopeng






 

 原始邮件
 
 

 

 

 

 
 发件人:
 SHADMI,DAVID 
 

 
 收件人:张茂鹏10030173 LANDO, MICHAEL ROZIN, EDEN 
 

 
 抄送:yangya...@chinamobile.com denglin...@chinamobile.com 孟照星10024238 
onap-discuss@lists.onap.org 
 

 
 日期:
 2017-08-10 20:57:55
 

 
 主题:RE: RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 

 
 
 
 
 
 


 
 
 
Hi,
 

 
 

 
  
 

 
 
My comments are embedded.
 

 
 

 
  
 

 
 
@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser?
 

 
 

 
  
 

 
 
Thanks,
 

 
 
David
 

 
 

 
  
 

 
 

 
  
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Thursday, August 10, 2017 2:57 AM
 To: SHADMI, DAVID 
 Cc: LANDO, MICHAEL  yangya...@chinamobile.com 
denglin...@chinamobile.com meng.zhaoxi...@zte.com.cn 
onap-discuss@lists.onap.org ROZIN, EDEN 
 Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 

 
  
 

 
 
 hi david
 

 
 
 
  
 

 
 thanks, david. a few questions below.
 

 
 
 
  
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types.
 

 
 
[Maopeng]does the SDC plan to add open-o TOSCA Type in R1? [David] Yes. 
That is the plan. The types’ namespace would follow OpenECOMP convention.
 

 
 
#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add.
 

 
 
 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.  
 

 
 
#5 – Please see enclosed email.
 

 
 
 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks. [David] What information the vnfminfo has?
 

 
 
 
  
 

 
 
 
  
 

 
These questions still need your advices.
 

 
 
   1\ Whether to support ELAN VL, which can be shared among VNFs.
 

 
 
  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL.
 

 
 
  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.
 

 
 
[Michael: David can you respond?]
 

 
2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks
 

 
 
   3\ About the parser, VFC written in python can not use the java lib  
directly.
 

 
 
  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1
 

 
 
  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
  If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?
 

 
 

 
  
 

 
 Best Regards
 

 
 Maopeng
 

 
 
 
 
 原始邮件
 

 
 
 
 
 
 
 
发件人： 
 

 
 
 
 
 
收件人：张茂鹏10030173 
 

 
 
 
 
 
抄送人：  孟照星10024238 
 
 

 
 
 
 
 
日 期 ：2017年08月10日 12:07
 

 
 
 
 
 
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 
 
 
 
 

 
  
 

 
 
 
 
Hello,
 

 
 
 
 

 
 
#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.
 

 
 
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.
 

 
 
#5 – Please see enclosed email.
 

 
 
 
 

 
 
 
 

 
 
Thanks,
 

 
 
David
 

 
 
 
 

 
 
 
 

 
 
From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Wednesday, August 09, 2017 9:15 PM
 To: LANDO, MICHAEL  SHADMI, DAVID 
 Cc: yangya...@chinamobile.com denglin...@chinamobile.com 
meng.zhaoxi...@zte.com.cn onap-discuss@lists.onap.org ROZIN, EDEN 

 Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C
 

 
 
 
 

 
 
 hi micheal & david
 

 
  
 

 
  Thanks micheal
 

 
   Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.
 

 
  The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks
 

 
   About the parser, VFC written in python can not use the java

Re: [onap-discuss] M2 Functionality Frezee feedback request

2017-08-10 Thread SPATSCHECK, OLIVER (OLIVER)


Can we discuss below? I agree with Catherine if we want to have the code stubs 
in place by M2 we will have a DETAILED functional design freeze milestone 
before M2. Having both on the same day makes little sense to me too. To late to 
worry about this for r1 (will just push trough and adjust as needed) but we 
should fix this on the timeline for R2.

Oliver

> On Aug 9, 2017, at 7:07 AM  EDT, LEFEVRE, CATHERINE  
> wrote:
> 
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Good morning Gildas,
>  
> Thank you for building this new proposal.
>  
> Please find my feedback.
>  
> Slide 4
>  
> •The goal of the Functionality Freeze is to de-risk the release by 
> providing a stable target for integration with other components. It marks the 
> end of the API definition coding and feature addition activities. At 
> Functionality Freeze, API stubs must be coded.
> [CLEF]:
> I do not think it is possible because there is no previous design freeze 
> milestone prior M2
> At functionality freeze, the design and the documentation should be available 
> but not yet the source code.
> The implementation of the API is one of the targets of M3.
>  
> •After Functionality Freeze, no new visible features/APIs are to be 
> added to the current ONAP release codebase.
> [CLEF]: Please consider my previous feedback. It is not practical to freeze 
> the ONAP source code at M2 milestone if there is no previous design freeze.
>  
> •At Functionality Freeze, the following activities have been achieved:
> -All committed functionalities have been coded and committed to the 
> onap repos.
> [CLEF]: See previous statement, what do you consider as left for M3 & M4 if 
> all the code is already implemented
>  
> -All source code has automated unit test (Project Team).
> [CLEF]: All the already available source code should have an automatic unit 
> test but the code not yet available will also require additional unit tests 
> -The team is meeting regularly and has completed at least one sprint.
> [CLEF]: Is there a reason to add this new statement? Or do you consider 
> Sprint0 – typically use to set the preparation work to be performed by the 
> Scrum Team.
> -Seed code has been delivered to LF, scanned, and deposited into ONAP 
> repos
> [CLEF]: Can we suggest to LF team that they provide the scan results no later 
> than M2-2 weeks so the project team has enough time to fix any identified 
> issue?
> It also requires that the seed code is available to LF, M2-3 weeks? Is it 
> achievable?
>  
>Please also add to the slide 3 - the API Stubs as part of 
> activities to be achieved by M2
>  
> Many thanks & regards
> Catherine
>  
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
> Sent: Thursday, August 03, 2017 10:08 PM
> To: onap-discuss@lists.onap.org
> Subject: [onap-discuss] M2 Functionality Frezee feedback request
>  
> Dear ONAP Community Members,
>  
> This email is to follow up on an action item that came up during M2 
> Functionality freeze earlier today at TSC weekly meeting.
>  
> The requirement was to clarify and propose changes on some elements of M2 
> definition and more particularly on the expectation from a code perspective 
> at M2 Functionality Freeze.
>  
> The attached proposal presents the current definition and highlights the 
> proposed changes to meet the above expectations.
>  
> Let me know your thoughts and we will take it from there to refine the 
> definition.
>  
>  
> Thanks,
> Gildas
>  
> 
> Gildas Lanilis
> ONAP Release Manager
> Santa Clara CA, USA
> gildas.lani...@huawei.com
> Mobile: 1 415 238 6287
>  
> ___
> 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=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=9iyuArzgyekj47PZSPfIijI2cSHsUJtAlcTA0X_udNI=Q54z_bfnqw83IU94T3wnWcr1dtmSGp_7w0GDltgsj30=Q2GMr8jBJ6D8hDGl3wWNGszLNvvOW-t8Ky_VB6giV1U=
>  

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

Re: [onap-discuss] [sdc][vfc] SDC questions from VF-C

2017-08-10 Thread SHADMI, DAVID

Hi,

My comments are embedded.

@Michal, @Eden – could you please help with the three questions about ELAN VL, 
service and VNF package, and the Parser?

Thanks,
David


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Sent: Thursday, August 10, 2017 2:57 AM
To: SHADMI, DAVID 
Cc: LANDO, MICHAEL ; yangya...@chinamobile.com; 
denglin...@chinamobile.com; meng.zhaoxi...@zte.com.cn; 
onap-discuss@lists.onap.org; ROZIN, EDEN 
Subject: 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C


hi david



thanks, david. a few questions below.



#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF 
packages in R1. Also, SDC is planning to add Open-O TOSCA types.

[Maopeng]does the SDC plan to add open-o TOSCA Type in R1? [David] Yes. 
That is the plan. The types’ namespace would follow OpenECOMP convention.

#3 – @Michael – Could you please make sure we the node type definition 
file(s) for VF and Service exist in the wiki. @Maopeng  - could you please 
elaborate more on the node type you would like to add.

 [Maopeng] If SDC can import openo tosca type in R1, I have no more node 
type to add.  But in the design time, we can desgin different VNF base on the 
VF node type and VNF package.

#5 – Please see enclosed email.

 [Maopeng]  Thanks. For the NS , the new parameter serviceType and 
serviceRole I think is ok.  For the VF, we need the vnfminfo. what's about your 
advice? Thanks. [David] What information the vnfminfo has?





   These questions still need your advices.

   1\ Whether to support ELAN VL, which can be shared among VNFs.

  [Maopeng ] now the SDC supports VL, but it is automatically produced. 
 Now I can design the Eline type VL, but for the VoLTE case , we need
multiple VNFs share one VL.

  what's the automatic rule of VL creating? How to 
design it? could you show with us. thanks.

[Michael: David can you respond?]

   2\The service package and vnf package CSAR in the SDC catalog, please share 
them. Thanks

   3\ About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng
原始邮件
发件人： >;
收件人：张茂鹏10030173; >;
抄送人： >; 
>;孟照星10024238; 
>; 
>;
日 期 ：2017年08月10日 12:07
主 题 ：RE: RE: RE: [sdc][vfc] SDC questions from VF-C


Hello,

#2 - SDC is planning to allow onboarding VNFSDK0-validated TOSCA VNF packages 
in R1. Also, SDC is planning to add Open-O TOSCA types.
#3 – @Michael – Could you please make sure we the node type definition file(s) 
for VF and Service exist in the wiki. @Maopeng  - could you please elaborate 
more on the node type you would like to add.
#5 – Please see enclosed email.


Thanks,
David


From: zhang.maope...@zte.com.cn 
[mailto:zhang.maope...@zte.com.cn]
Sent: Wednesday, August 09, 2017 9:15 PM
To: LANDO, MICHAEL >; SHADMI, 
DAVID >
Cc: yangya...@chinamobile.com; 
denglin...@chinamobile.com; 
meng.zhaoxi...@zte.com.cn; 
onap-discuss@lists.onap.org; ROZIN, EDEN 
>
Subject: 答复: RE: RE: [sdc][vfc] SDC questions from VF-C


hi micheal & david



 Thanks micheal

  Now many advices need David to answer. If the email can reply, it 
will be OK.  Possible, meeting & email may be more effective way.

 The service package and vnf package CSAR in the SDC catalog, please 
share them. Thanks

  About the parser, VFC written in python can not use the java lib  
directly.

  Oneway:  If in the SDC can provide the REST API & 
JSON output, it will be welcome for R1

  The other way: the CSAR output of SDC follow the  
OASIS tosca simple profile, it can be parsed by other parsers.
 If the output is not standard, we 
need to know which part is not standard, and can it be fixed in the R1?



Best Regards

Maopeng
原始邮件
发件人：

Re: [onap-discuss] [onap-tsc] Register Now - ONAP Face To Face Developer Event in Paris-Saclay France

Below mail requires correction in terms of dates …

Monday, Sept. 25th, 13:00 - 17:00:  Early Bird Sessions (Optional) for those 
able to arrive on Monday
Tuesday, Sept. 26th, 09:00 - 17:00: Main Developer Forum
Wednesday, Sept. 27th, 09:00 - 17:00: Main Developer Forum
Thursday, Sept 28th, 09:00 - 15:00: Follow-on Unconference Sessions


Regards,
Nagesha

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Wednesday, August 09, 2017 2:39 AM
To: onap-discuss@lists.onap.org
Cc: Lara Taback ; onap-tsc 

Subject: [onap-tsc] Register Now - ONAP Face To Face Developer Event in 
Paris-Saclay France

Hello ONAP Community Members:

We have confirmed the following high level agenda for the next ONAP Developer 
Face to Face meeting to be held at the Nokia facility in Paris-Saclay, France.

Monday, Sept. 25th, 13:00 - 17:00:  Early Bird Sessions (Optional) for those 
able to arrive on Monday
Tuesday, Sept. 25th, 09:00 - 17:00: Main Developer Forum
Wednesday, Sept. 26th, 09:00 - 17:00: Main Developer Forum
Thursday, Sept 27th, 09:00 - 15:00: Follow-on Unconference Sessions

A detailed agenda will be provided as the event nears.  We are soliciting 
topics for the event on the following wiki page:  
https://wiki.onap.org/display/DW/September+26-28+Topics

Please review this page, and put your name down for sessions you would like to 
participate in, and also add any session(s) you would like to lead or see 
discussed.

Please register for the event at your earliest convenience here:  
https://www.regonline.com/ONAPDeveloperParis

Details on the venue, local hotels and how to receive Visa Invitation letters 
will be mailed to you along with your Registration Confirmation.  For your 
convenience, that information is also provided below


Venue
Nokia Paris-Saclay
Route de Villejust
91620 Nozay
France
Phone: +33 01 60 40 60 40

Nearby Hotels
Below is a list of hotels within 7km of the Nokia facility
Best Western Hotel L'Oree, Saulx Les Chartreux
Route de Montlhery
91160 Saulx Les Chartreux , France

Hotel Mercure Paris Sud Les Ulis Courtaboeuf
3 Rue Rio Solado
91952 Les Ulis, France
+33 1 69 07 63 96

Meals
Nokia and ONAP will be hosting beverages and breaks throughout the conference. 
Please be sure to have breakfast prior to arriving each morning. The group will 
be eating in the cafeteria on campus each day, at your own expense.

Cancellation/No-Show Fee
There is no cost to participate in the ONAP Developer Event. You will only be 
charged a cancellation/no-show fee of $50.00 USD if you do not cancel by 08:00 
PST on Tuesday, September 19 or do not attend the event.

Visa Information
Please visit http://events.linuxfoundation.org/visa-request to request a visa 
letter.

Thanks in advance for participating in this event.  It will be our last 
opportunity for face to face work during our 1st release cycle.

If you have any questions or concerns regarding this event, please contact the 
ONAP Events team at eve...@onap.org

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: RE: RE: RE: [sdc][vfc] SDC questions from VF-C