ONAP R4 Resource IM Call 2019-2-04

General Information:

• Date and Time: 2019, February 04, 10pm~11pm Beijing Time, 9am~10am US Eastern
• Meeting Room: https://zoom.us/j/645982535

Agenda:

• Agenda review
• Modeling Current Activity Status
• Current R3 Clean Compare with IFA011 V2.5.1ff
• Root Class Analysis

Material:

• Modeling Current Activity Status
• Comparison of Current R3 Clean Version with IFA011 v2.5.1
• ONAP R4 Modeling High Level Requirements

Minutes:

• Modeling Current Activity Status
  We briefly reviewed the current activity lists.  We need to focus on bringing these items to closure. 
• Current R3 Clean Compare with IFA011 V2.5.1:
  • Jessie walked us through the analysis.  The compare was made against the R2 WIKI table, with some peeks at the Papyrus model.  Observations made include:
    • Removal of certain material including references to yaml, or which version of IFA the definitions came from the ONAP model
    • Fixing things that were specified as dentifiers that should be relationships
    •  A number of attributes need to be updated to "deprecated".
    • VnfElemenetGroups was tagged as obsolete.
    • Discussion about restricting the enum list, or even using enums rather than strings due to handling updates.   Maybe a discussion item in the Tuesday modeling calls?
    • May need to look at IFA014 for some material.
    • Replace vnicorder with order
    • There are a number of ifa011 defined entities related to deployment flavor that we do not have.  Should we include them?  Suggestion from Alex is to include them
  • We do not want analyze and have two consensus votes, on for the WIKI and another for the Papyrus output.   One approach could be for the Resource team to provide comments on the Wiki compare in the next two weeks, and use that as a basis to update the Papyrus model, and perform a consensus vote on that output.
• ONAP Root Analysis
  Did not have time to discuss this agenda item.
• Next call: