...
| Duration | Agenda Item | Requested by | Notes / Links | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
START RECORDING: | |||||||||||||||||||||||||||||
| 15 | Co-chair
| 1) Email Polls 2) Non-MANO Artifacts (Fei Zhang (Ericsson) ) Come back until end of Frankfurt release)
Slides describing the proposal available for comments: ONAP Non-MANO Artifacts Set Identifiers_PA3.pptx (Michela Bevilacqua) Action item: Michela Bevilacqua will connect with VNFRQS PTL to build lifetime readthedoc. Jira is created for VNFRQS. UPDATE: Updated Wiki Page, JIRA to update requirements. Ready for ETSI to review. For all non-MANO artifacts. Action: Initiated ETSI review. Awaiting response from ETSI 3) Modeling current activity status. Provide the dash board of current status and how to involve: See: Modeling Current Activity Status 4) How to proceed future DM discussion?
5) R7 Guilin Architecture Review (template) - functional requirements Added information flow elements to the Arch Template 6) Review procedure: 6.1: ONAP R7 Modeling High Level Requirements Category 1 : R1/R2: Fred: Whether ETSI NFV 2.7.1 review next week will be decided by next Monday. Category 1 : R3 will contact about how to proceed. Category 1: R4 Chuyi will detail the requirement Category 2: Ben will handle them firstly , will contact with chairs once he need the help Category 5: Container model documented, encourage the contribution. 6.2: Use case guidance from Modeling subcommittee Action item: encourage to review and comment Benjam will help to arrange modeling present in use case group on May 13th. 7) Proposal on how to describe and document relationships in ONAP Info Model Jacqueline Beaulac [Ericsson] Michela Bevilacqua
8) June virtual LFN Developer and Testing Forum event, deadline June 3rd: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297 June 22-25 Deadline for topics June 3 | |||||||||||||||||||||||||||
| A5 | CNF Modeling | Action review: ACTION: Fred will create R7 requirement. Done Next step: CNF IM proposal. | |||||||||||||||||||||||||||
| 10 | Review use case process update | Hui Deng | Use case guidance from Modeling subcommittee Proposed ONAP Release Process Updates for Information and Data Modeling Feedback last week in use case and TSC meeting | ||||||||||||||||||||||||||
| 5 |
| Resource IM | |||||||||||||||||||||||||||
| 5 |
| Service IM | |||||||||||||||||||||||||||
| 5 |
| AAI Reverse Engineering status | |||||||||||||||||||||||||||
| 15 | GeoLocation Model Update PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion | ||||||||||||||||||||||||||||
| 5 | API Documentation | Developing ONAP API Documentation Discussed Proposed Phased activities: (e.g., Minimum 1, 2, & 3 Guilin; 4 & 5 Stretch goals) 1. All components should place externally facing API definitions (e.g. Swagger) in a common path within their Gerrit/Git a.Suggested Path: <Component>/docs/api/swagger/ 2.Apply ReDoc to Swagger and place HTML in Readthedocs for the release. 3.Apply Minimum (Phase 1+) swagger guidelines a.Use common insert for Info section template 4.Use embedded markdown for conceptual documentation 5.Apply full swagger guidelines. Proposed ACTION: Created non-functional requirements for Guilin release:
Progress: Added Non-functional requirements in wiki Created JIRAs within documentation project: Epic: https://jira.onap.org/browse/DOC-608 User Story: https://jira.onap.org/browse/DOC-609 User Story: https://jira.onap.org/browse/DOC-610 User Story: https://jira.onap.org/browse/DOC-611 Scheduled to review with Reviewed and Endorsed by the Requirements Subcommittee on May 25th. see: May 25th, 2020 | |||||||||||||||||||||||||||
| 5 | Container model | 0310： Introduction of K8S module in MultiVIM project 0324： Invite K8S PoC CNF Taskforce takes place after Thursday's TSC: CNF-Taskforce Recordings 0421: Container Modeling at April Technical Event | |||||||||||||||||||||||||||
| Modeling and Use Cases | Proposed ONAP Release Process Updates for Information and Data Modeling Discuss M3 process Proposed Functional Template for Use Cases Need to begin using these Functional Templates for each Use Case. Possibly merge into a single template. Benjamin Cheungis working with the Architecture Subcommittee (Use Case realization effort) to introduce. See: ONAP Use Case / Requirements Teams Process Way of Working (WoW) May 13th call with Use Case teams. April 16th 5G call will also discuss. (11:00 eastern US) https://zoom.us/j/478423919 | ||||||||||||||||||||||||||||
...