2019-02-13 Meeting Agenda and Minutes



  1. Admin (@Former user (Deleted) )

    1. Recent Updates Summary - See Vnf 2.5.1 update notes below

    2. Model Observations and Concerns

      1. Duplicate attributes - removed from VirtualLinkProfile - given they are in L2ProtocolData

      2. Handling of "New Proposals" - especially if multiple editors

        1. Options & Notes 

          1. Completely new domains like Pnf - not an issue

          2. Make proposals in own local copy

          3. Make a package and copy all relevant artifacts and edit, merge when done

          4. Create a 'duplicate' copy of item being edited (Vnfd and VnfdDraft)

          5. Create a "Proposed" stereotype with a string that can be populated with (By Jessie).  

            1. Could use Experimental with a string?? - this will probably not work.   What if already accepted, then experimental???

          6. Should we allow for multiple editors, or should there just be one to not compound the problem?

          7. Use colors of text to highlight proposed changes with a comment

            1. Colors only apply to diagrams, not the tables 

            2. Would have to standardize on colors

        2. Premise

          1. The editor must not 'destroy' accepted material until updates are accepted 

          2. Must have traceability

    3. Papyrus Bug Status

      1. Bug resurfaced with cross sub-model moves

      2. Could have Vincent reclean

      3. Hopefully fix will be in next version - Jessie will engage with Vencent 

    4. Common is getting fairly large - when do we break out some additional submodels? 

  2. Submodel Status

    1. Common (@Kevin Scaggs)

    2.  

      1. Root

        1. Working with Jessie on a Root Hierarchy Proposal.

        2. Hope to have something to socialize next week.

      2. VES - Version 7.1 Model Draft Complete and ready for review on next Monday's Resource IM call.

      3. Policy

      4.  

        1. Met with the Policy PTL this week

        2. Looking to refine model per insights provided

      5. License

        1. Updated Papyrus Model to same level as internal Sparx Model

        2. Performing Model Review with SDC developers

        3. Refinements per how it is modeled in SDC Today

        4. Model for today or how it could be??? 

      6. Business Interaction  - No Activity; Tied to Root Hierarchy effort

    3. Infrastructure ( @Arun Gupta )

    4. Nf (@Kevin Scaggs )

    5. Ns (@guochuyi )

    6. Party (@Kevin Scaggs )

      1. Have started developing a Party Model - tied to license work

    7. Pnf (@Former user (Deleted) )

    8. Resource (@guochuyi )

    9. Service (@guochuyi )

      1. Make updates to WIKI, and then add into model later, or take over as editor (Kevin has no plans to work in Service presently)

      2. Kevin did delete duplicate "ServiceDescripter" Objects

      3. Chuyi to talk to Lin Meng about possibly deleting some of the diagrams in this submodel.

    10. Vnf ( @Former user (Deleted) )

      1. Compare of ONAP to ETSI 2.5.1

        1. Some conflicts with Chuyi's contribution

        2. Some updates to common

        3. QoS updates

        4. Virtual Link Descriptor to Common 

        5. Papyrus Bug resurfaced

  3. Modeling Tip and Tricks 

    1. Discussed adding a stereotype of reference, and then put in a reference (IFA011 v2.5.1)

      1. This can be useful to give credit to where this concept came from (TMF, MEF, ETSI, ....) 

  4. Next Meeting

    1. See if we can settle on handling of updates (see notes above)

    2. Possibly breaking out Common into some submodels