...
• ONAP R2+ service IM Discussion Review and Proposal
• 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.
...
- Service Order (Andy/Kevin) - 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)
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)
- Network Service Descriptor (Maopeng Zhang)
• Priority and Planning Discussion
...