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

Compare with Current View Page History

« Previous Version 6 Next »

This is a potential draft of a project proposal template.  It is not final or to be used until the TSC approves it.

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.  The SO accepts TOSCA service models from the SDC and conducts orchestration operations and workflows based on goals (e.g. service deployment, scaling, upgrades, healing, etc..).  The SO will participate in and initiate BPMN workflows.  The SO will use the AAI to map resource requirements to available resources.  It will instantiate and construct VNF service chain via interfaces to downstream controllers (SDN-C, APP-C).  It will maintain the state of complex services in the runtime model.  The SO will have a pluggable architecture to support multiple VIMs.


Scope:

    • Support TOSCA models in native format as distributed by SDC

    • Participate in and launch BPMN workflows

    • Orchestrate complex service chains from model input (e.g. vIMS)

      • Deployment

      • Undeployment

      • Scale

      • Heal

      • Custom (in place upgrade, blue/green testing, other)

    • Use AAI and TOSCA node requirements to perform late service/infrastructure binding

    • Pluggable VIM support (including containers)

    • VIM capability awareness (e.g. VIM version)

    • Multi/hybrid VIM support

    • REST API ( ideally message bus as well: TBD)

    • Multi-tenant capabilities

    • Initial Release goals :

    • Drive orchestration from TOSCA model - as an alternative to using the MSO Catalog representation of the TOSCA, reference the TOSCA model directly from the orchestration workflows and/or from cloud adapter logic.

      • Use for decomposition of service into resources (VNFs, Networks, etc.)

      • Use for the definition of VNF resources (i.e. breakdown of Heat templates, environment properties, orchestration parameters)

      • Identify target workflows (BPMNs) in the TOSCA model on the service template

      • Identify lifecycle operation references (i.e. BPMNs) in the TOSCA node template definitions

      • Identify IAAS requirements in TOSCA and construct runtime model via AAI query.

      • Command SDN-C from TOSCA network description

      • Target OpenStack initially (either via HEAT API or using OpenStack component APIs: Nova, Neutron...)
      • Virtual Machines deployment

Architecture Alignment:

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



    • What other ONAP projects does this project depend on?

      • Modeling

      • SDC

      • AAI

      • SDN-C

      • APP-C

      • DMaaP (?)

  • How does this align with external standards/specifications?

    • TOSCA Simple Profile in YAML Version 1.1

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


  • Are there dependencies with other open source projects?
    • ARIA

  • Resources:
  • Primary Contact Person: DeWayne Filppi (dewayne@gigaspaces.com)
  • Names, gerrit IDs, and company affiliations of the committers
    • DeWayne Filppi, dewayne@gigaspaces.com, GigaSpace
    • Byung-Woo Jun - byung-woo.jun@ericsson.com, Ericsson
    • Xin Jin - Huawei
      Steve Smokowski, ss835w@att.com, AT&T
    • Rob Daugherty, rd472p@att.com, AT&T
    • Gil Bullard, wb5674@att.com, AT&T
    • Ting Lu, tl2062@att.com, AT&T
    • Jeff Mitryk, jm5764@att.com, AT&T
    • Claude Noshpitz, cn5542@att.com, AT&T
    • Eric Debeau, eric.debeau@orange.com Orange

    • Eyal Holzman EyalH@Amdocs.com Amdocs

    • Barak Dabush Barak.Dabush@amdocs.com Amdocs

  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • 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?
  • 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:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
rd472p@att.com
ss835w@att.com


Eyal Holzman EyalH@Amdocs.com

Barak Dabush Barak.Dabush@amdocs.com


*Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels