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
TBD

Add items (eg : Honolulu feature review)

Improvement to distribution client

migrate to java11, upgrade dependencies and junit5 upgrade, notifications improvements,

Jira tracking.


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)


oom reviews:

[SDC] Support setting SDC-BE configuration at deployment time → Still in Progress?  was off for a while not sure about status

investigating locally, problem is related to secrets mapping, last gating run shows secrets are not properly translated (CS INIT job failing)

Vasyl noticed that changing some config to http-only makes the fix work, suspect a mismatch in config mapping - have a bit more time to look at it this week

https://gerrit.onap.org/r/c/oom/+/107976


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 :

 

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 :

In progress, working on SNAKEYAML upgrade, anyone can look at his proposal (see gerrit review WIP)

current update : we got two tests failing after the update, seems the behavior of the parser has changed

Proposing to Amir to push his code as a gerrit review (even if failing) so that community can see & help

Vasyl found the issue and provided comment in Gerrit review, waiting for Amir to comment


Guilin SignOff on Dec 3rd → done


New ONAP release plan :

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



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,

Will implement basicAuth as many other components are doing right now Xue working on it,



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


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

  • Chris to contact Sylvain/oom team for the pending OOM review → in progress, testing locally, provided fixes
    • Still issues but see item in agenda, progressing, some tests are failing and are related to configuration settings


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 - updated to  1.7.3(STAGING latest) and installed most of ONAP components.


IMPORTANT NOTE :

most of AT&T committers will start taking their vacation for EOY, expect low/delayed responses starting from end of this week until new year

Call cancelled on 12/21 and 12/28


Recording


zoom_0.mp4

Chat



1 Comment

  1. Hi team, I got one question about adding customed dataType into the final generated CSAR.

    1. SDC-FE is able to edit my customed nodes because during sdc-backend & sdc-backend-init image building, maven copy datatypes.yml into the image.
    2. Now SO downloaded distributed CSAR, and recognise my customed datatype invalid. Maybe it is caused by data.yml contains the same as usual?

    For packing my customed datatypes into the data.yml in the final CSAR, where should I edit?