...
- Agenda bashing
- Model Proposals
- allotted resource
- the plan is to finish the network slicing discussion in service model first, then discuss allotted resource
- VES model update
- wiki: VES 7.2 (updated on Oct. 20)
- model updates:
- event diagram change: add StndDefined
- highlights the changes: blue bold text show changes, show inheritance in attribute names
- gendoc template discussion:
- 2 solutions: 1) only show attributes dedicately defined for each class; 2) show the class each attribute first defined/introduced
- the audience prefer the 2nd solution
- Damian ask if we want to see the full inheritance path
- comment:
- stndDefinedNamespace should be only present in the StndDefined class, but is currently defined in VesEvent
- the reason for the design is to optimize the performance
- stndDefinedNamespace should be only present in the StndDefined class, but is currently defined in VesEvent
- AP:
- ask for poll on modeling subcommittee call
- Xu will present the gendoc template change next call
- CPS model
- no updates
- 5G service
- no updates
- ETSI support for CNF model
- ETSI IFA011 v3.3.1 & v4.1.1 Changes to support OsContainer based VNFs
- commentcomments from last call:
- backward compatibility consideration, support v2.6.1 (implemented in Dublin), which versions are to support is FFS
- for package upgrade, there could be limitations for the lowest version that can be upgraded upgraded
- conclusion: will support in DM design, to identify the version of the package and support (slightly) different version of packages onboarding
- present 2nd part (container support):
- new class OsContainerDesc (represents container)
- new type MciopProfile (represents Helm Charts)
- new class VirtualCpd (represents a K8S service)
- AP for updates:
- Fred to add an association between OsContainerDesc and Vdu, and also a comment stating Vdu can only compose of OsContainerDesc or ComputeDesc at one time
- fix typo in VersionSelector class
- allotted resource
- Modeling Documentation
- R6 readthedocs review:
- gendoc template improvement: ONAP Information Model - Gendoc Examples
- AP: simplify the sterotypes for the associations, Xu will help summarize the status and trigger the discussion
- add relationship documentation to the UML guideline:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key ONAPMODEL-28 - UML principle wiki page:
- Principle and Guideline for Information Model Proposal Using Papyrus (Draft)
- https://wiki.onap.org/pages/viewpage.action?pageId=84669384
- reviewed, no comments for now
- will continue working on the pages
- UML principle wiki page:
- R6 readthedocs review: