SO Weekly Meeting 2020-03-11
Topics:
SO needs to update M4 score, Frankfurt Release Requirements, 2: Frankfurt Release Integration Testing Status
Project Status in Frankfurt Release
Meeting recording:
Review
ARC Service Orchestrator Component Description - Frankfurt
Code Freeze : 2nd March the final.
Requirements | M1 committed Requirement details | M4 preparedness Status |
Risk on completing by Feb, decision point API has dependency that is not yet resolved. Backup plan: The existing flow is intact and we will switch back to the existing code till the new changes are merged. For F release we will continue with what we have. For F release looks like the backup plan would be defaulted forPNF Config Assign, Config Deploy. This functional aspects would be checked in parallel and would be included in the master branch. 11-03: Testing is in progress and the master release is being verified, found a new error in the Workflow executor related to the inventory "No PNF found" investigating further. This is a blocking issue for the PNF flow to be complete. need to verify with the new AAI and the input params. | ||
Need to revisit based on the badging demands | ||
SO supports ETSI SOL005 Alignment of its interfaces with NFVO | Expected to finish code review by next week. Yet to start Module level testing. Need to rebase the code and provide a new commit including all the related changes, ETA this week. Code Merged to the master and would be cut to the F branch, fine tuning is requried to increase the testing. The code is in the adaptation and would not impact the key flows.
11-03: Standalone testing is in progress, need to perform the integration testing on the windriver lab. Testing will happen with VFC. | |
Multi-domain Optical Network Service Orchestration Support in SO | This week expected the code review. Module level is in progress. So code is submitted for review. Need to re-submit the code the current changes seems to have issues and bring additional complexity. Cant be included in the F release branch, so will try take it as PoC and after review include in the master for the next release. XinMiao agrees to this approach.
11-03: Scope is reduced to bare minimal , there is no dependency with other modules of ONAP (SDC, AAI and OOF). There will be no optimization as the selection of the best possible for now. This will be the basic functional feature provided for the F release, will be extended further to the expected feature in the G release. To ensure the existing functionality not to be broken and verify in the CMCC (CCVPN) , Swisscom (BBS), Windriver (Integration) and the Orange (MDO) labs. To work wit the Usecase leaders to ensure there is no impact. | |
SO-2428: SO changes merged.
11-03: Demo ready. | ||
No risk, code by this week, testing to be completed. For F release we noticed to have some non-functional issues, working on the alternatives, need to check if this could be moved to the ESTI catalog manager for G release. Dependency on the SDC for the ETSI type if possible.
11:03: ready for the Integration testing. | ||
working on OOF integration part, Final integration testing of OOF. This week the coding is targeted. Testing will continue next week, have dependency on OOF. AAI 1.6.4 is released and unblockd for the code to checked in , would be dne by EOD today. UT is in progress and expected to be completed by next week. Testing would be conducted in the CMCC and windriver lab with the simulator in place. 11-03: All changes are merged , testing started in CMCC Lab. | ||
Demo will follow the same as above. Last week the demo has been addressed. - Closed | ||
ETSI Alignment Support - SOL003 Adapter Enhancement for Frankfurt | No risk, testing in progress, and it will be done before March 2nd. TLS between SOL003 Adapter and SVNFM could be moved to the G release.
11:03: ready for the Integration testing. certificates from MSB are being updated and tested. | |
| ||
Testing effort, will need to take it as per the need. Https call to the MC. dependency on the changes of the MC. Plan to complete this by next week. Should ensure the openstack part of the code is not impacted. Build failure of SO and the oom patch update needs to be corrected for the msb input. 11-03: MSB changes are merged in OOM for the HTTPS config. Testing is in progress. MC is in progress of HTTPs movement. | ||
The initial analysis is done. the code is being done in a separate branch and testing is in progress for the vFW usecase. Oparent should be 3.0.0 Java SDK should be the one from Integration team. Deferred it G release. Will continue the work and merge to the master. Att is doing an internal PoC on the migration will take the inputs. | ||
TSC must have | SO code coverage after the migration to sonar cloud is 64% - PASS SO/libs - 67% - PASS Upgrade capabilities - In progress Vulnerabilities fix - So/libs -Done |
Issues open :
Discussion:
TSC Must haves SO-2519
Provide Upgrade Capabilities... SO-2520 | Under Analysis |
SECCOM Perform Software Composition Analysis - Vulnerability tables
https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16089452
SECCOM Password removal from OOM HELM charts – This is being discussed with ATT team SO-2535
SECCOM HTTPS communication vs. HTTP (Integration with AAF) – This is due for further confirmation of the role of AAF in F and further releases.
OJSI-110 - so-monitor exposes plain text HTTP endpoint using port 30224 UNDER REVIEW
OJSI-138 - so exposes plain text HTTP endpoint using port 30277 UNDER REVIEW
OJSI-169 - Port 30224 exposes unprotected service outside of cluster UNDER REVIEW
OJSI-203 - SO exposes unprotected APIs/UIs (CVE-2019-12128) UNDER REVIEW