Modeling 2018-11-13

Meeting Info:

Zoom Meeting Link:  https://zoom.us/j/137904496
International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

Nov 13, 2018

2018 Modeling Subcommittee Recordings

Nov 13, 2018

2018 Modeling Subcommittee Recordings

Duration 60 minutes

Duration

Agenda Item

Requested by

Notes / Links

Duration

Agenda Item

Requested by

Notes / Links

START RECORDING

 5

Co-chair

@Hui Deng

@Andy Mayer

Welcome

5

ONAP Model Governance Approved

@Andy Mayer

@Kevin Scaggs

Approved version on wiki

Approved ONAP Model Governance

 5

 Resource IM report

@Xu Yang

Discussed abstract NF (Network Function) concept and plan for future proposals.

@Kevin Scaggs and @Chesla Wechsler will provide additional contributions.

Initial proposal shows difference between on-boarding and internal model as an initial draft. Clarifying relationship between on-boarding and internal model. Further work will be accomplished based on input wiki page.



 5

 Service IM report

@Lingli Deng

@LIN MENG

Please add your topic or proposal under 'Proposed Agenda' in this page ( ONAP R4+ Service Modeling Discussion Calls ) for 11.14 Service IM call.

Discussed Service Instance model. And how to model NS in A&AI. Alignment of attributes. Most attributes clarified.

Follow-up : NS Level and Flavour ID (need Arch team input)

Discussion on how to represent Service Specific attributes (e.g., Bandwidth, QoS, SLA) in A&AI @Chesla Wechsler is following up.

 5

 DM report

@Anatoly Katzman

@Chesla Wechsler

Did not meet

10

Development Process Improvements for Modeling

@Kevin Scaggs

Release specific model milestones need to have more formal description of what is expected at each milestone.

Need involvement of components

Review proposed M3 checklist

Please review and provide comments on: Proposed M3 Checklist modeling updates discussion

Review Material presented by Kevin: <link>

10

Updates to Papyrus Modeling Process

@Kevin Scaggs

Process proposal presented. Posted on wiki for additional comments. Will review comments next week (Nov 20).

Proposal may be found here: <link>

Use of stereotypes to move from working to master to indicate maturity level of model elements

Need mapping of stereotypes to the approval status.

10

R4 Modeling for Controller (SO identification of proper controller) Proposal

@Benjamin Cheung

Modeling subgroups should assess impacts and report back .

See:

https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16268543

https://lf-onap.atlassian.net/wiki/display/DW/Casablanca

Controller to NF Association.

Can "Owning Entity" relationship be used to describe the "Technology Domain" (need to assess in Resource Info Model.

Can also apply NF Type/Role/Function

Possibly use "Line of Business" as well to tag NFs

Map to Persona Type (not controller instance)

@Benjamin Cheung and @Chesla Wechsler to discuss during Ben's Wednesday call, and provide model recommendations at next weeks Service IM call.

15

TOSCA Task Force (Update)

@Alex Vul

Earlier on the agenda next week.


 

Agreement on ??

ACTION ITEMS:

@Andy Mayer will summary page for a table sub-teams showing work and status of on-going topics. (input, discussed, working, approved) and time-frame.

(reach out to subteam leads). 

Next week: Using JIRA for tracking modeling subcommittee tasks @Michela Bevilacqua

@Chesla Wechsler @Alex Vul @Former user (Deleted) to review and make a proposal for renaming the term "internal model" where such models are shared across the platform (one proposal was "platform model")




Zoom Chat Log