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

Compare with Current View Page History

« Previous Version 59 Next »

Link to Project Proposal training materials

Project Name:

  • Proposed name for the project: SO
  • Proposed name for the repository: so

Project description:

The SO provides the highest level of service orchestration in the ONAP architecture.  Currently SO is implemented via BPMN flows that operate on Models distributed from SDC that describe the Services and associated VNFs and other Resource components. Cloud orchestration is currently based on HEAT templates.

 In order to support Use Cases 1 and 2 in such a way to promote re-usability within ONAP, the goal of this project is to enhance ONAP’s overall orchestration capabilities by aligning and integrating its imperative workflows with a TOSCA-based declarative execution environment.

Service Orchestrator in ONAP WIKI


Scope:
  • This project proposes an expansion of ONAP SO to include a declarative topologically-driven approach to orchestration.  Specifically this project proposes to enhance ONAP SO run-time orchestration framework to support orchestration driven from declarative models (TOSCA encoded) as well as integrated or independent BPMN imperative processing extensions that themselves could be TOSCA-aware.   

  This is envisioned as a multi-release project, which in its maturity will:

    • Support TOSCA models in native format as distributed by SDC
    • Perform lifecycle operations based on a declarative TOSCA model, including: 
      • Deployment
      • Undeployment
      • Scale (Out, In)
      • Heal
      • Software Upgrade (various forms)

Alternative 1: The following diagram illustrates one option for the internal processing BPMN and TOSCA Orchestrator sub-components within SO.  In this approach a separate off-the-shelf TOSCA Orchestrator is incorporated into SO, with a top level BPMN layer delegating well defined orchestration activities to this native TOSCA Orchestrator (see diagram below).

Alternative 2: Another potential approach is shown below, where the BPMN itself in effect is a TOSCA Orchestrator component. 

It is envisioned that initial Releases of this project would demonstrate both alternative approaches:

               For Alternative 1 approach: 

    • Demonstrate SO BPMN workflows interacting with an off-the-shelf TOSCA Orchestrator to collectively drive orchestration behavior for at least an instantiation use case
    • Demonstrate rainy day handling
    • Accomplish the above in a way that is demonstrably extensible to support lifecycle operations such as Scale-In and Scale-Out. 

               For Alternative 2 approach:

    • Demonstrate SO BPMN workflows to drive TOSCA-aware orchestration behavior for VoLTE use case, dependency to VF-C.
    • Support lifecycle operations such as Scale-In and Scale-Out. 

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?



    • What other ONAP projects does this project depend on?

      • SDC (true dependency with SDC SDK)

      • AAI (using API interface)

      • SDN-C (using API interface)

      • APP-C (no existing interface yet)

      • DMaaP (included as part of SDC SDK)

      • MSB (no existing interface yet)

      • VF-C (no existing interface yet)

How does this align with external standards/specifications?

    • TOSCA Simple Profile in YAML Version 1.0
    • OASIS TOSCA Simple Profile for Network Functions Virtualization (NFV) Version 1.0


  • Are there dependencies with other open source projects?
    • ARIA
    • JBOSS
    • Camunda
    • MariaDB
    • EELF

  • Resources:

Other Information:

  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
             The current SO seed code has been already scanned and cleanup to remove all proprietary trademarks, logos, etc. except openecomp to be replaced by onap
             Subsequent modification to the existing seed code should continue to follow the same scanning and clean up principles.

  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: Master Service Orchestrator (can be renamed as Service Orchestrator)
  • JIRA project prefix: MSO- (can be renamed as SO-)

Repo name: mso (can be renamed as 'so' ?)
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
Rob Dugherty, rd472p@att.com, AT&T
John Choma, jc1348@att.com, AT&T

DeWayne Filppi dewayne@gigaspaces.com, GigaSpaces/Cloudify

Eyal Holzman EyalH@Amdocs.com

Barak Dabush Barak.Dabush@amdocs.com

Xin Jin saw.jin@huawei.com

Chuanyu Chen chenchuanyu@huawei.com

Seshu Kumar, seshu.kumar.m@huawei.com

Joe Zhang, zhang.zhou1@zte.com.cn, ZTE

liang wu     wu.liang@zte.com.cn, ZTE
*Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels