Date  

Meeting Logistics

DayTimeMeeting IDZoom LinkJoin by phone
Monday[sdc] Team ONAP4, Mon UTC 11:00 / China 19:00 / Eastern 6:00 / Pacific 03:0091998850070https://zoom.us/j/91998850070

US: +16699006833,,826152979# or +16465588656,,826152979# Or Telephone: US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 826 152 979 International numbers available: https://zoom.us/u/aclJhy4bl7

Meeting Attendees

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
  • Others


High priority defects for Guilin:

 

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

  • SDC-3216
    • Work can be huge to refactor, discuss with team on how to handle this, can it fit in G release ? Considering time frame will probably defer
    • Defered to next release (Guilin Maintenance
  • CSIT status ?
    • document output.xml issue - lower priority, sometimes output of tests is failing, marking job as red
    • Will deprecate CSIT jobs, now running in verify job
  • SDC-3104 → Xue is investigating, patch merged
  • SO-3119 : responded in JIRA, issue is due to lack of resource in previous release, Xue provided info on how to fix:  SDC-3228 in progress
  • Other High priority ticket to discuss ?

Open Reviews :

As approved by TSC and after waiting grace period :

DCAE-DS repositories are ARCHIVED : project discontinued

Will remove from oom charts and plugin configuration, will revisit integration testing to remove any

Test topology review : organize a session tomorrow to discuss it

oom reviews:

  • onboard plugin into main SDC container

Gerrit REVIEW can proceed with auto test in verify job

  • 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


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:

Ashish Mentoriship is completed

Amir status :

In progress, working on SNAKEYAML upgrade


Python upgrade from 2.7 to 3.8 in Guilin release

Discussion with Paweł Pawlak Michał Jagiełło

Tasks status :

  • Import Normative script -  user-7f92d  submitted, waiting for review. Added retry mechanism to avoid failures.
    • Upgrade normatives - review this flow offline   → Can this be closed ?
  • Tosca-lab (https://git.onap.org/sdc/dcae-d/tosca-lab/tree/) - deprecated DCAE-MOD project replaces DCAE-DS
  • backend-init scripts: consumers, users, health - submitted, waiting for review → can be closed ?
  • cs-init scripts → Can this be closed ?
  • Different UIs npm packages that could use Python - Ilana: supports Python 3 already according to docs
  • sdc_base-python upgraded

SDC-3094 - Getting issue details... STATUS


WORK COMPLETED

one oom change still to be done, but all ok on SDC side

Validated OOM change on 10.12.6.10, waiting OOM team merge to CLOSE

 https://gerrit.onap.org/r/c/oom/+/111190 is still opened, issue on distribution ?


Yes SDC-2822 has introduced a new parameter in Entitlement pools (Type), this parameter is mandatory and fails auto testing since it was not there before

Will introduce a default value for this release (no time to create a new V2 API)

Note : found out that this is very hard to debug, chef is obfuscating logs and it is also hard to determine reason for error, will need to revisit this in future releases

review is rebased,  and Fix implemented and merge(default value in API), will update to container 1.7.1 once released (this week hopefully)



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

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

10.12.5.145  aaf-onap-test.osaaf.org


Java 11

Reflection was changes, need to know the business logic better to refactor - YamlToObjectConverter  SDC-3080 - Getting issue details... STATUS


It was detected that JanusGraph does not support JAVA 11 (due to one of its dependency not supporting it)

Chris created an exception request for G release since we don't have time/resources to replace JanusGraph

  Seb was able to make it work, but keeping item open in case we need to rollback due to issues.


SDC-BE, SDC-FE, ONBOARDING-BE are upgraded to Java11, no issues in tests, was able to deploy on Windriver using OOM



Guilin requirements

M1 commitments reviewed with tSC → M1 is approved implementation in progress, Any progress update ?

See M1 tracking table :

SDC R7 M1 Release Planning

    Testing in progress on Windriver lab

  • ETSI changes, most of reviews are merged ? any important pending ? before we release this week ?
  • Test Topology Auto Design new reviews are in progress, would be good to get understanding of the change

Remaining items :

WFD → java 11

Disable DCAE-D charts

review container licenses and origin


Non Functional progress :

OOM use of Certinitializer, code is merged on oom


M4 has been pushed back to Sept 17th,  JIRA updates in progress

New tickets raised by integration for gating check (SSL, root pods, limits, java&python version) → chris to check


Optional:

Amdocs/YoppWorks to work on Multi-Tenancy (Stretch Goal For Guilin) → did not get news about this

Cucumber api ci - TBD

New Profile Feature

SDC Type Management

Configuring UI tabs (R6 backlog)

i
Reviewing last week's action items

see below


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


Action Items ()

  • Java 11 Migration - 
    • Janusgraph issue with java11
    • only WFD to update, rest seems fine, will keep monitoring
  • Christophe Closset  ongoing, need to validate if change is impacting on other components (distribution),
    • found issue with SDC-2822 intoducing breaking changes on ENTITLEMENT POOLS (new mandatory TYPE)
    • More to come after running PairWise testing ?
    • Fix merged, need to go through gating when 1.7.1 containers are released
  • An idea came during the call to organize specific call with the developper to review his PR, especially for big PR's, so it makes life easier on committers who needs to review it. this might help speed up PR's reviews.
    • Please contact ONAP-SDC mailing list or mail to committers to set up review session if needed


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 JAVA11 containers and 1.7.1 (STAGING latest)

Recording


Chat