Date
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 |
Note that a Waiting room has been added to the meeting room, the host will let you join once identified
Meeting Attendees
TBD - see recording
Agenda & Minutes
Review open action items from last week
Agenda | Minutes (Draft to be updated during call) | Slides |
TBD | Add items (eg : Honolulu feature review) - review Release planning template with team Release planning : SDC R8 Release Planning | |
Call for Committers | Requesting active committers to apply for formal Committer's role Fill the template under : Committer Promotion Request for [SDC] Will review and request a vote from all current committers | |
JIRA Updates
| High priority defects for Honolulu:
Open Reviews : New features review / Bug fixes for H release Similarly for distribution client, should we already deliver a new version ? Note : SDC CSIT are disabled as tests are done within the SDC verify job, tests that imply only SDC and run on simulators should be run inside the verify job of each project The CSIT jobs are deprecated for SDC, it would be good to display testing results inside the the jenkins UI (Chris/Seb to check with Jess if feasible - still in progress) oom reviews: [SDC] Support setting SDC-BE configuration at deployment time → Cancelled Gerrit REVIEW can proceed with auto test in verify job, now accepting changes for Honolulu
Important : for new features, please provide explanation of changes and API/UI/unit testing, it is also advised to present changes at SDC weekly we have a plan to add SONAR test to the verify job, will work on this in the coming months Note : SONAR rules have changed (TS profile) and we've lost about 1% coverage, will work on increasing this in next release Defect & Tasks Backlog (no update this week):
Others:
Amir status : Contacted Amir to see if he still is engaged - he seems to be busy with other tasks Julien working on his Review Honolulu release in progress according to new release cadence process (should be less admin work) Release planning discussions happened last week, in short : Release is for First quarter next year link to release planning wiki : Release Planning: Honolulu M1 Passed on Thur 1/14, M2 is planned for 1/21 Important : Global Requirements VS Best practices GR = a requirement or rule that MUST BE applied to ALL code (old and new) BP = a requirement or rule that MUST BE applied on NEW code/NEW containers A GR must be a BP first before being adopted by TSC 3 BP have been approved for H release :
2 GR
Important note to committers and code contributors : please make sure these are followed or your contribution will not be merged | |
Automated Rolling Upgrade and Data Migration | No Update this week Support of automated upgrade from version X to version X+1 Needed for every change that breaks existing data validity : Have a strategy to handle data migration
→ Discuss further and create User stories along with Bell Canada, Amdocs, Tata communications Will need to prioritize VS Guilin Requirements → this may shift to next release due to low commitment Learn from SDNC experience; "Normatives" types: challenging | |
Important Jira tasks we need to pick up Long Term tasks | No Update this week
| |
Security - Guilin | Looking at these and this will significantly impact SDC APIs, since SDC does not have password it has to defer request to portal/aaf exception for this in Guilin requested , though PORTAL provided Credentials validation API so that SDC can check users - will see if we have time to do something about these OJSI tickets open on SDC Basic Auth setup introduced for SDC APIs by Xue, try to be non breaking to avoid failures, not perfect solution for now
| |
Reviewing last week's action items | see below | |
Q&A | If you have time, pay attention to SDC mailing list questions | |
Honolulu Requirements | New requirements for H release are now open, See : Honolulu Release Requirements and impact per components : Honolulu Impact View per Component M2 in progress Release planning : SDC R8 Release Planning Please plan to present your changes at SDC weekly 1 POC and 1 REQ without stories | |
Discuss SDC-2661 | Is this still needed ? Triggered by Jira comment to see if we should pursue this or not | |
Discuss Starting up SDC Onboarding UI locally | Discussed on how to start both UI parts sdc-fe and onboarding ui in a local setup in IDE (so outside of running them in containers)
Check if someone can have a look to investigate further Ilana has proposed a patch to fix onboarding proxy |
Action Items ()
OOM review → in progress, testing locally, provided fixes, root cause is configuration.yaml issues (don't know yet exactly where)→ CANCELLED- Chris to check with Xue if she can help on SDC UI local - done but no resolution yet, Chris to try and contact amdocs for more info - running REAKT ui locally of onboarding → Done, Ilana has proposed a patch
Rocket Chat channel :
http://onap-integration.eastus.cloudapp.azure.com:3000/channel/sdc
IMPORTANT NOTE, Rchat will be decommissioned on 1/31, pls use LF Slack
SDC Dev lab on Windriver :
ssh ubuntu@10.12.6.10 (with onap key)
10.12.6.10 - LAb is installed with Guilin