Date
...
| Agenda | Minutes (Draft to be updated during call) | Slides | ||||||||||||||||||||||||||||||
High Priority Bugs | High priority defects :
| |||||||||||||||||||||||||||||||
| Open review | ||||||||||||||||||||||||||||||||
| Istanbul release | Istanbul release planning schedule here: Release Planning: Istanbul M3 (functional code freeze) on August 26th. All JIRA issues with 'High' or 'Highest' priority need to be resolved
Inactive old issues with 'High' or 'Highest' priority to be reduced in priority. If anybody feels any of these issues should be kept as high or highest priority then please raise a discussion on it Code coverage at 55.6 %
Some 'High' or 'Highest' priority issues resolved since last week. The following issues that will be reduced in priority:
Code coverage at 55.5 %
M3 postponed to Thursday 2nd Sept No change in rest of the rest of the release schedule
M3 passed last Thursday 2nd Sept, no more functional content accepted in Istanbul
M4 planned for this Thursday 16th Sept. Releasing the docker images delayed by failure in https://jenkins.onap.org/view/docker/job/sdc-maven-docker-stage-master/, need to update version of maven from 3.5 to 3.6
M4 passed by TSC last Thursday. Issue seen in gating with importing VSPs using backend REST API. Fix implemented, to be released to gating
Gating results look good with latest release 1.9.3
Not merged in yet to OOM, but latest gating shows 100% on health check and smoke tests and review has received +2. RC is this Thursday 14th October. All stories, epics, tasks, and subtasks delivered in Istanbul should be closed. All open issues to be moved to Jakarta release | |||||||||||||||||||||||||||||||
| SDC performance issue | During H release Stability testing for SDC, it was noticed that performance decreases over time, up to the point where onboarding is not successful Not had time to investigate logs yet but saw some exceptions happening Test details and logs can be found here :
Cassandra configuration changes in stability tests resulted in significant improvement with success rate in excess of 90%. Remaining failures are likely to be due to timing issues Duration per request increases as DB becomes more loaded. Patchset to be pushed with new configuration and to expose configuration through helm charts to enable tunning where required.
Review push for exposing the configuration https://gerrit.onap.org/r/c/sdc/+/122516
SDC changed merged. OOM change in progress
OOM change pushed, waiting on SDC release
SDC release to be done at M3 on Thursday
M3 postponed last week so release not done, plan to release at M3 this Thursday instead, but if needed earlier let PTL know
Release to be done when issue observed in deploying is resolved | |||||||||||||||||||||||||||||||
| Jakarta Release timeplan | Milestone date approved by TSC: | |||||||||||||||||||||||||||||||
| 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 | |||||||||||||||||||||||||||||||
| Q&A | If you have time, pay attention to SDC mailing list and Slack channel questions
Two issues raised by Bhagya:
Jira issues to be created and team will provide support |
...