Versions Compared

Key

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

Date  

...

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/, 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

 

1.9.3 merged in.

New oom review opened with 1.9.4 with bug fixes

RC decision postponed by TSC last Thurdsay, to be evaluated after PTL meeting today

 

1.9.4 merged in to OOM

Sign-off postponed to Nov 15th

 

1.9.5 merged in OOM

Sign-off to be discussed at PTL meeting later today

 

Istanbul sign-off approved


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 :

INT-1912 - SDC Stability test: success rate drops after ~ 500 onboarding IN PROGRESS

 

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

 

Should be possible to progress OOM review with version SDC 1.9.3 

 

OOM review in progress

 

OOM review merged in, however new bug raised on Istabul (SDC-3733)

 

Fix merged in for SDC-3773 and 1.9.5 merged in OOM. Stability tests are being re-run

 

Stability tests result looks good with 1.9.5, overall success rate 92%. Success rate in line with Honolulu and tests executed much faster (1440 in 24hrs up from ~600)


Jakarta Release timeplan

 

M1 (Global requirement freeze) scheduled for 2nd December

Release Planning: Jakarta


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

Jakarta Release Requirements

 

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


Build issue

Unit tests started failing systematically last week on Jenkins with ApplicationContext error (

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3757
). @Ignored the affected test cases to enable reviews to proceed and created issue to investigate a fix (
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-3758
)

 

Code in review


Q&A



...