Modeling 2019-01-29

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

https://lf-onap.atlassian.net/wiki/display/DW/ONAP+R4+Resource+IM+Call+2019-1-28

Call to approve PNFD (for the Clean Model) with the attributes geographicalLocationInfo and swVersionList removed for the present R4 release. Subcommittee will initiate 2 week email poll on this question. (call for general consensus during the Feb 12th call).

 5

Service IM report

@Lingli Deng

https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Service+IM+Minutes+20190124

Focused discussion on R4 items. Items 1, 2, 3, 4, and 5 are to be included in R4 High Level requirements.

Consider having a separate discussion thread for service descriptor vs nested services

 5

DM report

@Anatoly Katzman

Focused on updating R4 High Level Requirements for Data Modeling.

See: ONAP R4 Modeling High Level Requirements

5

Infrastructure Modeling Discussion

@Arun Gupta

@Alex Vul

General interest in holding Infrastructure Modeling calls.

What Use Cases would use this? (e.g., card - slot capacity, Cloud Provider abstraction, consumption, etc.)

ONF modeling may be useful.

@Andy Mayer will set-up poll and call.

15

R4 High level requirements

@Hui Deng

@Andy Mayer

 https://lf-onap.atlassian.net/wiki/display/DW/ONAP+R4+Modeling+High+Level+Requirements

Need to influence actual code with High Level Requirements.

Code commitment is essential for data model. Need modeling leads to work with PTLs and members to identify development resources.

Input needed by M2, please provide input by Feb 12th (especially on the Code Commitment).