Date  

Meeting Logistics

DayTimeMeeting IDZoom LinkJoin by phone
Monday[sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00https://lists.onap.org/g/onap-meetings/calendarSee 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

AgendaMinutes (Draft to be updated during call)
Slides
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
  • Open Reviews
  • Defects & tasks backlog
  • Others


High priority defects for Honolulu:

 

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

  • Other High priority ticket to discuss ?
  • SDC 1.8.0 is out and but not yet merged on oom master
  • Moving to 1.8.1 ?
  • Yes will proceed to create 1.8.1 docker

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:

No review in progress right now


Gerrit REVIEW can proceed with auto test in verify job, now accepting changes for Honolulu

  • Reminder of merge conditions : Verify must pass AND tests must be provided for new features (SONAR metrics are important but can only be checked AFTER code is merged)

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):

 

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

 

  • Use the AID (Architecture integration documentSDC Data model also for new comers


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




3 BP have been approved for H release :

  • up-to-date new dependencies (not transitive) - can contact seccom for guidance
  • Helm V3 (mostly for OOM)
  • CII badging improvements (use good crypto)

2 GR

  • no more use of python2 (deprecated) -#GR
  • java 11 -# 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 release (parking topic for later)


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

  • Create a wiki page, details for every feature and its impact on data for migration / schema changes -  check the wiki page: Upgrade plan
    • Feature X: All services metadata must have new property Y
  • Implementing a "task" for migrating data accordingly.
    • Example: asdctool mig2002

SDC-3155 - Getting issue details... STATUS Epic created

→ 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

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 :

  • Reduce line of codes (unused code)
  • Increase testing
  • Use LomBok to cover getter setter


Other long term tasks

  • SDC-2708 Add assertions for unit tests  - #NewComers
  • SDC-2812Refactor all usage of Eithers - Guilin R7, #NewComers
  • SDC-2844 JUnit 5 unit test  - on going for new UT
  • SDC-3108 - Getting issue details... STATUS Migrate all TestNG tests to Junit5 , #NewComers
  • SDC-2688Upgrade Selenium - Guilin R7, André



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

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh


Reviewing last week's action items

see below


Q&AIf 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, was postponed las week


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

SDC-2661 - Getting issue details... STATUS

Is this still needed ? Triggered by Jira comment to see if we should pursue this or not

Moved to Committer's meeting


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)

  • agreed that this was not the way the build is designed
  • it is possible to start them up but there is some complex proxy configuration to change in order for the UI to properly communicate 2 ways with BackEnd

Check if someone can have a look to investigate further

Ilana has proposed a patch to fix onboarding proxy


Fix is merged, it is not perfect but apparently allowed to progress

Can we close ?

No objection to close



LF DDF developer event

one item for SDC distribution client from Nokia team :


ONAP / 3GPP Harmonization ves-openapi-manager & SDC distribution monitoring enhancements on Wed Feb 3 2021


Schedule : https://teamup.com/ksgw6qzqcmg9zbzsfq



Action Items ()

  • None


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


Recording

zoom_0.mp4


Chat