Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
https://lf-onap.atlassian.net/browse/CPS-1956 found while testing above. @Sourabh Sourabh is able to reproduce and likely cause already identified. Preliminary fix expected today. But need to ensure our testware is improved as this shouldn't have slipped trough!
@Waqas Ikram (Unlicensed) need more detailed study regarding TBAC (@Kolawole Adebisi-Adeolokun has been in touch with @kieran mccarthy regarding this and it should be available soon. Waqas also request a presentation by the study author if possible.
@Lee Anjella Macabuhay present latest version of our automatic performance (daily) plots. The last issues have been fixed. The variation in the plots is mainly caused by environmental issues when running at daytime. According to @Daniel Hanrahan the results form the 2am run are most stable. Lee Anjella will change the trigger to time based so the data wil only include the 2am runs. @Daniel Hanrahan is fixing the limits based on teh latest results and wil also work on choosing a small set of representative test to plot and examin on a daily basis.
CPS Sonar reported 10 new issues. Most of these seem to be caused by the upgrade to Java17. @Priyank Maheshwari will address those and @Halil Cakal will address the issue related to his recent commit
https://lf-onap.atlassian.net/browse/CPS-1789@Gerard Nugent is close to delivering the Springboot 3.0 upgrade, this wil required developers to use a Java17 JDK when building locally! Newer version cause build problems (for spotBugs mvn plugin). Gerard wil notify with details when it is ready
@Gerard Nugent agreed to push the SpringBoot 3 changes today for review and merge soon hopefully. The failign test can temporary be ignore and the Code coverage adjusted as needed to follow up in separate commit(s)
https://lf-onap.atlassian.net/browse/CPS-1784 - a question came up on consistency of the ordering of records returned when using the descendants option. @Rudrangi Anupriya to check and confirm the consistency.
scenario 4 that a DMI reports some cm handles are 'pending' is NOT a valid scenario; a DMI can only reject or accept cm handles. Need a code update to fix this. @Halil Cakal to fis this
demo still use incorrect datastore but code fix is pending in review @Toine Siebelink confirms
outcome from dmi to ncmp is inefficient if many (all) cm handles are not accepted for the same reason. The reason wil be repeated in the json for each cm handle We could use a similar grouping schema as is used when forward outcome from ncmp to client. @Priyank Maheshwari to decide if this will be changed now.
The demo could be approved to show that different responses from DMI are grouped per message, the current demo uses only only one error message 3 times it would be betert to use different message, one of the at last occurring twice to show the grouping when status details are forwarded to client...
scenario 3 is also based on an actual response from dmi saying all are pending this is not valid @Halil Cakal will prepare a new demo where the 'pending' state wil occur and a message set by NCMP about te pending state...
AOB
Holiday plans. @Toine Siebelink will discuss with @Priyank Maheshwari
@Gerard Nugent DMI Being upgraded to Java 17 too now (some build issues)
CPS/NCMP Code Coverage now up over 98% however recent code is still missing coverage for error scenarios. It remains the responsibility for the whole team to double-check their own new code for coverage.
ONP Release planning is on hold as the impact of ONAP 'disaggregation' is being analyzed and the process are updated to cater for that.
