...
Upcoming call
Logistics
Start Time: 1 pm 8 am US western SundayFriday, March 2530
Length: 4 5 hours
Meeting room: https://zoom.us/j/882442618
Part of the ONAP Sunday afternoon Friday morning modeling session in ONS 2018 (30 March 2018)
Proposed Agenda
- TBA
Past calls
20180325
Agenda
- ONAP R2+ service IM Discussion Review and Proposal
...
- SDO Persptive
MEF (Jack Pugaczewski)
TMF (John Wilmes)
ONF (Nigel Davis)
- ONAP R3 Service IM Proposals
Service Service Order (Andy/Kevin) (Skipped as Andy is not online)
Service
Service Component: Network WAN Service Descriptor (Maopeng ZhangZhuoyao Huang & Nigel Davis) Service
Service Component: WAN Network Service Descriptor (Zhuoyao Huang) Maopeng Zhang & Thinh)
- Priority and Planning Discussion
The current status of service IM and my observations (Xu Yang) (Skipped for time limitation)
Discussion
Past calls
20180325
Agenda
(Partially covered during the flow of discussion)
Minutes
• ONAP R2+ service IM Discussion Review and Proposal
...
Service IM layering framework (Lingli Deng)
• SDO
...
Perspective
• MEF (Jack Pugaczewski) - MEF API Development Approach provides an introduction to MEF LSO and proposed a tooling chain that triggered the discussion of common information model methods and strategies. It was agreed that the ONAP community can be used as a catalyst to promote CIM from vision to implementation between related SDOs of the Radeon. However, the ONAP's own design and implementation of the model is not tied to the existing specification or specification plan of the CIM or any other SDO. The ONAP model work is based on the developers' willingness to contribute, and the development of the version is the iterative design and organization cycle of the discussion. MEF models are still evolving and featured with the model-driven approach and usage of decorator pattern.
• TMF (John Wilmes) The advantage of staying compatible with the legacy systems is highlighted from TMF SID modeling proposal. A mapping analysis of the ETSI NFV IFA model to the TMF SID in terms of the ETSI NFV vCPE use case is proviced. It is suggested to supplement the ONAP service scenario with a service-level mapping analysis, add elaboration on the relationship between SID and openAPI, and submit to the next level discussion on Friday Workshop.
• ONF (Nigel Davis) - ONF Modeling introduced the ONF modeling experience, and it is envisioned that the modeling for both resource and service would converge. Specific suggestions for WAN descriptor refinement based on ONF CIM and TAPI were presented. It is recommended that the follow-up continue to discuss the model design refinement offline.
• ONAP R3 Service IM Proposals
...
- - Skipped for lack of presenter
- Service Component:
- Network Service Descriptor (Maopeng Zhang)
- Suggestion to extend resource modeling for network service descriptor in R2 is not accepted by SDC team.
- Request to accelerate NSD DM work is made by Thinh. If no further comments on the NSD IM is received for the next week, it would be moved into a clean version (stable phase), based on which the corresponding NSD DM work could be kicked off.
- Service Component: WAN Service Descriptor (Zhuoyao Huang
- Network Service Descriptor (Maopeng Zhang)
...
- )
Nigel suggested to change some concepts of WAN IM proposal for aligning with ONF IM concepts( following ITU-T Recommendation M.3100 ) better and keep the UML class topology of original WAN IM proposal:
WAN IM
Nigel suggestion
Forwarding Construct
SNC(Subnetwork Connection)
FC Port
CTP(Connection Termination Point)
Node
SN(Subnetwork)
FC Route
SNCRoute(Subnetwork Connection Route)
XC Port
CTP(Connection Termination Point)
- )
•
Service Component: Network Service Descriptor (Maopeng Zhang & Thinh)
Priority and Planning Discussion
- The current status of service IM and my observations (Xu Yang)
...
- - delayed due to time limitation
...
- Discussion
...
- for follow-ups
- Lingli provides customer-facing business scenarios as input for service model discussion and comparison by Tuesday;
- For Friday workshop, each presenter (including SDOs/individuals) is expected to provide their respective proposal models and with the context of customer facing business scenario;
- Based on which, the team is expected to develop a more clearly scoped target and collaborative pattern for R3+.
Minutes
...
20180321
Agenda
- Agenda bashing
R2 Status summary and priority
ONS workshop agenda
- R2 VNFD DM clean up discussion (added for R2 priority)
- Network Service Descriptor R2 Implemenation Discussion
- Service Order Model (added to the agenda, but deferred to next meeting due to time limit)
...