Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Topics:

SO needs to update M4 score, Frankfurt Release Requirements, 2: Frankfurt Release Integration Testing Status


Release Planning: Frankfurt

Project Status in Frankfurt Release

Frankfurt Milestone Status


Meeting recording:


Review 


ARC Service Orchestrator Component Description - Frankfurt

Code Freeze : 2nd March the final.

RequirementsM1 committed Requirement detailsM4 preparedness Status
SO-2556Migrate PNF PNP workflow to Building Blocks

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:


SO-2519S3P - Improvements of Service OrchestratorNeed to revisit based on the badging demands
SO-1579SO 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.

SO-2432Multi-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:


SO-2427SOL002 Adapter - supports EM-triggered VNF/VNFC Management

SO-2428: SO changes merged.

  • Use-case testing will be delayed post M4. 
  • CSIT testing will be delayed probably to G release
  • Manual testing is in progress and expected to completed by this week.
SO-2404SO Catalog Management Support

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.

  • More testing is in progress 
  • Closed
SO-2368Support 5G slice orchestration

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.

SO-2281SO support of Network Slicing Demo in FrankfurtDemo will follow the same as above. Last week the demo has been addressed. - Closed
SO-2156ETSI 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.  

  • Done, Demo has been presented to the SO team
  • Closed
SO-2087AAI update for VNF improvements
SO-2086SO Multicloud plugin to Multicloud improvements

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.

SO-2046support Java 11 upgrade

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.

SO-2519

 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 - In progress.

Issues open :

type key summary assignee reporter priority status resolution created updated due
Refresh

Discussion:


Provide Upgrade Capabilities... SO-2520

Under Analysis


SECCOM Perform Software Composition Analysis - Vulnerability tables

https://wiki.onap.org/pages/viewpage.action?pageId=68542772

https://wiki.onap.org/display/DW/Proposal%3A+Remediating+Known+Vulnerabilities+in+Third+Party+Packages



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


  • No labels