Modeling project and Modeling sub-committee are using the same teleconf bridge, one week for Modeling project, then the next week will be for Modeling sub-committee.
Meeting Bridge
- Meeting every Tuesday 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET, 9:00/10:00PM Beijing -
- IRC -https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling
Meeting bridge?https://zoom.us/j/137904496
Or iPhone one-tap (US Toll): +14086380968,137904496# or +16465588656,137904496#
Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 137 904 496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a
Meeting List
ONAP Modeling session in September 2017 during F2F deverloper event
20170919 Meeting Agenda
1) AT&T present the Data Model
2) Release 2: September F2F event
20170912 Meeting Minutes
1? AT&T presented information model
2? AT&T were asked to open the spec of IM and DM within this week
3) AT&T will present Data model next week.
20170912 Meeting Agenda
1) AT&T will present ECOMP AID information model and GAP [ECOMP info model, ECOMP info model (ppt)
3) Release 2: September F2F event
20170905 Meeting Minutes
1) Last issue of Release 1, WAN will be discussed between SO/SDNC in the list
2) Release 2 planning:
2.1) ECOMP AID (Rittwik) will present in the next teleconf about Ecomp info model, and the proposal of next step.
2.2 ) September Modeling session in Paris
2.2.1) It will be divided into 2 session, first preparation discussion (2 hours), the second is the summary discussion (2 hours)
2.2.2) Rittwik and Lingli will try to join and lead the information model proposal discussion
2.2.3) Will invite PTL from SDC/VNFSDK/SO/VFC/A&AI/EAPI/SDNC to feedback about R1 modeling and R2 suggestion
2.2.4) Will not arrange the close loop modeling discussion this time.
2.3) there was suggestion about working with Architecture committtee
2.4) try to follow top down approach and bottom up for coding part as well, let them them meet in the middle.
20170905 Meeting agenda
1) Regular Modeling Project topics
2) Left issues for release 1
a) SDC WAN
3) Release 2 plan
a) Before F2F Developer event
b) Modeling session in Developer event
20170829 meeting minutes
1) Issues have been resolved by SDC
2) only WAN spec left unresolved, others finalized, VNF CSAR package will be finalized until Friday VFC/SDC meeting
3) Namespace will be discussed future for release 2
20170829 meeting agenda
1) Remaining issues of modeling spec among VNFSDK/SDC/VFC/SO
2) Modeling specification for ONAP release 1
3) ONAP Model namespace related to both R1&R2
20170822 meeting minutes
1) Spec would better be more detail specified like tosca simple profile version and ETSI NFV spec
2) Whether VNF CSAR will be changed from import of SDC to outport of SDC.
3) Heat flow should be added into Release 1 diagram
20170822 meeting agenda
1) Modeling project, (only 1 tosca parser is on the repo for VFC, UUI hasn’t confirmed yet)
2) Check the status of interface and modeling spec
Interfaces
a) VNFSDK-SDC
b) SDC-SO
c) SDC-VFC
d) SO-VFC
e) SO-SDNC
Modeling specs
1.a) VNFD (skip for R1?)
1.b) SD
1.c) NSD
1.d) WAN spec
1.e) vnf package (skip for R1)
3) ONAP modeling namespace
20170815 meeting Minutes
1?Service template has finalized WAN as the resource which needs a new definition of type of resource in SDC
2?WAN discussion
ONAP WAN Modeling Draft - R1 Volte use case.pptx
2.1) SDNC expect the hierarchical naming for WAN YANG modeling, need to work jointly with Brian.
2.2) how SO do tosca translate into YANG depends on contribution of the code
3? Workflow will be presented in SDC next week
4? VNF CSAR proposal needs to go back VNF SDK to get consensus before submission to modeling subcommittee
The consensus of the VNF SDK modeling sub-project was reached and described in ONAP VNF Model (PROPOSAL for Release 1)
5 ) other topics will continue to go to SDC session.
20170815 meeting agenda
1) Service template design (resolved?)
2) WAN discussion (SDC-SO, SO-SDNC)
3) Workflow design
4) VNF CSAR format
5) SDC vs VFC interfaces
6) Onboarding Open-O types
20170803 meeting minutes
1) SDC team will start to support service composition from R2
2) agree the hack solution, SDC will confirm it in 3 hours
3) ZTE will propose tosca based SD-WAN solution to SDC for review and will also coordinate with SDNC project.
4) modeling committee will start to work on IM and DM as soon as possible
20170724-26 virtual meeting agenda
1) use case 1/2/3 coordination with modeling
2) modeling spec discussion with other projects
2.1: VNFD (VNF-SDK, ICE, SDC, SO, VF-C)
2.2: NSD (VNF-SDK, ICE, SDC, SO, VF-C)
2.3: SO (SDC, SO)
2.4: A&AI
2.5: workflow (SDC, SO, VF-C)
2.6: CLAMP, Policy, DCAE modeling
20170718 Meeting Minutes
1) we don't mandate the unfiied tosca parser API during 1st release
2) need to coordinate with SDC PTL about their modeling spec
3) will apply for time slot during Virtual meeting for modeling, agenda will be posted
4) create sub page under committee to publish the spec of modeling
5) Modeling project and Modeling subcommittee will be splited into 2 teleconf every 2 weeks.
20170711 Meeting Minutes
1) This is the UML based Information model for VNF and NS, mostly come from ETSI NFV IFA spec.
2) Michael suggest that ONAP will not follow IFA 1:1 Mapping
3) Lingli suggest that we need to be cautious about release cadence.
3) VNF package and VNFD spec of VNFSDK will overlap with the spec submited by VF-C, the harmonization of spec will be done by Modeling subcommittee
4) NSD need to be updated to show the difference with IFA spec