SO Weekly Meeting 2020-04-01

Requirements

M1 committed Requirement details

M4 preparedness Status

SO-2556

Migrate 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:

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.

SO-2519

S3P - Improvements of Service Orchestrator

Need to revisit based on the badging demands

SO-1579

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.

SO-2432

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-2427

SOL002 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. - Done

11-03:

Demo ready.

02-04:

Release notes description:

Ve-Vnfm Adapter (aka SOL002 Adapter) registers in external VNFM for VNF LCM notifications (ETSI SOL002 v. 2.5.1)

Ve-Vnfm Adapter (aka SOL002 Adapter) sends DMaaP events based on ETSI VNF LCM notifications received from external VNFMs (ETSI SOL002 v. 2.5.1)

SO-2404

SO 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

11:03:

ready for the Integration testing.

Change:

Support of ETSI Catalog management among the SDC - SO SDC Controller - ONAP-ETSI Catalog Manager.

• SDC supports SOL004 package onboarding

• SO SDC Controller invokes ETSI Catalog Manager if the incoming package is SOL004-based

• ETSI Catalog Manager queries SDC CSAR files for the given CSAR ID and stores the original vendor package into the ETSI Catalog Database

SO-2368

Support 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 unblocked for the code to checked in , would be done 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.

SO-2281

SO support of Network Slicing Demo in Frankfurt

Demo will follow the same as above. Last week the demo has been addressed. - Closed

SO-2156

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.  

• Done, Demo has been presented to the SO team

• Closed

11:03:

ready for the Integration testing.  certificates from MSB are being updated and tested.

Change:

SOL003 Adapter Enhancement for Frankfurt

• SOL003 Adapter supports the following ETSI Package Management (v2.5.1) by leveraging the ETSI Catalog Manager. 

• SOL003 Adapter supports the following ETSI Package Management (v2.5.1) for SVNFM

  • Query VNF Package

  • Read VNFD

  • Fetch VNF Package Artifacts

  • Subscribe

  • Query Subscription Info

  • Terminate Subscription

  • Notify

  • Secure communication between SOL003 Adapter and ETSI Catalog Manager thru MSB

SO-2087

AAI update for VNF improvements

SO-2086

SO 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.

11-03:

MSB changes are merged in OOM for the HTTPS config.

Testing is in progress. MC is in progress of HTTPs movement.

SO-2046

support 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.

Att is doing an internal PoC on the migration will take the inputs.

SO-2519

 TSC must have

SO code coverage after the migration to sonar cloud is 64% - PASS

SO/libs - 67% - PASS

All Http port to migrate to the Https:

 Waiver for the 30227  port is granted 

30224 is fixed

Vulnerabilities fix - So/libs -Done

Provide Upgrade Capabilities... SO-2520

Under Analysis