SO Beijing Architecture Review
Changes since Amsterdam
Support the Homing through OOFSO-390: Support homing solution in SO workflows through OOF (HPA)Closed
Support the Scale-Out featureSO-391: SO should support scaling of Network services and VF modulesClosed
Support PNF OrchestrationSO-436: SO should support orchestration of PNF resource typeClosed
Support Change Management
TOSCA Orchestrator demonstration(Stretch goal).SO-22: Alternative 1 requires that the TOSCA orchestrator be part of the SO. Closed
Enhance the SO code SO-368: To improve the SO Amsterdam releaseClosed
S3P UpdatesSO-375: To make SO carrier GradeClosed
Security
WIP: CII Badge
WIP: Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
WIP: Increase test code coverage to reach 50%
Pilot the security static checking for Beijing (Coverity issue fix)
Manageability-Logging
Update log configuration for SO components according to Logging guidelines
Resiliency and Scalability
Depend on kubernetes to manage instance(s) of SO component(s)
Coordinating with the OOM for the configuration for SO in OOM
Usability
Document APIs in readthedocs (Swagger) and solve inconsistent problem between code and API
Improve the deployment and configuration documentation
Performance and Stability
Defining the performance criteria with Bench marking team.
SO team will work with Integration team to do performance testing
IM/DM Alignment
SO team is participating the modeling discussion about Service/Resource IM/DM
Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee
API Updates
Support the homing through OOF through new API.
NS Scale out interface
ETSI for SOL support needs to be checked with VFC