Re: [onap-discuss] Info needed about application inside dockers on MSO and SDNC inside ONAP system

[Gaurav Gupta (c)]

Thanks Michael for the Info .


I had looked at the link for docker-containers .But what you shared below w.r.t 
to

--"Not everything is containerised " . and Microservices input makes certain 
things very clear  .


Do you any time plan to propose on a unified packaging strategy for each VM and 
everything as in docker container .


Second Item could be to improve upon --

a- What is the most common item in each ONAP VM .

b - What is the common item in few of the ONAP VM where in few could be 2 and 
higher but not all ONAP VM's.




with best regards

gaurav



From: Michael O'Brien 
Sent: 04 July 2017 19:44:54
To: Gaurav Gupta (c); Lefevre, Catherine; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Info needed about application inside dockers on MSO 
and SDNC inside ONAP system

Gaurav,
   Hi, good question, we had the same questions about the OOTB docker 
architecture – it looks like there is a mix of docker-compose (VID, SDC, MSO 
and APPC for example) and raw docker run orchestration.  A evolving low level 
view of the 1.0 system (1 instead of 2 AAI VMs) is in a diagram below.

https://wiki.onap.org/display/DW/Overall+Deployment+Architecture#OverallDeploymentArchitecture-Version1.0.0

   Essentially any microservice (docker container) that does not need to expose 
a port – should be able to communicate on its vm via it’s docker private 
network – usually this is setup in compose.  For others that expose the DB 
directly like MSO, SDNC or APPC the mariaDB 3306 is mapped as well to 32768 
outside.
   Also note that not everything is containerized yet – some jars run directly 
on their VM – this is specific to 4 of the 5 zld* VMs of DCAE.

   /michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
Sent: Monday, July 3, 2017 09:58
To: Lefevre, Catherine ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Info needed about application inside dockers on MSO 
and SDNC inside ONAP system


Good Morning Catherine



Actually I had looked at the below Link already .



but was looking more to know the actual applications to Docker mapping for 
understanding various docker interaction inside each VM such as MSO and SDNC .



thanks and regards

gaurav


From: Lefevre, Catherine >
Sent: 25 June 2017 01:51
To: Gaurav Gupta (c); 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Info needed about application inside dockers on MSO 
and SDNC inside ONAP system


Good evening Gaurav,



You can find the ONAP Docker strategy on the ONAP wiki – look at the “VMs and 
Containers” section

https://wiki.onap.org/display/DW/Release+Notes+1.0.0+draft



Best regards

Catherine



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
Sent: Friday, June 23, 2017 8:00 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Info needed about application inside dockers on MSO and 
SDNC inside ONAP system



Hello There



We  have started looking at MSO Code and there does exists an relationship 
between docker-compose.yml and pom.xml present inside multiple directories 
inside MSO projects   .



To Further look at Code Flow  - In case some has deployed ONAP System can the 
following information be provided .



a- how many Application are running inside each docker containers  . ( When I 
say Application I mean distinct PID as indicated  in ps -eaf )

b - How does the Application running inside 2 differnt docker containers inside 
the same VM  interacts with each other .



For Example MSO has 2 docker containers and SDNC 4 Dockers .

- ps -eaf  ( output from each docker containers )

- netstat -tunlp ( output from each docker containers )



pls note that above two information needs to be collected from each of the 
dockers inside MSO , SDNC





with best regards

Gaurav

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

[onap-discuss] [integration] RE: MSB daily building

[Gary Wu]

Hi Huabing,

Yes, this will have to be handled by LF admins.  I would expect that the same 
third party lib jobs should be migrated to ONAP, and the corresponding entries 
added to the Maven settings.xml.  Another possibility is to keep the 
dependencies on *.open-o.org, but that’s up the LF to decide since Open-O 
services were supposed to be decommissioned.

Thanks,
Gary


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Monday, July 10, 2017 6:47 PM
To: Gary Wu 
Cc: Gildas Lanilis ; meng.zhaoxi...@zte.com.cn; 
jian.m...@zte.com.cn
Subject: MSB daily building


Hi Gary,



I'm writing to ask your help,  again. :-).



MSB codes have already been uploaded to ONAP Gerrit. Since the compiling of MSB 
depends on some third party libs hosted on OPEN-O Nexus server, How could I add 
OPEN-O maven repo to maven settings.xml for  ONAP jenkins so MSB daily building 
could run at ONAP Jenkins server?



The below configuration should be added to maven setting:





  open-o-thirdparty

  open-o-thirdparty

  
https://nexus.open-o.org/content/repositories/thirdparty/https://nexus.open-o.org/content/repositories/thirdparty/%3c/url>>

  

true

  

  

false

  





  open-o-thirdparty-snapshots

  open-o-thirdparty-snapshots

  
https://nexus.open-o.org/content/repositories/thirdparty-snapshots/https://nexus.open-o.org/content/repositories/thirdparty-snapshots/%3c/url>>

  

false

  

  

true

  





I have sent out a mail to ask help from LF to migrate those third party libs 
Jenkins job from OPEN-O to ONAP, there's no response yet.



Thanks,

Huabing








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

[onap-discuss] [esr] [aai] Hope to add an agenda for ESR at TSC meeting for this week

[li.zi30]

Hi all,






Since A team and ESR team have made a consensus about the merge approach. I 
would like to suggest to cancel the ESR discussion meeting for this week 
(planned at last TSC meeting) and add an agenda for ESR review at the TSC 
meeting (13th July ). How do you think about this ? 


If you have any question about ESR please let me know.




Thanks,

Li Zi












原始邮件



发件人：李滋00164331
收件人：    

抄送人：  
日 期 ：2017年07月10日 18:05
主 题 ：Re: [onap-discuss] ESR






Hi, All,




To make a clearer description about merge plan with A:




Original ESR scope (proposed at 5/14/17)Merge Plan with A (decided at 
7/10/2017)Provide the API to register/query/update/delete external system, A 
is the data storage back-endcontribute these function to A the Portal 
for user to  register/query/update/delete external systema function of ESR 
which would be a sub-project of A whether the external systems are 
reachable, and store the health status to A function of ESR which would be 
a sub-project of A



And also the baseline approach of each project to got the external system 
addresses in different scenario shows as the table bellow:


Scenario


External system to be provisioned


Baseline approach

Reflections Have Interface Interact With ESRConnection to cloud infra

Address and capabilities of VIM managers


(e.g. openstack port)

Mult-VIM: will register/unregister VIM with ESR/A, the register VIM from ESR 
portal and need the health check function of VIM.
YesVID: manually input the VIM addresses and connection information to the 
portal, and sent this info to MSO which later call controllers which interact 
with all of these systems (VNFMS , VIM , EMS)
NoVF-C: get the VIM addresses from ESR/A
YesSO: will not interact with external system directly
NoConnection to transport

SDN controller address’s and capabilities

vendor sdn controler which managed by VIM is not in the scope of ESR. How about 
the vendor sdn controller managed by ONAP SDN-C?


There is a request about API used to verify that platform is available from 
SDN-C release plan.


ONAP SDN-C: ?


no responseConnecting to S-VNFM

S-VNFM and capabilites

VF-C: manage VNFM addresses from ESR/A be part of the tosca/heat   
templateYesEMS


(Element Management System)

EMS address and capabilitiesAPP-C: will not interact with external system 
directly. Interfaces with other ONAP Components: AAI, Policy, MSO, DCAE etc.
NoVF-C: manage EMS addresses from ESR/A
YesOther
DCAE: DCAE will not collect the data from external system?




Hope it helps for your judgement.





Thanks,

Li Zi















发件人：李滋00164331
收件人： 
抄送人：   

日 期 ：2017年07月10日 15:54
主 题 ：RE: RE: [onap-discuss]  ESR






Hi, Dear TSC members,




As we discussed with the PTL of related project, ESR is necessary for Amsterdam 
release. Also our team has got a consensus that ESR team is committed to 
working the necessary A features and interface agreements to support making 
A the datastore for ESR data.  The portal and update  functions can be a 
separate microservice and would use A as the database. And Jimmy (A PTL) 
agreed that the Portal/healthcheck function of ESR to be the subproject of A




So, Could I suggest that the TSC cast a vote for ESR?




For ESR proposal https://wiki.onap.org/pages/viewpage.action?pageId=5734948 

For ESR discussion result 
https://wiki.onap.org/display/DW/ESR+Discussion+And+Comments+Collection 




Thanks,

Li Zi





















发件人： 
收件人：李滋00164331   

日 期 ：2017年07月07日 21:38
主 题 ：RE: [onap-discuss]  ESR







Hi, Everyone,


 


After further discussion with Li Zi, I believe that from the perspective of 
development resources, A might be the best choice as the parent project for 
ESR  even if typically A does not do the kind of UI and healthcheck function 
that ESR provides.  Li Zi’s team is committed to working the necessary A 
features and interface agreements to support making A the datastore for ESR 
data.  The portal and update  functions can be a separate microservice and 
would use A as the database.


 


Therefore, if the TSC agrees that the ESR data is necessary and useful in the 
Amsterdam release, ESR can stay with A for this release.  If there is 
consensus  that the portal healthcheck/creation/management GUI belongs outside 
A perhaps that microservice could be moved at some point, but given that Li 
Zi’s team is committed to manage that piece I believe A can accommodate this 
sub project for Amsterdam.


 


Thanks,


Jimmy Forsyth


 


 


 


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn
 Sent: Friday, July 07, 

[onap-discuss] Invitation: [oom] cloudify for oom @ Tue Jul 11, 2017 6am - 7am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20170711T13Z
DTEND:20170711T14Z
DTSTAMP:20170710T222844Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:r5jhpmquj54pu41hklkk8tb...@google.com
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=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20170710T222843Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 3 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/366326440\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,366326440# o
 r +16465588656\,\,366326440#\n\nOr Telephone:\nDial: +1 408 638 0968 (U
 S Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 366 326 440\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=ZVqU98Pklm26vryO
 hYGZtvAirGwfo1Ty\n\n\nView your event at https://www.google.com/calendar/ev
 ent?action=VIEW=cjVqaHBtcXVqNTRwdTQxaGtsa2s4dGJtbTAgb25hcC1kaXNjdXNzQGx
 pc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Z
 m1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tM2QwNTZjOGMyYmUyNjQxMWZhY2Rj
 MjUwMTkwMmYyZmI5NDBiNjJkMQ=America/Los_Angeles=en.
LAST-MODIFIED:20170710T222843Z
LOCATION:https://zoom.us/j/366326440
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[oom] cloudify for oom
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

Re: [onap-discuss] [sdc] Help for compiling SDC module

[Morales, Victor]

Howdy,

I’ve been trying to identify the root cause of the SDC compilation error and I 
noticed that it’s caused by onboarding-ui-war module.  I’m getting the 
following error when it tries to run the build maven goal[1]

[INFO]  [1025] ./src/sdc-app/heatvalidation/UploadScreen.jsx 3.7 kB {2} [built]
[INFO]  [1083] multi sdc-app/heatValidation.app.jsx 28 bytes {2} [built]
[INFO]  + 904 hidden modules
[INFO]
[INFO] ERROR in ./src/sdc-app/flows/SequenceDiagram.jsx
[INFO] Module not found: Error: Can't resolve 'dox-sequence-diagram-ui' in 
'/opt/sdc/openecomp-ui/src/sdc-app/flows'
[INFO]  @ ./src/sdc-app/flows/SequenceDiagram.jsx 37:28-62
[INFO]  @ ./src/sdc-app/flows/FlowsListEditorView.jsx
[INFO]  @ ./src/sdc-app/flows/FlowsListEditor.js
[INFO]  @ ./src/sdc-app/ModulesOptions.jsx
[INFO]  @ ./src/sdc-app/sdc.app.jsx
[INFO]  @ multi sdc-app/sdc.app.jsx
[INFO] bundleJS : Failure!!
[INFO]  -language:  en
[INFO] [21:13:19] 'prod' errored after 2.25 min
[INFO] [21:13:19] Error: Webpack build FAILED
[INFO] at prodTask.catch.err (/opt/sdc/openecomp-ui/gulpfile.js:89:9)
[INFO] at tryCatcher 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/util.js:26:23)
[INFO] at Promise._settlePromiseFromHandler 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/promise.js:510:31)
[INFO] at Promise._settlePromiseAt 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/promise.js:584:18)
[INFO] at Promise._settlePromises 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/promise.js:700:14)
[INFO] at Async._drainQueue 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/async.js:123:16)
[INFO] at Async._drainQueues 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/async.js:133:10)
[INFO] at Immediate.Async.drainQueues 
(/opt/sdc/openecomp-ui/node_modules/bluebird/js/main/async.js:15:14)
[INFO] at runCallback (timers.js:649:20)
[INFO] at tryOnImmediate (timers.js:622:5)
[INFO] at processImmediate [as _immediateCallback] (timers.js:594:5)
[INFO]

My understanding is that maven[1] calls gulp[2], gulp calls webpack in its prod 
task[3] and the prod task loads the modules using the webpack.production.js 
file[4].  I’m currently using the code as it is in the 
repo(https://git.onap.org/sdc/) but I’m not sure if I’m missing something? Any 
help will be really appreciated.

Regards/Saludos
Victor Morales
irc: electrocucaracha

[1] https://git.onap.org/sdc/tree/openecomp-ui/pom.xml#n114
[2] https://git.onap.org/sdc/tree/openecomp-ui/package.json#n9
[3] https://git.onap.org/sdc/tree/openecomp-ui/gulpfile.js#n80
[4] https://git.onap.org/sdc/tree/openecomp-ui/tools/gulp/tasks/prod.js#n89


From:  on behalf of Victor Morales 

Date: Monday, July 3, 2017 at 11:12 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [sdc] Help for compiling SDC module

Hey there,

I’m trying to compile the SDC repo[1] with the command `mvn clean install 
-DskipTests=true -Dmaven.test.skip=true -Dadditionalparam=-Xdoclint:none` but 
I’m getting the following error:

==> sdc: [ERROR] npm ERR! code ENOENT
==> sdc: [ERROR] npm ERR! errno -2
==> sdc: [ERROR] npm ERR! syscall chmod
==> sdc: [ERROR]
==> sdc: [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod 
'/opt/sdc/openecomp-ui/node_modules/coffee-script/bin/coffee'
==> sdc: [ERROR] npm ERR! enoent ENOENT: no such file or directory, chmod 
'/opt/sdc/openecomp-ui/node_modules/coffee-script/bin/coffee'
==> sdc: [ERROR] npm ERR! enoent This is most likely not a problem with npm 
itself
==> sdc: [ERROR] npm ERR! enoent and is related to npm not being able to find a 
file.
==> sdc: [ERROR] npm ERR! enoent
==> sdc: [ERROR]
==> sdc: [ERROR] npm ERR! Please include the following file with any support 
request:
==> sdc: [ERROR] npm ERR! /opt/sdc/openecomp-ui/npm-debug.log

During the compilation of onboarding-ui-war module, I tried updating the 
node.js and npm versions and adding some dependencies(like coffe, istambul and 
others) without any success.  I just wondering if there is a missing step or 
dependency for that compilation.

Thanks
Victor Morales
irc: electrocucaracha

[1] https://git.onap.org/sdc/
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [DCAE] [ MultiVIM] Discuss Designate dependency and VES integration

[Danny Lin]

Hi,

The MultiVIM project team would like to have a conference call with DCAE team 
to discuss the ONAP R1 dependencies

1: We would like to update your team on our plan for VES integration to bring 
infrastructure FCAPS information into DCAE to facilitate close loop 
remediation, and get your feedback and make sure we are aligned on the approach.
2: We also understand DCAE has a dependency on DNSaaS as part of your R1 
deliverables, and that you are currently considering Designate for it. We would 
like to understand the use case better and figure out if and how MultiVIM can 
deliver such DNSaaS for you to consume.

Kindly let us know when is a good time for our two teams to meet and discuss.

Thanks

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

Re: [onap-discuss] [Onap-usecasesub] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi, Evgeniy,

Sure, I will add this to agenda.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F9C7.2194BE50]

From: Ievgen Zhukov [mailto:evgeniy.zhu...@netcracker.com]
Sent: Monday, July 10, 2017 9:16 PM
To: Alla Goldner ; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
Subject: RE: [Onap-usecasesub] [onap-tsc] Use case subcommittee - agenda for 
the upcoming meeting this Monday

Hi, Alla

Can we put into Agenda SD-WAN and SD-LAN for Release 2?
This Use Cases will be able to demonstrate ONAP Orchestration capability for 
VNFs hosted on CPE device (SD-WAN Case) and beyond it (SD-LAN Case).

And, if meeting time will be enough, can we take MEC Use Case for consideration?
This Use Case might have significant impact for Architecture and other Use 
Cases.

Thank you,
---

Evgeniy Zhukov, Business Analysis
Netcracker Technology

+38 (044) 238-8727 | ext. 26927| office
+38 (093) 210-4266 | mobile

We are Netcracker, and we are focused forward



[https://www.netcracker.com/assets/img/netcracker-social-final.png]ƕ
From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, July 7, 2017 9:37 AM
To: onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
>
Subject: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting’s time can be 
managed accordingly.



  1.  Review of suggested Use case subcommittee flow of operation as documented 
here https://wiki.onap.org/display/DW/Usecase+subcommittee , “Use case 
subcommittee flow”
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   More?
  4.  AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F9C7.2194BE50]

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 proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
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] [Onap-usecasesub] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Ievgen Zhukov]

Hi, Alla

Can we put into Agenda SD-WAN and SD-LAN for Release 2?
This Use Cases will be able to demonstrate ONAP Orchestration capability for 
VNFs hosted on CPE device (SD-WAN Case) and beyond it (SD-LAN Case).

And, if meeting time will be enough, can we take MEC Use Case for consideration?
This Use Case might have significant impact for Architecture and other Use 
Cases.

Thank you,
---

Evgeniy Zhukov, Business Analysis
Netcracker Technology

+38 (044) 238-8727 | ext. 26927| office
+38 (093) 210-4266 | mobile

We are Netcracker, and we are focused forward



[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, July 7, 2017 9:37 AM
To: onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
>
Subject: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting’s time can be 
managed accordingly.



  1.  Review of suggested Use case subcommittee flow of operation as documented 
here https://wiki.onap.org/display/DW/Usecase+subcommittee , “Use case 
subcommittee flow”
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   More?
  4.  AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F9BE.88D26D00]

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 proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Invitation: [sdc] Weekly #2 @ Weekly from 12am to 1am on Tuesday (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20170711T00
DTEND;TZID=America/Los_Angeles:20170711T01
RRULE:FREQ=WEEKLY;BYDAY=TU
DTSTAMP:20170710T184316Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:c4bne7it2tjqhk0livqkuq5...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ml6...@intl.att.com;X-NUM-GUESTS=0:mailto:ml6...@intl.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20170710T184316Z
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/447532405\n\nOr iPhone one-tap (US Toll):  +16465588656\,\,447532405# o
 r +14086380968\,\,447532405#\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: 447 532 405\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=OkOhrZZRSzhhJd12
 Ha5jhR6gzd_9L9W7\n\n\nView your event at https://www.google.com/calendar/ev
 ent?action=VIEW=YzRibmU3aXQydGpxaGswbGl2cWt1cTU0Zmsgb25hcC1kaXNjdXNzQGx
 pc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Z
 m1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNzUxNmQ1MWZmYWMzNTMxZjM5YzFl
 ZjIzZjYyZTFjZjc4ODJjM2NiYg=America/Los_Angeles=en.
LAST-MODIFIED:20170710T184316Z
LOCATION:https://zoom.us/j/447532405
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[sdc] Weekly #2
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] [SDNC][APP-C] Importance of SDNC in vFW Demo

[Cipher Cipher]

Hey,

I am trying vFirewall demo using ONAP. Along the way I am trying to
understand the each component I encountered. I couldn't understand the
following two points.

1) *Preloading of data*: Before deploying Vf-module, we have to preload the
data to SDNC. But in one of the comments, I came to know this step to
update AAI indirectly through SDNC. If that's true, then what is the role
of SDNC here. How can I make use of SDNC in complex usecases.

2) APP-C Mounting: Why we need to ./demo.sh appc to trigger the action in
packet generator. If I am using a different VNF, how can I use ./demo.sh ?

3)In the release-1.0.0 can we have support of SFC in SDNC?


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

Re: [onap-discuss] YANG.XML format

[Lando,Michael]

+Eden,Zahi


BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com


From: CHAPNICK, AVI
Sent: Saturday, July 08, 2017 11:05 AM
To: TIMONEY, DAN ; Rozin, Eden ; Thomas 
Nadeau ; FREEMAN, BRIAN D ; NOSHPITZ, 
CLAUDE ; Lando,Michael ; Kedar Ambekar 

Cc: WRIGHT, STEVEN A ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] YANG.XML format

Hi,

Some of the questions below refers to SDNC managed devices YANG schemas , which 
ODL gets  from the devices once the device is mounted.
Are we planning to allow getting customized version of those schemas from SDC  
for allowing fixing problems on the managed devices yang?

Some of the answers referred  to the yang models which are being used to define 
SDNC NB interfaces (Service RPC+ data model + storage schema)
As Dan explained today these are required in compile time and for that there is 
no sense of getting in runtime via SDC.

In APPC we do allow getting YANG schema from SDC in runtime , we are using 
these to define the structure and  the storage schema of the specific VNF APPC 
Is managing.
Loading NB yang schema dynamically to ODL is tricky , mainly as ODL is not 
providing API for that  and forces you to upload a synthetic  OSGI bundle with 
yang schema embedded.
I have started the engagement with ODL community for adding this support while 
back , if SDNC has the same interest (which makes a lot of sense to me.) maybe 
its good time to revive this discussion.

Avi,



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TIMONEY, DAN
Sent: Saturday, July 8, 2017 4:03 AM
To: ROZIN, EDEN >; Thomas 
Nadeau >; FREEMAN, 
BRIAN D >; NOSHPITZ, CLAUDE 
>; LANDO, MICHAEL 
>; Kedar Ambekar 
>
Cc: WRIGHT, STEVEN A >; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] YANG.XML format

All,

The YANG.XML artifact type name is perhaps a bit confusing. The actual artifact 
itself is in XML format. The YANG.XML designation indicates that the structure 
of the file is defined by a Yang model. The Yang model itself isn't distributed 
by SDC.

In the case of SDNC, we need to have the Yang model available to us at compile 
time so that we can use it to generate the code to parse XML files defined by 
that model. So, right now there really wouldn't be much use at least to SDNC in 
distribution of the Yang model itself via SDC. In the longer term, though, we 
are looking into being able to handle Yang models more dynamically. So when we 
get that working, we may very well be very interested in receiving Yang models 
from SDC. But that would not be in scope for release 1.

Hope this helps,
Dan

Sent from MyOwn, an AT BYOD solution.


From: "ROZIN, EDEN" >
Date: Thursday, July 6, 2017 at 12:50:05 PM
To: "Thomas Nadeau" 
>, "FREEMAN, BRIAN D" 
>, "NOSHPITZ, CLAUDE" 
>, "LANDO, MICHAEL" 
>, "Kedar Ambekar" 
>
Cc: "WRIGHT, STEVEN A" >, 
"onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] YANG.XML format
***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
The artifacts types are configurable, so there is a way to add 'YANG' as 
another type for artifacts upload.
All the artifacts are located inside the distributed CSAR that contain all the 
relevant Service information.
If SDN-C would like to get the artifacts, they can.

Eden

From: Thomas Nadeau [mailto:thomas.nad...@amdocs.com]
Sent: Thursday, July 06, 2017 12:26 AM
To: FREEMAN, BRIAN D >; NOSHPITZ, CLAUDE 
>; Lando,Michael 
>; Kedar Ambekar 

Re: [onap-discuss] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Vul, Alex]

Hi Alla,

Can you please add support for hardware platform awareness  (EPA) to the list 
of future discussion topics. We would like discuss EPA support as part of vCPE 
and other ONAP supported use cases in R2 and beyond.

Thank you in advance,

Alex Vul
Intel Corporation


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Friday, July 7, 2017 9:37 AM
To: onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
Subject: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting's time can be 
managed accordingly.



1.   Review of suggested Use case subcommittee flow of operation as 
documented here https://wiki.onap.org/display/DW/Usecase+subcommittee , "Use 
case subcommittee flow"

2.   R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions

3.   R2 use cases: the initial proposals

a.   Network Function Change Management?

b.  Enterprise vCPE?

c.   More?

4.   AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F956.A7B92C80]

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] [openlab] OpenLab Kickoff Meeting Schedule

[Elhay Efrat]

Yes imho it could be great ;)

-- Sent from my Android Device



From: Chengli Wang
Sent: Friday, July 07, 2017 11:08:04 AM
To: Alla Goldner
Cc: Yang Xu (Yang, Fixed Network); stephen.go...@windriver.com; 
spat...@research.att.com; vanbra...@att.com; yangyi@chinatelecom.cn; Yunxia 
Chen; zhang.maope...@zte.com.cn; Alon Strikovsky; Elhay Efrat; 
bin.y...@windriver.com; ma...@research.att.com; denglin...@chinamobile.com; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
Hi,

Sorry for that.
My consider is that almost every nights(China)/mornings(US) are occupied by 
other community meetings. We can change to 8 next Tuesday evening if it's ok 
for the West Coast folks in US.

Regards,
Chengli

在 2017年7月7日，下午6:24，Alla Goldner 
> 写道：

Hi all,

As Elhay had mentioned, it is middle of night in Israel. If this call is 
scheduled for the suggested time slot, our assigned people will not have any 
possibility to participate. Please kindly consider this.

Best regards, Alla

 Original Message 
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
From: "Yang Xu (Yang, Fixed Network)" 
>
Date: Jul 7, 2017, 1:20 PM
To: 
wangchen...@chinamobile.com,stephen.go...@windriver.com,spat...@research.att.com,vanbra...@att.com,yangyi@chinatelecom.cn,Yunxia
 Chen 
>,zhang.maope...@zte.com.cn,Alon
 Strikovsky 
>,Elhay Efrat 
>,bin.y...@windriver.com,ma...@research.att.com,Alla
 Goldner 
>,denglin...@chinamobile.com
Good for me!

Sent from HUAWEI AnyOffice
From:Chengli Wang
To:Chengli Wang,Yang Xu (Yang, Fixed 
Network),stephen.go...@windriver.com,spat...@research.att.com,vanbra...@att.com,yangyi@chinatelecom.cn,Yunxia
 
Chen,zhang.maopeng1,alon.strikov...@amdocs.com,elhay.efr...@amdocs.com,bin.y...@windriver.com,Mazin
 E Gilbert,Alla Goldner,Lingli Deng
Cc:onap-discuss@lists.onap.org
Date:2017-07-07 04:04:53
Subject:Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

Hi,

If the time slot works for majority folks, I will send invite and logistic next 
Monday.

Thanks,
Chengli

在 2017年7月7日，下午4:00，Chengli Wang 
> 写道：

Hi Subcommittees,

I would like to invite you to attend open lab subcommittee  kickoff meeting. As 
so many meetings scheduled in each week it hard to find more suitable time slot 
for everyone located in different time zone.
I propose our first meeting time is 8:30 am July 12,2017 Beijing time, 8:30 pm 
July 11, 2017, EDT, Is it work for you?

On the Kickoff meeting, I proposed agenda below,

1. Proposed lab specification and guidelines (refer to OPNFV Pharos), linked 
here(Specification, https://wiki.onap.org/display/DW/ONAP+Lab+Specification 
Guide https://wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and 
comments in advance.
2. Discussion on collaboration with Integration team on CI/CD and E2E 
integration test.
3. Solicit Interest of Usecases Integration Testing from Lab Donators

Hope you can join us and feedback.

Thanks and Regards,
Chengli


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 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] 事件邀请：Re: Re: [openlab] OpenLab Kickoff Meeting Schedule

[Chengli Wang]

“wangchengli”已邀请您参加事件：Re: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule，它被安排于 2017年7月11日 下午9:00（GMT）。若要接受或拒绝这个邀请，请点按下面的链接。BEGIN:VCALENDAR
CALSCALE:GREGORIAN
VERSION:2.0
METHOD:REQUEST
PRODID:-//Apple Inc.//Mac OS X 10.12.4//EN
BEGIN:VEVENT
TRANSP:OPAQUE
DTEND:20170711T14Z
LAST-MODIFIED:20170710T033511Z
ORGANIZER;CN="wangchengli":MAILTO:wangchen...@chinamobile.com
UID:41ED73F9-CB79-44E7-98C5-2F563AC3C8C1
DTSTAMP:20170710T033511Z
LOCATION:https://zoom.us/j/9117271979
PRIORITY:5
DESCRIPTION:Hi all\,\n\nBased on feedback about time slot\, I would like
  to reschedule the meeting to 9:00 pm July 11\, 2017(Beijing)/ 9:00 am J
 uly 11\, EDT/4:00 PM July(Israel)/6:00 am July 11\, for West Coast folks
 .\nIt's realy hard to find the convient timeslot for everone\, thanks fo
 r your underdstanding.\n\nThe meeting logistic below.\n\nThanks and Rega
 rds\,\nChengli\n\nHi there\, \n\nONAP Open Lab Subcommittee is inviting 
 you to a scheduled Zoom meeting. \n\nTopic: Open Lab Kickoff Meeting\nTi
 me: Jul 11\, 2017 9:00 PM Beijing\, Shanghai\n\nJoin from PC\, Mac\, Lin
 ux\, iOS or Android: https://zoom.us/j/9117271979\n\nOr iPhone one-tap (
 US Toll):  +16465588656\,\,9117271979# or +14086380968\,\,9117271979#\n\
 nOr Telephone:\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (
 US Toll)\nMeeting ID: 911 727 1979\nInternational numbers availa
 ble: https://zoom.us/zoomconference?m=gOYfuD6bgjKCKALU45taWVbpR4FYRl5S\n
 \n \nFrom: Yunxia Chen\nDate: 2017-07-08 01:25\nTo: Chengli Wang\; Yang 
 Xu (Yang\, Fixed Network)\; stephen.go...@windriver.com\; spatsch@resear
 ch.att.com\; vanbra...@att.com\; yangyi@chinatelecom.cn\; zhang.maop
 eng1\; alon.strikov...@amdocs.com\; elhay.efr...@amdocs.com\; bin.yang@w
 indriver.com\; Mazin E Gilbert\; Alla Goldner\; Lingli Deng\nCC: onap-di
 sc...@lists.onap.org\nSubject: Re: [onap-discuss][openlab] OpenLab Kicko
 ff Meeting Schedule\nHi\, Chengli\,\nIf you would like to have some PDT 
 time zone to attend\, 5:30AM to them is too early.  Or could we move 30 
 minutes later\, like 9:00PM at Beijing time? \n \nRegards\,\n \nHelen Ch
 en\n \nFrom: Chengli Wang \nDate: Friday\, 
 July 7\, 2017 at 1:00 AM\nTo: Chengli Wang 
 \, "Yang Xu (Yang\, Fixed Network)" \, "stephen.goo
 c...@windriver.com" \, "SPATSCHECK\, OLIVER" 
 \, "vanbra...@att.com" \, y
 angyi \, Helen Chen 00725961 \, "zhang.maopeng1" \, "Alon.Strikovs
 k...@amdocs.com" \, "elhay.efr...@amdocs.com" 
 \, "bin.y...@windriver.com" \, "GILBERT\, MAZIN E (MAZIN E)" \, Alla Go
 ldner \, Lingli Deng \nCc: "onap-discuss@lists.onap.org" \nSub
 ject: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule\n \nHi Su
 bcommittees\, \n \nI would like to invite you to attend open lab subcomm
 ittee  kickoff meeting. As so many meetings scheduled in each week it ha
 rd to find more suitable time slot for everyone located in different tim
 e zone.\nI propose our first meeting time is 8:30 am July 12\,2017 Beiji
 ng time\, 8:30 pm July 11\, 2017\, EDT\, Is it work for you?\n \nOn the 
 Kickoff meeting\, I proposed agenda below\, \n \n1. Proposed lab specifi
 cation and guidelines (refer to OPNFV Pharos)\, linked here(Specificatio
 n\, https://wiki.onap.org/display/DW/ONAP+Lab+Specification Guide https:
 //wiki.onap.org/display/DW/ONAP+Lab+Guide)\, Welcome review and comments
  in advance.\n2. Discussion on collaboration with Integration team on CI
 /CD and E2E integration test.\n3. Solicit Interest of Usecases Integrati
 on Testing from Lab Donators\n \nHope you can join us and feedback.\n \n
 Thanks and Regards\,\nChengli\n \n
RESOURCES:
STATUS:TENTATIVE
SEQUENCE:1
CLASS:PUBLIC
X-MICROSOFT-CDO-IMPORTANCE:1
SUMMARY:Re: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
DTSTART:20170711T13Z
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
CREATED:20170710T033511Z
ATTENDEE;CN="Chengli Wang";CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED:mailto:ch
 l.wan...@gmail.com
ATTENDEE;CN="Yunxia Chen";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TR
 UE:MAILTO:helen.c...@huawei.com
ATTENDEE;CN="alla.goldner";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=T
 RUE:MAILTO:alla.gold...@amdocs.com
ATTENDEE;CN="alon.strikovsky";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSV
 P=TRUE:MAILTO:alon.strikov...@amdocs.com
ATTENDEE;CN="bin.yang";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRUE:
 MAILTO:bin.y...@windriver.com
ATTENDEE;CN="denglingli";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=TRU
 E:MAILTO:denglin...@chinamobile.com
ATTENDEE;CN="elhay.efrat1";CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;RSVP=T
 

Re: [onap-discuss] [openlab] OpenLab Kickoff Meeting Schedule

[Yunxia Chen]

Hi, Chengli,
If you would like to have some PDT time zone to attend, 5:30AM to them is too 
early.  Or could we move 30 minutes later, like 9:00PM at Beijing time?

Regards,

Helen Chen

From: Chengli Wang 
Date: Friday, July 7, 2017 at 1:00 AM
To: Chengli Wang , "Yang Xu (Yang, Fixed Network)" 
, "stephen.go...@windriver.com" 
, "SPATSCHECK, OLIVER" , 
"vanbra...@att.com" , yangyi , 
Helen Chen 00725961 , "zhang.maopeng1" 
, "alon.strikov...@amdocs.com" 
, "elhay.efr...@amdocs.com" 
, "bin.y...@windriver.com" , 
"GILBERT, MAZIN E (MAZIN E)" , Alla Goldner 
, Lingli Deng 
Cc: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

Hi Subcommittees,

I would like to invite you to attend open lab subcommittee  kickoff meeting. As 
so many meetings scheduled in each week it hard to find more suitable time slot 
for everyone located in different time zone.
I propose our first meeting time is 8:30 am July 12,2017 Beijing time, 8:30 pm 
July 11, 2017, EDT, Is it work for you?

On the Kickoff meeting, I proposed agenda below,

1. Proposed lab specification and guidelines (refer to OPNFV Pharos), linked 
here(Specification, https://wiki.onap.org/display/DW/ONAP+Lab+Specification 
Guide https://wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and 
comments in advance.
2. Discussion on collaboration with Integration team on CI/CD and E2E 
integration test.
3. Solicit Interest of Usecases Integration Testing from Lab Donators

Hope you can join us and feedback.

Thanks and Regards,
Chengli

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

Re: [onap-discuss] [openlab] OpenLab Kickoff Meeting Schedule

[wangchen...@chinamobile.com]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:-//Tencent Corporation//Foxmail
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
UID:41ED73F9-CB79-44E7-98C5-2F563AC3C8C1
CLASS:PUBLIC
DTEND:20170711T14Z
STATUS:TENTATIVE
TRANSP:OPAQUE
CREATED:20170710T033511Z
DTSTAMP:20170710T033511Z
DTSTART:20170711T13Z
SUMMARY:Re: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
ATTENDEE;CN=onap-discuss;ROLE=OPT-PARTICIPANT;RSVP=TRUE:MAILTO:onap-discus
 s...@lists.onap.org
ATTENDEE;CN=denglingli;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:denglingli@ch
 inamobile.com
ATTENDEE;CN=alla.goldner;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:alla.goldne
 r...@amdocs.com
ATTENDEE;CN=mazin;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ma...@research.att
 .com
ATTENDEE;CN=bin.yang;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:bin.yang@windri
 ver.com
ATTENDEE;CN=elhay.efrat1;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:Elhay.Efrat
 1...@amdocs.com
ATTENDEE;CN=alon.strikovsky;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:Alon.Str
 ikov...@amdocs.com
ATTENDEE;CN=zhang.maopeng1;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:zhang.mao
 pe...@zte.com.cn
ATTENDEE;CN=yangyi.bri;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:yangyi.bri@ch
 inatelecom.cn
ATTENDEE;CN=vanbrakle;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:vanbrakle@att.
 com
ATTENDEE;CN=spatsch;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:spatsch@research
 .att.com
ATTENDEE;CN=stephen.gooch;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:stephen.go
 o...@windriver.com
ATTENDEE;CN=yang.xu3;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:Yang.Xu3@huawei
 .com
ATTENDEE;CN=Yunxia Chen;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:Helen.Chen@h
 uawei.com
LOCATION:https://zoom.us/j/9117271979
PRIORITY:5
SEQUENCE:0
ORGANIZER;CN=wangchengli:MAILTO:wangchen...@chinamobile.com
RESOURCES:
DESCRIPTION:Hi all,\n\nBased on feedback about time slot, I would like to 
 reschedule the meeting to 9:00 pm July 11, 2017(Beijing)/ 9:00 am July 11,
  EDT/4:00 PM July(Israel)/6:00 am July 11, for West Coast folks.\nIt's rea
 ly hard to find the convient timeslot for everone, thanks for your underds
 tanding.\n\nThe meeting logistic below.\n\nThanks and Regards,\nChengli\n\
 nHi there, \n\nONAP Open Lab Subcommittee is inviting you to a scheduled Z
 oom meeting. \n\nTopic: Open Lab Kickoff Meeting\nTime: Jul 11, 2017 9:00 
 PM Beijing, Shanghai\n\nJoin from PC, Mac, Linux, iOS or Android: https://
 zoom.us/j/9117271979\n\nOr iPhone one-tap (US Toll):  +16465588656,,911727
 1979# or +14086380968,,9117271979#\n\nOr Telephone:\nDial: +1 646 558 
 8656 (US Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 911 727 1979\
 nInternational numbers available: https://zoom.us/zoomconference?m=gOY
 fuD6bgjKCKALU45taWVbpR4FYRl5S\n\n \nFrom: Yunxia Chen\nDate: 2017-07-08 01
 :25\nTo: Chengli Wang; Yang Xu (Yang, Fixed Network); stephen.gooch@windri
 ver.com; spat...@research.att.com; vanbra...@att.com; yangyi.bri@chinatele
 com.cn; zhang.maopeng1; alon.strikov...@amdocs.com; elhay.efr...@amdocs.co
 m; bin.y...@windriver.com; Mazin E Gilbert; Alla Goldner; Lingli Deng\nCC:
  onap-discuss@lists.onap.org\nSubject: Re: [onap-discuss][openlab] OpenLab
  Kickoff Meeting Schedule\nHi, Chengli,\nIf you would like to have some PD
 T time zone to attend, 5:30AM to them is too early.  Or could we move 30 m
 inutes later, like 9:00PM at Beijing time? \n \nRegards,\n \nHelen Chen\n 
 \nFrom: Chengli Wang \nDate: Friday, July 7, 
 2017 at 1:00 AM\nTo: Chengli Wang , "Yang Xu 
 (Yang, Fixed Network)" , "stephen.go...@windriver.com
 " , "SPATSCHECK, OLIVER" , "vanbra...@att.com" , yangyi , Helen Chen 00725961 , "zhang.maopeng1" 
 , "alon.strikov...@amdocs.com" , "elhay.efr...@amdocs.com" , "bin.ya
 n...@windriver.com" , "GILBERT, MAZIN E (MAZIN E)" <
 ma...@research.att.com>, Alla Goldner , Lingli De
 ng \nCc: "onap-discuss@lists.onap.org" \nSubject: [onap-discuss][openlab] OpenLab Kickoff M
 eeting Schedule\n \nHi Subcommittees, \n \nI would like to invite you to a
 ttend open lab subcommittee  kickoff meeting. As so many meetings schedule
 d in each week it hard to find more suitable time slot for everyone locate
 d in different time zone.\nI propose our first meeting time is 8:30 am Jul
 y 12,2017 Beijing time, 8:30 pm July 11, 2017, EDT, Is it work for you?\n 
 \nOn the Kickoff meeting, I proposed agenda below, \n \n1. Proposed lab sp
 ecification and guidelines (refer to OPNFV Pharos), linked here(Specificat
 ion, https://wiki.onap.org/display/DW/ONAP+Lab+Specification Guide https:/
 /wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and comments in 
 advance.\n2. Discussion on collaboration with Integration team on CI/CD an
 d E2E integration test.\n3. Solicit Interest of 

Re: [onap-discuss] [openlab] OpenLab Kickoff Meeting Schedule

[Lingli Deng]

Hi Chengli,

 

Thanks for coordinating this.

The new time slot works for me.

 

Thanks,

Lingli

 

From: Chengli Wang [mailto:wangchen...@chinamobile.com] 
Sent: 2017年7月7日 23:55
To: Chengli Wang 
Cc: Alla Goldner ; Yang Xu (Yang, Fixed Network)
; stephen.go...@windriver.com;
spat...@research.att.com; vanbra...@att.com; yangyi@chinatelecom.cn;
Yunxia Chen ; zhang.maope...@zte.com.cn; Alon
Strikovsky ; Elhay Efrat
; bin.y...@windriver.com; ma...@research.att.com;
denglin...@chinamobile.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

 

Hi.

More clarification about the new suggested time slot is  8:00 pm July
11(Beijing Time),  8:am July 11 EDT(US), 3: 00 pm July 11 (Israel)

 

 

在 2017年7月7日，下午7:08，Chengli Wang  > 写道：

 

Hi,

 

Sorry for that.

My consider is that almost every nights(China)/mornings(US) are occupied by
other community meetings. We can change to 8 next Tuesday evening if it's ok
for the West Coast folks in US.

 

Regards,

Chengli

 

在 2017年7月7日，下午6:24，Alla Goldner  > 写道：

 

Hi all,

 

As Elhay had mentioned, it is middle of night in Israel. If this call is
scheduled for the suggested time slot, our assigned people will not have any
possibility to participate. Please kindly consider this.

 

Best regards, Alla

 

 Original Message 

Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

From: "Yang Xu (Yang, Fixed Network)"  >

Date: Jul 7, 2017, 1:20 PM

To: wangchen...@chinamobile.com 
,stephen.go...@windriver.com 
,spat...@research.att.com 
,vanbra...@att.com  ,yangyi@chinatelecom.cn
 ,Yunxia Chen  >,zhang.maope...@zte.com.cn
 ,Alon Strikovsky  >,Elhay Efrat

>,bin.y...@windriver.com 
,ma...@research.att.com  ,Alla Goldner mailto:alla.gold...@amdocs.com>
>,denglin...@chinamobile.com  

Good for me!

Sent from HUAWEI AnyOffice

From:Chengli Wang

To:Chengli Wang,Yang Xu (Yang, Fixed Network),stephen.go...@windriver.com
 ,spat...@research.att.com
 ,vanbra...@att.com
 ,yangyi@chinatelecom.cn
 ,Yunxia
Chen,zhang.maopeng1,alon.strikov...@amdocs.com
 ,elhay.efr...@amdocs.com
 ,bin.y...@windriver.com
 ,Mazin E Gilbert,Alla Goldner,Lingli Deng

Cc:onap-discuss@lists.onap.org  

Date:2017-07-07 04:04:53

Subject:Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

 

Hi,

 

If the time slot works for majority folks, I will send invite and logistic
next Monday.

 

Thanks,

Chengli

 

在 2017年7月7日，下午4:00，Chengli Wang  > 写道：

 

Hi Subcommittees, 

 

I would like to invite you to attend open lab subcommittee  kickoff meeting.
As so many meetings scheduled in each week it hard to find more suitable
time slot for everyone located in different time zone.

I propose our first meeting time is 8:30 am July 12,2017 Beijing time, 8:30
pm July 11, 2017, EDT, Is it work for you?

 

On the Kickoff meeting, I proposed agenda below, 

 

1. Proposed lab specification and guidelines (refer to OPNFV Pharos), linked
here(Specification, https://wiki.onap.org/display/DW/ONAP+Lab+Specification
Guide https://wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and
comments in advance.

2. Discussion on collaboration with Integration team on CI/CD and E2E
integration test.

3. Solicit Interest of Usecases Integration Testing from Lab Donators

 

Hope you can join us and feedback.

 

Thanks and Regards,

Chengli

 

 

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 meeting on Monday

[Lando,Michael]

Hi,
Today's call will not occur.

The first call we will have will be on Wednesday an invitation will be sent.


BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com


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

Re: [onap-discuss] [vnfsdk] Regarding Story VNFSDK-18 and VNFSDK-31

[Kapeluto, Zahi]

BTW,
How does VNF packaging effort aligns with the already existing CSAR packaging 
code in SDC? Is this an effort to extract this functionality into a mS?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From:  on behalf of Murali p 

Date: Monday, 10 July 2017 at 15:20
To: "onap-discuss@lists.onap.org" , "Christopher 
Donley (Chris)" 
Subject: [onap-discuss] [vnfsdk] Regarding Story VNFSDK-18 and VNFSDK-31

Dear All,

https://jira.onap.org/browse/VNFSDK-18

https://jira.onap.org/browse/VNFSDK-31

Until now I could not find any code in the repository for  VVP (VNF Validation 
program).

[As per my understanding]Since the above two stories are related to tools from 
VVP, how can we go ahead
with these stories without analyzing or knowing VVP code.


  1.  I fear my effort may become duplicate without knowing what exists in VVP 
repo if I go ahead with implementation of above stories.
  2.  Link (interfaces) and high level flow between the related projects is not 
clear.

Any help or suggestion is welcome.

With regards,
Murali
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Call for volunteer to external standard coordination

[denghui (L)]

Hello all

I have created a page for external standard coordination, if you have resource 
to attend both ONAP and standard, and expertise in this area, please kindly 
help to volunteer
https://wiki.onap.org/display/DW/External+Standard+Coordination

thanks a lot for your help
Best regards,

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

Re: [onap-discuss] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi Lingli,

Thanks a lot for your feedback.
I fully agree with you that R1 discussions should be prioritized.
You can see that this item (R1 use cases (vCPE and vVoLTE): Status, Open 
issues, required actions) appears before the R2 use cases discussions.
However, we should limit this discussion to Status, Open issues and required 
actions, as mentioned, during Use case subcommittee meeting, for the following 
reasons:


1.   As agreed for R1 (there were quite a few discussions and emails shared 
by a different people in this regard), we have R1 expedited process, by which, 
upon use cases approval, responsibility on use cases coordination moved to 
Integration project. This results in a different meetings between use cases 
leaders and the respective involved projects. BTW, the feedback I am getting so 
far as that this work has been very productive, for both approved use cases.



2.   In order to analyse different projects dependencies and affected 
functionalities, technical issues should be discussed with people working on a 
different projects. The reason is that projects’ expertise is within a project, 
not within Use case subcommittee. We can’t force all projects’ ALL 
representatives to attend Use case subcommittee, while, only if all people 
working on specific project participate in discussion, we can have full 
functional coverage and appropriate split of responsibilities.



3.   We do need start talking about R2 use cases, in order to have our 
proposal ready for TSC review in advance before R2 starts, in order to align 
correctly and on time with R2  goals.


2 weeks ago I raised question on whether we should move to weekly use case 
subcommittee meetings. No response was received. I will raise it again today 
during the meeting, as, in my understanding, such a move is needed in order to 
allow a comprehensive coverage.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F96A.D2752D70]

From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Monday, July 10, 2017 9:41 AM
To: Alla Goldner ; 'BEGWANI, VIMAL' ; 
onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; 'onap-tsc' 
Subject: RE: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi Alla,

I wonder if we should prioritize the R1 usecase discussion in this time slot.

Currently, there are ad hoc meetings arranged respectively for VoLTE and CPE 
usecases, which makes people rather frustrating and not efficient because it is 
really hard to allocate a common time slot for cross project discussion, which 
I believe would be improved much if we host such discussion in this 
subcommittee, which to my understanding is the top priority.

Thanks,
Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: 2017年7月8日 0:59
To: BEGWANI, VIMAL >; 
onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
>
Subject: Re: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi, Vimal,

Yes, of course, happy to do that.

Here is the updated agenda:


  1.  Review of suggested Use case subcommittee flow of operation as documented 
here 
https://wiki.onap.org/display/DW/Usecase+subcommittee
 , “Use case subcommittee flow”
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   5G
   i.  RAN 
deployment
 ii.  E2E 
Network Slicing

 *   More?
  1.  AOB


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F989.346CD870]

From: BEGWANI, VIMAL [mailto:vb1...@att.com]
Sent: Friday, July 07, 2017 7:53 PM
To: Alla Goldner >; 
onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc 
>
Subject: RE: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Alla,
  We are still in an initial discussion, but I would like to add 5G RAN 
deployment and E2E Network Slicing support for 5G network.  Can we add it as a 
place holder?