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
TBDAdd items (eg : Honolulu feature review)

JIRA Updates

  • High priority defects
  • Open Reviews
  • Defects & tasks backlog
  • Others


High priority defects for Guilin:

 

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

  • Other High priority ticket to discuss ?
  • SDC 1.7.3 is out and merged on master / Guilin, fixing most issues

Open Reviews :


New features review / Bug fixes for H release

Should we release 1.8.0 ? a couple of fixes/features have been merged

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:

[SDC] Support setting SDC-BE configuration at deployment time → Still in Progress

Investigated last week, error seems to be in configuration.yaml, comparing files from good deployment VS new setup shows many difference, still trying to get which one is failing but the backend seems to not be properly configured and is responding 500 when onboarding. (Note that this change overwrites what the Chef deployment is doing at init)



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


New ONAP release plan :Guilin SignOff on Dec 3rd

Honolulu release in progress according to new release cadence process (should be less admin work)

Release planning discussions happened last week, in short : Release is for First quarter next year

link to release planning wiki : Release Planning: Honolulu


Important : Global Requirements VS Best practices

GR = a requirement or rule that MUST BE applied to ALL code (old and new)

BP = a requirement or rule that MUST BE applied on NEW code/NEW containers


A GR must be a BP first before being adopted by TSC


5 BP have been approved for H release :

  • no more use of python2 (deprecated)
  • java 11
  • up-to-date new dependencies (not transitive) - can contact seccom for guidance
  • Helm V3 (mostly for OOM)
  • CII badging improvements (use good crypto)

TSC 2020-12-10


Important note to committers and code contributors : please make sure these are followed or your contribution will not be merged

It is not clear how/if any of these will be promoted to GR in H release



Automated Rolling Upgrade and Data Migration

No Update this week


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

No Update this week, most tickets defered to next release

  • Aligning SDC dependencies -  high priority → tracked under Guilin Reqs
  • 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


In progress, discussions with Portal PTL, SDC does not have a proper API user auth system


Need to investigate these for H

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


Will create release planning template details, tracking stories and EPIC + committments

M1 Jira tasks have been created


Please plan to present your changes at SDC weekly (I'm planning to cancel SDC weekly on 12/21 and 12/28)


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



Action Items ()

  • OOM review → in progress, testing locally, provided fixes, root cause is configuration.yaml issues (don't know yet exactly where)


Rocket Chat channel :

http://onap-integration.eastus.cloudapp.azure.com:3000/channel/sdc


SDC Dev lab on Windriver :

ssh ubuntu@10.12.6.10 (with onap key)

10.12.6.10 - LAb is installed with Guilin


Logistics :

Next week call is cancelled (the week after as well)

Next call planned on JAn 4th


Most of AT&T committers will be off in the coming weeks due to long pending holidays


Happy New year & Merry Xmas (stay safe!)



Recording


zoom_0.mp4

Chat