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 3 Next »

Project Name:

Service Orchestrator

Project Description:

  • The SO provides the highest level of service orchestration in the ONAP architecture.

Leadership Resources :

Role

First Name Last Name

Linux Foundation ID

Email Address

PTL

Seshu Kumar Mudiganti



Committers

Steve Smokowski




Byung-Woo Jun


max.benjamin




Lukasz Muszkieta



Project & Release History

The Service Orchestrator (SO) Project has been an active ONAP Project since Amsterdam and has participated in all releases through Frankfurt.

  • How long the project has been an active:  At launch
  • Release Participation:  All ONAP releases
  • Engagement levels for past releases (up to 3): 
    • Commits per Release:  
    • Contributors per Release: 
    • Companies per release: 

Use Case Participation

SO is pretty much involved in all use cases, since it's the key module in the runtime execution of any of the usecases.

The key use cases that the SO project has contributed to are the following:

vFirewall

vDNS

Scale Out

vCPE

VoLTE

CCVPN

5G OOF SON

BBS

E2E 5G Network Slicing

HPA

MDONS

ONAP - ETSI alignment improvements


Bitergia Statistics from the Last 2 Years

Release name and timeframeCommits Authors 
Amsterdam ( 1/1/2017 to 11/16/2017 )65738
Beijing ( 11/17/2017 to 6/7/2018 )83349
Cassablanca ( 6/8/2018 to 11/30/2018 )68350
Dublin ( 12/1/2018 to 7/9/2019 )97871
El Alto ( 7/10/2019 to 10/24/2019 )34753
Frankfurt ( 10/25/2019 to 6/18/2020 )61865

Architecture Alignment:

Last Architecture Review was for Frankfurt on Jan' 2020 with the results posted here: SO R6 Frankfurt Architecture Review and ARC Service Orchestrator Component Description - Frankfurt

Artifact Information:

SO is divided to several modules each providing an unique functional feature necessary in the orchestration process.

SO project intends to provide  a plug and play architecture based on the business needs of the users.

  • onap/so/api-handler-infra
  • onap/so/bpmn-infra
  • onap/so/catalog-db-adapter
  • onap/so/openstack-adapter
  • onap/so/request-db-adapter
  • onap/so/sdc-controller
  • onap/so/sdnc-adapter
  • onap/so/so-monitoring
  • onap/so/vfc-adapter
  • onap/so/vnfm-adapter
  • onap/so/ve-vnfm-adapter
  • onap/so/nssmf-adapter


Other Information:

Details of the SO components and its functionalities are explained further in the following doc

Understand SO



  • No labels