Date
| Table of Contents |
|---|
Meeting Logistics
| Day | Time | Meeting ID | Zoom Link | Join by phone |
| Monday | [sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00 | https://lists.onap.org/g/onap-meetings/calendar | See Groups.io calendar invite | See Groups.io Calendar Invite |
Meeting Attendees
Francisco Javier Paradela Vila (Unlicensed)
...
Agenda & Minutes
Review open action items from last week
| Agenda | Minutes (Draft to be updated during call) | Slides | ||||||||||||||||||||||||||||
High Priority Bugs | High priority defects :
| |||||||||||||||||||||||||||||
| Open review | ||||||||||||||||||||||||||||||
| Jakarta Release timeplan |
M1 (Global requirement freeze) scheduled for 2nd December
Tasks for M1:
M1 postponed by 1 week from 2nd to 9th Dec. Other milestones unaffected We should plan to release more often in Jakarta to move towards a more CI way of working.
M1 approved by TSC
M2 milestone scheduled for 27th January
First delivery for Jakarta (1.10.0) built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/126602). Content can be seen here: https://docs.onap.org/projects/onap-sdc/en/latest/release-notes.html#version-1-10-0 Still in review in OOM 1.10.1 built and submitted to OOM (https://gerrit.onap.org/r/c/oom/+/127003) M2 passed last Thursday 3rd Feb. Next milestone is M3 on 3rd March
M3 planned for Thursday week 3rd March - last date for merging in functional changes for Jakarta. Code Coverage currently at 55.6% - must maintain above 55%
1.10.1 merged in to OOM M3 this Thursday 3rd Mar
M3 approved last Thursday. No new functionality can be added to Jakarta, only big fixes, documentation etc. M4 planned for 24th March | |||||||||||||||||||||||||||||
| Jakarta Impacts | Portal is in unmaintained state in Istanbul and is proposed to be removed in Jakarta, need to consider how user authentication for SDC UI to be performed if portal is removed
Proposed new global requirement: REQ-441 ONAP application log to stdout and stderr Proposed new best practice: Standardized Logging Fields, see Jakarta Best Practice Proposal for Standardized Logging Fields - v2
Previous best practice
Proposed impact for Jakarta:
Concerns raised at modeling subcommittee on ASD POC, was discussed at TSC last Thursday, to be further discussed at modeling subcomittee today to see if agreement can be reached on way forward
Modeling subcommittee chair referred ASD model to TSC for decision. TSC vote in-conclusive, Kenny Paul to publish outcome once voting rules clarified
Kenny Paul sent email last week to onap-tsc mailing list, further discussions at TSC last Thursday
ASD and delete functionality carried forward to Kohn |
Action Items
Slack Channel: #SDC on LFN ONAP.org Slack instance (onapproject.slack.com)
Recording
| View file | ||||
|---|---|---|---|---|
|