Service Design & Creation

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:
  • SDC portal
  • Onboarding VNF/VF
    • Onboarding heat based VNF/VF
    • Onboarding TOSCA based VNF/VF
  • Service design
  • VNF/VF design
  • Workflow design
    • lifecycle flows
    • change management flows

    • Discovery of available workflow actions (related to Micro Services and discovery)

  • API design
  • Close loop design
  • policy design
  • Service function chaining Design
  • VNF/VF License Design
  • VF/VNF deployment flavor design
  • Export NS/VNF as CSAR Package
    • including the service template
    • including the implementation artifacts
• Collaborative design
  
  • versioning
  • Design Lifecycle
  • Project/Admin dashboard (include user management, VNF/VF and Services relevant to the project).
• VNF/VF/SERVICE testing and certification
• Distribution to ONAP
  • TOSCA parser
  • Distribution to multiple clouds.
• 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
• Test
  • VNF/VF automatic distribution and testing.
  • Service automatic distribution and testing.
• Integration with BSS / Customer ordering.
  
  
• 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

• An alignment between the below projects should be agreed on

  • CLAMP is showing “Designing the Control Loop”

  • ICE – there is a link with onboarding

  • Modelling – we intend to provide modelling for A&AI in SDC
  • Network Function Change Management is showing “This project provides users with the ability to design workflows”
  • Policy Framework Project Proposal is showing “Policy Design GUI - work with SDC project to integrate the Policy Design GUI”
  • VNF SDK – there is a link with onboarding
• 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 mail ml636r@att.com Gerrit ID ml636r Company AT&T
• David Shadmi mail dshadmi@interwise.com Gerrit ID sd200p Company AT&T
• Eden Rozin mail eden.rozin@att.com Gerrit ID er434w Company AT&T
• Liron Shtraichman mail lironsh@amdocs.com 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 Company Huawei
• Chong Li mail chong.li@huawei.com Company 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
• Sun Qi   mail sun.qi310@zte.com.cn Company ZTE   Chengdu, China. UTC+8
• Rene Robert mail rene.robert@orange.com Company Orange UTC+2
• Ting Lu, tl2062@att.com, AT&T
• Xin Jin mail saw.jin@huawei.com Company Huawei Beijing China UTC+8
• Ni Lu mail luna.lu@huawei.com Company Huawei Beijing China UTC+8
• Bin Hou mail bin.hou@huawei.com Company Huawei Beijing China UTC+8
• Chuanyu Chen mail chenchuanyu@huawei.com Company Huawei Beijing China UTC+8
• Earle West ew8463@att.com (AT&T)
• Zhou Jun mail zhoujun8@huawei.com Company Huawei Beijing China UTC+8
• Tao Shen, shentao@chinamobile.com Company China Mobile Beijing China UTC+8

Other Information:

• link to seed code : 
  • SDC Source
  • https://gerrit.open-o.org/r/p/common-tosca-catalog.git
  • https://gerrit.open-o.org/r/p/common-tosca-model-designer.git
  • https://github.com/zte/winery/tree/workflow-modeler
• Vendor Neutral
  The current SDC 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)

Key Project Facts

Project Name:

• JIRA project name: Service Design and Creation
• JIRA project prefix: SDC-

Repo name: SDC and SDC/sdc-destribution-client
Lifecycle State: 
Primary Contact: Michael Lando, Tal Halfon
Project Lead: Michael Lando (AT&T), Avi Ziv (amdocs)
mailing list tag sdc 
Committers:

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