ONAP R6 Resource IM Call 2019-12-16

General Information:

• Date and Time: 2019, Dec 16th, 10pm~11pm Beijing Time, 9am~10am US Eastern
• Meeting Room: https://zoom.us/j/645982535
• Meeting Recording:  
• Meeting Chat Log:  
  

Attendees

• Kevin Scaggs
• Xu Yang
• Jacqueline Beaulac [Ericsson]
• MEHMET TOY
• Michela Bevilacqua
• Zu Qiang
• Benjamin Cheung
• guochuyi

Agenda:

• Agenda bashing - 5 minutes
  • items for checking:
    
    • ves spec
    • PNF instance model
    • modeling glossary update
    • plan for X'mas and new year's eve
• allotted resource (final comments)  - 20 minutes
• Modeling Process discussion - 25 minutes

Material:

• Proposed ONAP Release Process Updates for Information and Data Modeling
• Modeling sub-committee Contributions
• Allotted Resource Revised
• New PNF example

Minutes:

• Agenda bashing:
  • VES specification -
    
    • Kevin has checked with Alok, VES 7.1.1 is expected to be closed one week ago (and Alok is OOF since then)
    • the only impact to IM is to change one attribute which is related to one relationship
  • PNF instance model
  • Modeling glossary update -
    • DOC TEAM DISCUSSION - Andy & Kevin joined the doc. team discussion last week, spend time showing what had been developed. Well received. Highlighted idea of experimental vs preliminary. Some exp. don't necessarily have def.; incl. exp if it has a definition. exper. is ok to have. This may be just one aspect of the glossary. Acronym is not in an information model.
    • NEXT STEPS - As Next step - will add Stereotype back to the GenDoc script. There will be a follow-up discussion in 2020.
    • Q&A -
      • Q: Is the glossary going to be labeled "Modeling Glossary"? A: probably a more general glossary.
      • Q: The terminology should be anchored across different projects e.g. service might be a different?
      • Q: is a cross-project discussion planned? A: Don't know.
      • Q: Who will OWN the Glossary? A: probably the Docs team w/ the Modeling team being a contributor.
      • Q: e.g. slicing NSMF is basic concept for slicing part; will this be also one of the modeling glossary entries? i.e. Domain-specific concepts should they be included in the Glossary? A: probably not. guochuyi should be analyze some of the specific terms? A: Yes. If an information model is about concepts w/ attributes; should a slice be one of those concepts? If there are other sources of info going into the glossary, even if it is not a class, a S/C could submit the concept to the docs team.  
      • ACTION: Benjamin Cheung will contact Sofia Wallin to see if U/C teams should contribute to the glossary.
      • Q: Has doc team requested u/c to provide input for glossary?
  • Holiday Season plan -
• Discussed items:
  • allotted resource
  • Modeling Process discussion

RECORDING