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
20180109 Meeting Agenda & Minutes
1) Vodafone proposal about centralized and external tosca parser
1.1 Atul: the reason pick Aria is because aria is apache based
1.2 SDC: it will bring big change to all projects, it need to be approved by all projects and architecture committee, will also impact each catalog.
1.3 Michael Brenner recommend step by step to check whether it will works or not, first implement
1.4 some of parser couple with component implementation (data model)
Next step: Atul and Hui will build tiger team to handle R2 and R3+ plan
2)
2.1 NFV Parser current plan : Micro service
2.2 javaparser check
2.3 SDC tosca parser
3) ONAP R2 DM
https://wiki.onap.org/display/DW/Design-Time+Data+Model%3A+02.+Resource+Types+Hierarchy
https://wiki.onap.org/display/DW/Design-Time+Data+Model%3A+01.+Quick+Start
DM people work asap to publish the spec
4) ONAP R2 Service and Resource IM
Nigel needs to finalize the papyrus version asap
20180102 Meeting Minutes
1) Kevin will update accordin to our R2 falling back to service component.
2) Nigel will give a tutorial about papyrus this Friday in VNFSDK teleconf
3) papyrus version: Oxygen 3.2.0.201711120244
4) Rittwik will help to talk with Anatony to move foward with SDC DM - Basic, Resource
5) check A&AI related table gap by schedule another call or next friday.
6) need to build a time table to check all projects (SDC, VFC, SO, VNFSDK, MULTIVIM) progress,
7) Readout modeling of close loop control committee in the future
20171214 Minutes of ONAP Modeling workshop
1 Service IM: back to service(customer facing service)/service component(resource facing service, e.g. network service)/resource/resource component layering class diagram, not using composite/decorative pattern for Beijing, translate into papyrus format based on agreed clean version.
2 Resource IM: For design time model, agreed to work on a subset of IFA011 for Beijing (i.e. remove internalCP as show in the discussion page), agreed to add hierarchy for CP inheritance, agreed to work on the latest version of IFA011 (v2.3.1). For run time model, agreed to refactor some of the attributes (e.g., ip addresses).
3 Design time DM: Agreed on Service and Resource hierarchy, while both service and resource can leverage substitution mapping mechanism to realize self-recursion aggregation or composition relations if needed by the IM.
4 Runtime DM A&AI will update NFV related API? in order to align with Information model, and notify the related project accordingly
5 Agreed to work on a concrete example to show how ONAP IM maps to ONAP DM.
6 R2 will be based on TOSCA simple profile 1.1 other than 1.2, but may need to consider some special feature of 1.2 if needed by the use case
7 Each DF should be described in a single TOSCA Service template (VNFD) and considered as a single VNF, in Beijing release, one VNF package will only contain one VNFD
8 R2+ Modeling spec naming convention will use the low camel for attribute names, will consider to add naming convention check during M1/M4
9 WiKi will be used for Modeling spec intermediate version, Readthedoc will be used for published version
10 Michela volunteer to start to work on the common terminologies for ONAP modeling
11 Modeling spec will be migrate to Papyrus asap, needs to decide version number and setup the timeline to proceed it
12 Use Jira/backlog to track the work asap
20171213 Deployment Flavor Meeting Minutes
1) each DF should be described in a single TOSCA service template (VNFD) and considered as a single VNF.
2) In Beijing release, one VNF package will only contain one VNFD.
20171205 Meeting Minutes
1) December event will best use Monday to Wednesday for R2+ Modeling spec disucssion
2) need to establish operator's list to feedback modeling design like service type
3) composite / Atomic pattern discussions follow john's suggestion
20171205 Meeting Agenda
1) Service IM
2) Resource IM
3) Service/Resource design time DM
4) December events Program
5) M3 checkpoint
6) M2/M4 checkpoint
20171121 Meeting Minutes
1) Service IM
1.1 change catalogitem into descriptor
1.2 Lingli will lead WAN descriptor discussion asap
2) Resource IM
2.1 move vnfc class diagram back into discussion page
2.2 consider data type and constraint
2.3 a&ai NFV might not adapt to VDU, there is still needs for VNFC at runtime
3) Design DM
3.1, is this target DM or R2 DM? there are still limitation for implementation to implement target DM.
20171121 Meeting Agenda
1) Service IM
2) Resource IM
3) Service/Resource DM
4) December events Program
5) M3 checkpoint
6) M2/M4 checkpoint
20171114 Meeting Minutes
1) R2+ Modeling spec discussion procecure confirmed
Step 1: Members could submit their contribution on this page for review and disucssion.
Step 2: Discussion will happen in "Discussion Page" of wiki, if there is unresolved or non-replied items, they will not be moved to the "clean version"
Step 3: Move the concensused part into "Clean Version" of wiki.
2) Suggestion to start DM design asap , and encourage VNFSDK continue to work on it
3) Maopeng and Shitao will send email to the list about questions, other than read wiki page every day
4) Concensused part will be moved to clean version of wiki page
5) Service class chararacteristic diagram will be tentatively droped due to no commitment from SDC and AAI
20171114 Meeting Agenda
1) Wiki page working procecure clarification (input → discussion→ clean page)
2) Clarificaiton discussion of update doc
3) Wiki Page discussion key issues
4) Naming convention from OASIS
20171031 Meeting Minutes
1) Andy presented M3 checkpoint suggestion for IM/DM, will create a wiki page for 2 weeks discussion
2) Jimmy will find modeling people from AAI to answer A&AI question about ECOMP IM on the wiki page by this week.
3) Kevin & Andy will provide update of ECOMP IM and answer ECOMP IM questions by this week.
4) David confirmed that SDC will adopt ECOMP Service IM class diagram, one remaining issue of nested service descriptor still open.
Maopeng has already provided the use case, David will check this use case and feedback whether SDC is fine by this week.
David is requested to answer the remaining Service IM question for SDC part this week.
5) There was a concensus to start with SDC IM and mapping with ECOMP IM, and add extensions with missing.
David confirmed that SDC team will accept ECOMP Resource IM terminology, e.g. VFC and CP will be renamed as VDU and extCP etc.
However, there will be still discussion needed for parameters.
7) Shitao mentioned that OASIS had naming convention proposal, shitao will publish on the wiki page, discuss next week.
20171107 Meeting Agenda
1) M3 check proposal, Andy
2) Service IM discussion, Maopeng
3) Resource IM discussion, Yangxu
4) ONAP Modeling workshop, all
20171031 Meeting Minutes
1) Kevin & Andy will provide update of ECOMP IM and answer ECOMP IM questions
2) David needs to confirm whether SDC will adopt ECOMP Service IM class diagram
3) David needs to confirm whether SDC will accept ECOMP Resource IM
4) Jimmy needs to answer A&AI question about ECOMP IM on the wiki page.
20171031 Meeting Agenda
1) Gap analysis for service and resource
2) Other proposal
20171024 Meeting Minutes
1) R2+ Modeling design principles and guideline is tentatively fixed, Lingli will create a issue page for further discussion
2) Hui will work with Rittwik and Andy about IM gap and SDN IM part and presented next week
3) Hui will create 4 wiki page for people to start the work
20171024 Meeting Agenda
1) R2 Modeling design principles and guideline
2) Future plan of 2 tracks
20171017 Meeting Agenda
1) R2 Modeling design principles and guideline
2) Future plan of 2 tracks
20171010 Meeting Agenda
1) R2 Modeling design principles and guideline
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