Date
Table of Contents |
---|
Meeting Logistics
Day | Time | Meeting ID | Zoom Link | Join by phone |
Monday | [sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00 | https://lists.onap.org/g/onap-meetings/calendar | See 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
see recording
Agenda & Minutes
Review open action items from last week
Agenda | Minutes (Draft to be updated during call) | Slides | ||||||||||||||||
JIRA Updates
| High priority defects for Guilin:
Open Reviews : oom reviews: [SDC] Support setting SDC-BE configuration at deployment time → Sylvain investigating Pod limits and timeouts → minor comments Gerrit REVIEW can proceed with auto test in verify job
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 Defect & Tasks Backlog :
Others:
Amir status : In progress, working on SNAKEYAML upgrade Any news ? will move further work to next release as we are approaching RC0 Amir is working through some logging issue with SNAKEYAML Plan on Branching Guilin after RC0 | |||||||||||||||||
Python upgrade from 2.7 to 3.8 in Guilin release | Discussion with Pawel Pawlak Michał Jagiełło Tasks 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) Closed, fix provided in integration test suite, now properly provisionning testsuite | |||||||||||||||||
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
→ 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
| |||||||||||||||||
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
10.12.5.145 aaf-onap-test.osaaf.org | |||||||||||||||||
Java 11 | Reflection was changes, need to know the business logic better to refactor - YamlToObjectConverter
Xue did WFD last week so all java containers are now upgraded Closing as now completed | |||||||||||||||||
Guilin requirements | M1 commitments reviewed with tSC → M1 is approved implementation in progress, Any progress update ? See M1 tracking table :
Testing in progress on Windriver lab Merged code of Sithara today, will release new containers when merge of Test code from auto test Review
Remaining items :
review container licenses and origin Non Functional progress :
M4 has been passed on Sept 17th, working through RC0, planning to do Integration tests and pairwise with Policy team New tickets raised by integration for gating check (SSL, root pods, limits, java&python version) → All submitted now Status of Pair wise testing : SDC Pair Wise Testing for Guilin Release Next week, team is going to work on E2E use case (VLB CDS and scale out) + release RC0 artifacts + branching of Guilin Optional: Amdocs/YoppWorks to work on Multi-Tenancy (Stretch Goal For Guilin) → did not get news about this Cucumber api ci - TBD Configuring UI tabs (R6 backlog) | |||||||||||||||||
Reviewing last week's action items | see below | |||||||||||||||||
Discuss Degug Environment | will spend some time after RC0 to work on documentation (it would be good to create a wiki describing how to debug etc..) | |||||||||||||||||
Healthcheck improvements | Some improvements submitted in integration repo https://gerrit.onap.org/r/c/testsuite/+/113356 | |||||||||||||||||
Q&A | If 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 |
Action Items ()
Java 11 Migration -Janusgraph issue with java11 → Seems OK now, closing, will re open if we find an issue
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
- Chris to add link to log details in wiki to these minutes →Done see above
- Chris to update link in wiki about calendar invite for SDC call → Done see : [sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00
- Bin to send an updated AID document for publish (including changes for Guilin)
Rocket Chat channel :
http://onap-integration.eastus.cloudapp.azure.com:3000/channel/sdc
...
10.12.6.10 - updated to 1.7.1 (STAGING latest) and installed most of ONAP components.