ONAP R6 Resource IM Call 2020-3-9

General Information:

  

Agenda:

  • Agenda bashing - 5 minutes

    • Meeting time change? (DST)

    • ETSI NFV R3 feedback

    • Modeling glossary

  • Modeling Documentation - 0 minutes

  • Model Proposals - 40 minutes

    • PNF instance model

    • license management

    • allotted resource

    • 5G RAN service

  • Modeling Process discussion - 10 minutes

Material:

Minutes:

  • Agenda bashing:

    • Meeting time change

      • check if people would like to move the meeting time 1 hour earlier since the DST has begun in US

      • feedback:

        • both: Andy

        • prefer not to shift: Michela (overlap with ETSI-alignment call)

        • prefer to shift: Ben (to avoid overlapping with the requirement call)

      • AP:

        • Ben to check the requiremnt call will change the meeting time

          • Alla will not change for now (the requirement call will work by UTC time)

        • Michela to check the ETSI-alignment call will change the meeting time

    • ETSI NFV R3 feedback

    • Modeling glossary

      • Xu is working on a review wiki page

  • Modeling Documentation

    • suggestion from Michela: to add relationship documentation in the model (not only in the diagrams), and create Jira for it

      • Q: how to document the relationship classes in the papyrus?

      • will discuss later

    • AP:

  • Model Proposals

    • PNF instance model

      • Jacqueline has generated PNF instance model from A&AI input

      • the problem is the model still doesn't have attribute descriptions

      • Jacqueline suggests to ask Jimmy to re-start the reverse engineering call to solve this problem

      • Andy suggests to reverse engineering from the swagger documents (instead of UMLs)

      • AP: Jacqueline will talk with Jimmy about this issue, Andy will help create a long-term call if needed

    • license management

      • License Model Review Comments

        • #1: discuss how to document relationship classes

          • Xu will create a Jira and update the wiki page

        • #2: add a label to the diagram explaining why the model is refered to only VNFD now

          • will update

        • #3: SPPoolLimit and VendorPoolLimit are not found in the "resource onboarding" page, i.e., no evidence for including them in the model

          • Andy will double check

        • #4: question on how to deal with EntitlementInstance and LicenseKeyInstance in the approval? (suggest to keep "experimental", i.e., not requesting approval, for the current proposal)

          • Xu will create a Jira to discuss how to deal with the experimental classes in the readthedocs

        • #5: there is an attribute marked using "Future" stereotype, suggest not to use the "Future" stereotype

          • is "Future" stereotype needed compared with the "Experimental" stereotype?

            • no "Future" stereotype is defined in the "lifecycle stereotype proposal"

          • Andy will check and remove "Future" if it exists

    • allotted resource

    • 5G RAN service model

      • presentation of the A&AI discussion on this topic

  • Modeling Process Discussion

    • discuss the current status of the modeling process discussion

    • focus on modeling generation and approval process

      • during the process, modeling subcom needs to negotiate with arc, use case and other communities for modeling design

    • suggest to add checklist to M3

      • for use case team and also projects like A&AI, etc. to check the model impacts

    • see Proposed ONAP Release Process Updates for Information and Data Modeling