Versions Compared

Key

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

Date  

...

Note that a Waiting room has been added to the meeting room, the host will let you join once identified

Meeting Attendees

Michael Morris

Vasyl Razinkov

Krupa Nagabhushan

Former user (Deleted)

Former user (Deleted)

Anderson Ribeiro

Gervais-Martial Ngueko


Agenda & Minutes

Review open action items from last week

AgendaMinutes (Draft to be updated during call)
Slides

JIRA Updates

  • High priority defects
  • Open Reviews
  • Defects & tasks backlog
  • Current Release progress : H release
  • Others


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

  • Other High priority ticket to discuss ?

Open Reviews :

Important : for new features, please provide explanation of changes and API/UI/unit testing, it is also advised to present changes at SDC weekly


Defect & Tasks Backlog (no update this week):

 

Jira Legacy
serverSystem Jira
jqlQueryproject = "Service Design and Creation" AND labels = Documentation AND status != Closed
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
 

  • Use the AID (Architecture Integration DocumentSDC Data model also for new comers


Others:


3 new GR being reviewed for Istanbul and 1 BP :


  1. Promote to Global Requirement: CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES, SECCOM to provide recommendations

    Updates in progress :

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

  1. Promote to Global Requirement: CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR GOLD LEVEL, target is to reach silver level more info : CII Badging Program
  2. IPV4/V6 support : should be no issue for SDC (tested daily by Nokia Lab)
  3. Promote to Best Practice: LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA → use STDOUT as output for logs in Logback conf as a first step


2 new Best Practices approved by TSC for Jakarta:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-399

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-396



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


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 


Important Jira tasks we need to pick up


Long Term tasks

INCREASE SONAR Coverage and lower SONAR bugs

We've noticed a growth of SONAR issues and coverage is getting lower,

https://sonarcloud.io/dashboard?id=onap_sdc

Stats are computed only on Merged code, it would be good for contributors to :

1) Enable Sonar plugins in IDE try to fix issues before they get in

2) To reduce issues, we could try and run through module per module (divide and conquer approach)

3) other ideas ?

4) Coverage is back up to 55.3%

  • Reduce line of codes (unused code)
  • Increase testing
  • Use LomBok to cover getter setter
  • You can see where coverage per module in sonar views

Other long term tasks

  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2708
     Add assertions for unit tests  - #NewComers
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2812
     Refactor all usage of Eithers
    - Guilin R7, #NewComers
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySDC-2844
     JUnit 5 unit test  - on going for new UT



Security issues

Jira Legacy
serverSystem Jira
jqlQueryproject = OJSI and cf[10400] = OJSI-SDC and resolution != Done and resolution != "Not a Bug"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOJSI-94

This issue significantly impact SDC APIs, since SDC does not have password and has to defer request to portal/aaf. PORTAL provides credentials validation API so that SDC can check users - will see if we have time to do something about these.

Changes presented to SECCOM and they agreed on current progress.

Parking this topic until further updates.

Exemption was previously requested from SECCOM. Solution may cause big impact in sdc-wfd-fe.

 

Xue Gao have confirmed this significantly impacts SDC, and the changes must be studied and planned properly.

Added as a risk in the Istanbul release as we do not have resources to commit in fixing the issue: Istanbul Risks.



Intermittent Integration Tests

UI Tests  

Tooltip problem:


Unknown timeout exception: https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/sdc-integration-tests-master-verify-java/650/integration-tests/target/ExtentReport/UI/SDC_UI_Extent_Report.html.gz


Startup  

sdc-backend-init error:

https://jenkins.onap.org/job/sdc-integration-tests-master-verify-java/670/console

No Format
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.31.0:start (docker-start-for-it) on project sdc-integration-tests: I/O Error: [onap/sdc-backend-init:latest] "sdc-backend-init": Container stopped with exit code 0 unexpectedly after 541089 ms while waiting on log out 'Chef Client finished' -> [Help 1]



Build issues

 

NPM / YARN issue:

https://jenkins.onap.org/job/sdc-integration-tests-master-verify-java/671/console

No Format
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.8.0:install-node-and-yarn (install node and yarn) on project onboarding-fe: Could not extract the Node archive: Could not extract archive: '/home/jenkins/.m2/repository/com/github/eirslett/node/10.17.0/node-10.17.0-linux-x64.tar.gz': EOFException -> [Help 1]

 

Vasyl Razinkov has opened a ticket on LFN related to it: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22249

There is a work in progress to update Node/NPM dependencies (Vasyl Razinkov): 

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

 

Patchset merged in today, monitor result of patchset

 

New issue seen with maven version preventing all builds from succeeding. LF ticket created:

https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22401


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

...

 new wiki entry if you want to build a lab of your own : Deploy OOM and SDC (or ONAP) on a single VM with microk8s - Honolulu Setup


Recording

View file
namezoom_0.mp4
height250

Chat