Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AgendaMinutes (Draft to be updated during call)
Slides

High Priority Bugs


High priority defects :

 

Jira Legacy
serverSystem Jira
jqlQueryproject = "Service Design and Creation" AND issuetype = Bug AND status not in (closed) AND priority in (High, Highest) ORDER BY priority DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


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:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2716
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2325
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-1488
. 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.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/


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 :

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-1912

 

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.

Test results: https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/2021-06/28_21-34/stability/results_sdc_5_24h/onaptests_bench.html

 

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


Intermittent distribution failures in Gating

Intermittent failures in distribution causing Gating to fail. Was previously investigated, what is the current status?


Following issue reported during onboarding which can lead to distribution failures but the issue is in the onboarding: 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3508

Suspected to be caused by consistency issue between cassandra nodes. Changes to consistent settings in cassandra has been suggested by Orange that may resolve this issue

 

Priority likely to be lowered, failures due to concurrent requests to cassandra 


Q&AIf you have time, pay attention to SDC mailing list and Slack channel questions

...