Page History

...

• Agenda bashing:
  • PNF instance model
    • AAI feedback - not yet
• Model Proposals
  • license management - review comments
    • 1) have a seperate discussion on recording the approved classes (for information, we have readthedocs per release to document the approved classes)
      • the link of the readthedocs: https://docs.onap.org/en/elalto/submodules/modeling/modelspec.git/docs/index.html
        
      • AP: Xu will add a discussion issue for next week's IM call, and discuss how we could improve
    • 2) check root proposal to see the inheritance of the license classes
      • agreed, will update
    • 3) agree on the scope of the license, VNF/VNFD or broader (also relate to "software" definition in the descriptions)
      • current scope is only VNF
    • 4) clarify the usage of asset management system (which is outside ONAP) and relationship with the classes in the proposal
      • for further discussion
      • LicenseKeyInstance and EntitlementInstance will be experimental classes, attributes will be further reviewed (Michela suggest to remove the attributes)
    • 5) give descriptions to the relationship classes
    • 6) double check the SDC UI info with the current proposal to align the attributes definitions
    • 7) enlarge the scope to include "vendor" class (party proposal) and its super classes
      • will add vendor and its super classes to the proposal
    • 8) relationship between VNF/VNF instance and license needs further discussion: the proposed/as-built model may be different from what vendor thinks
    • 9) further updates for typos/missing diagrams/...
  • 5G RAN service model
  • allotted resource
• Modeling Process Discussion
  • use case team has started their work on the process: ONAP Use Case / Requirements Teams Process Way of Working (WoW)
    
  • start working on arc team involvement part
    • modeling subcommittee lead will contact arc PTL for a sync-up before M3