ONAP R6 Resource IM Call 2019-11-11
General Information:
Date and Time: 2019, Nov 11th, 10pm~11pm Beijing Time, 9am~10am US Eastern
Meeting Room: https://zoom.us/j/645982535
Meeting Recording: zoom_0.mp4
Meeting Chat Log:
Agenda:
Agenda bashing - 5 minutes
items for checking:
modeling glossary: gendoc templates check
ves spec: IM update check
License model proposal discussion - Kevin, 30 minutes
Modeling Process discussion - Ben, 20 minutes
Material:
Proposed ONAP Release Process Updates for Information and Data Modeling
AttServiceSpecification-VesEventListener-v7.1.1 - DRAFT.docx
Minutes:
Agenda bashing:
modeling glossary:
Kevin has started working on the gendoc templates
will first focus on class, datatypes and enumerations; would discuss whether to add attributes afterwards
ves spec update:
7.1.1 update hasn't been finalized
current updates only have a minor affect on UML: modify association names, which is kind of "invisible" from the diagrams
would wait for spec to finalize first, then have a review for the updates on the UML diagram; could go for a quick review and approval if only association names are changed
Discussed items:
License model proposal:
the main problem is besides the SDC implementation, R6 also has a discussion for license use case, and the two are not aligned
Michela suggest to start with a discussion of use case before discussing models, to understand better how AT&T would like to have for license management in ONAP
Not all models in the current proposal are relevant for Ericsson and Nokia's use case, e.g., number of instances
what's the purpose of IM
document the implementation
design a common model that would be agreed by the community, i.e., drive future usage
vendor may prefer to have their own license management entity
next steps:
get service provider involvement
have a dedicate meeting to present E&N's proposal (no regular meeting for now)
utilize use case subcommittee calls for discussion, reach out to more service providers (like Orange); Timo could ask Alla
topics for modeling subcommittee:
use of stereotypes
different review process for models reflecting the implementation vs model for future design
Modeling Process:
no time for discussion
continue next week