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

Compare with Current View Page History

« Previous Version 14 Next »

Project Name:

  • Proposed name for the project: SDC
  • Proposed name for the repository: SDC, SDC/SDC-Destribution-Client, TBD

Project description:

  • Provides a well-structured organization of visual design & testing tools, templates and catalogs to model and create resources, and services. The output of the SDC is a set of models which drives the orchestration.
    SDC in ONAP WIKI

Scope:

  • Full and comprehensive VNF/Software Application(VF), and service design, which includes, not limited to:
    • Onboarding VNF/VF
    • Workflow design
      • lifecycle flows
      • change management flows
    • Close loop design
    • policy design
    • Service function chaining Design
    • VNF/VF License Design
    • VF/VNF deployment flavor design
  • Collaborative design
    • versioning
    • Design Lifecycle
  • VNF/VF/SERVICE testing and certification
  • Distribution to ONAP
    • TOSCA parser
  • External API- for VNF/VF and  service 
  • Image management

  • Identify the usecase in the Release 1

    • VoLTE usecase 
      • Service and VNF design
      • Workflow design
      • SFC design


  • Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.
  • Specify any interface/API specification proposed,
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.


Architecture Alignment

  • How the existing functionality is going to align in ONAP
    • How it will integrate with:
      • VNF-SDK
      • ICE (VNF certification)
      • Modeling
  • What kind of dependency other projects will have with SDC, e.g SO modeling?
  • How will multi VIM project influence on the input/ output we have for SDC?
  • How to align to standards like ETSI VNF packaging?

Architecture Alignment:

current integration and new integrations for SDC in ONAP


    • How the existing functionality is going to align in ONAP
      • How it will integrate with:
        • VNF-SDK
        • ICE (VNF certification)
        • Modeling
    • What kind of dependency other projects will have with SDC, e.g SO modeling?
    • How will multi VIM project influence on the input/ output we have for SDC?
      • how do we keep close integration with the VIM that impacts modeling
    • How to align to standards like ETSI VNF packaging/OASIS TOSCA/TMF?


Resources:

  • Primary Contact Person: Michael Lando Gerrit ID ml636r Company AT&T
  • David Shadmi Gerrit ID sd200p Company AT&T  
  • Liron Shtraichman Gerrit ID lironsh Company AMDOCS 
  • Tal Halfon mail Halfon.Tal@amdocs.com Company AMDOCS)
  • Mark Pond mail mpond@amdocs.com Company AMDOCS
  • An Ho mail an.ho@huawei.com Gerrit ID anipbu Company Huawei 
  • Kang Xi mail kang.xi@huawei.com Huawei
  • KACHOROVSKY, ARKADY mail ak314p@intl.att.com Company AT&T
  • Zhaoxing mail meng.zhaoxing1@zte.com.cn Company ZTE   Chengdu, China. UTC+8 
  • Huabing mail zhao.huabing@zte.com.cn Company ZTE   Chengdu, China. UTC+8
  • Lv Bo   mail lv.bo163@zte.com.cn Company ZTE   Chengdu, China. UTC+8
  • Li Zi   mail li.zi30@zte.com.cn Company ZTE   Chengdu, China. UTC+8

Other Information:

  • link to seed code : SDC Source
  • Vendor Neutral
  • Meets Board policy (including IPR)

Key Project Facts

Project Name:

  • JIRA project name: SDC
  • JIRA project prefix: SDC

Repo name: SDC and SDC/sdc-destribution-client
Lifecycle State: 
Primary Contact: Michael Lando
Project Lead: Michael Lando
mailing list tag sdc 
Committers:


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

  • No labels