Modeling 2019-01-15
Meeting Info:
Zoom Meeting Link: https://zoom.us/j/137904496
International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a
Jan 15, 2019 | 2019 Modeling Subcommittee Recordings |
---|
Duration 60 minutes
Duration | Agenda Item | Requested by | Notes / Links |
---|---|---|---|
START RECORDING | |||
5 | Co-chair | @Hui Deng @Andy Mayer | Welcome and Plan M2 and M3 Checklist to be shared at the TSC this week for approval. |
5 | Resource IM report | @Xu Yang | ONAP R4 Resource IM Call 2019-1-14 Update of PNF Descriptor (figure updated), still working updates before final review of proposal. Final review during next week's Resource IM call. Policy Model introduced by Kevin. Current scope in Dublin is focused on ECA type policy. Intent (declarative) policy definition is for future design. Will have individual discussions with modeling stakeholders SOL001 alignment. Thinh provided comments and would like further clarification of ONAP extensions of IFA011 v2.5.1. Recommend contribution of extensions back to ETSI. Thinh stated that ETSI IFA011 2.6.1 IFA014 2.6.1, comment opportunity has been closed. Our comments will need to be directed towards v2.7.1 or v3.1. Thinh will look into the timefame. 2 tasks: 1) ONAP Dublin release model based on v2.5.1; 2) Identify gaps to ETSI v2.7.1 Alex, how do EPA attribute schemas get provided back to ETSI. Is there a data model in ONAP? |
5 | Service IM report | @Lingli Deng @LIN MENG | No update |
5 | DM report | @Anatoly Katzman | DM call yesterday went through list of Paris F2F actions and prioritized items. Will place on the wiki and capture priorities in JIRA. Some highlights: TSOCA 1.2 is a high priority for Dublin, but need contributors. Grammar changes, plus update of Type Library. Alignment with SOL001 2.5.1, ONAP may extend, PNFD updates, finalized type definitions Alignment with SOL004 package for internal distribution. Need to model "Service Slice". Need guidance from Arch Sub-committee. Should strive to have general and extensible modeling solutions. Support for multiple Data Model versions in ONAP. Need to document on wiki versions that are supported in a specific release. Possible to use multiple parsers. Need further alignment of internal data types and on-boarding data types. |
15 | Recap of Paris meeting | @Hui Deng @Andy Mayer | |
Additional topics | TOSCA simple profile need 1.2 in SDC. Need to get SDC to commit to implementation. (Shitao will put recommendation together for SDC call next week) @Former user (Deleted) WIll also create JIRA item for this topic. Need to update ONAP working assumptions and agreements for Dublin, Capture specific agreements for support in specific ONAP components. (R4 High level requirements page) Next week: walkthough JIRA items as well as R4 High level requirements page. |
Agreement on ??
ACTION ITEMS: