/
Service Design & Creation (5/17/17)

Service Design & Creation (5/17/17)

Project Name:

  • Proposed name for the project: SDC

  • Proposed name for the repository: sdc, sdc/sdc-distribution-client, 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

    • Service and VNF design

    • Workflow design

    • SFC design

  •  

    • VoLTE usecase 

    • vCPE

      • Service and VNF design

      • Workflow 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

    • DCAE

    • VF-C

    • SO

  • 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:

Other Information:

Key Project Facts

Project Name:

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

Name

Company

Email

Gerrit ID

TZ

Name

Company

Email

Gerrit ID

TZ

Avi Ziv

amdocs

Avi.Ziv@amdocs.com



Raanana, Israel. GMT +3

Gautam Shah

amdocs

GAUTAMS@amdocs.com



Pune, India. GMT +5.5

Vitaliy Emporopulo

amdocs

Vitaliy.Emporopulo@amdocs.com



Raanana, Israel. GMT +3

Zhaoxing Meng

ZTE

meng.zhaoxing1@zte.com.cn 

Zhaoxing

 Chengdu, China. UTC+8

Huabing Zhao

ZTE

zhao.huabing@zte.com.cn



 Chengdu, China. UTC+8

Bo Lv

ZTE

lv.bo163@zte.com.cn



 Chengdu, China. UTC+8

Zi Li

ZTE

li.zi30@zte.com.cn



 Chengdu, China. UTC+8

Sun Qi

ZTE

sun.qi310@zte.com.cn 



Chengdu, China. UTC+8

An Ho

Huawei

an.ho@huawei.com

anipbu

Pacific Time Zone. UTC -7

Kang Xi

Huawei

kang.xi@huawei.com





Rene Robert

Orange

rene.robert@orange.com



Lannion,

France,

UTC+2

Moti Grinberg

AT&T

mg877n@att.com



Lod, Israel. GMT +3

Ofir Sonsino

AT&T

ofir.sonsino@intl.att.com



Lod, Israel. GMT +3

Tao Shen

China Mobile

shentao@chinamobile.com



Beijing, China. UTC+8

Yuanwei Yang

BOCO

yangyuanwei@boco.com.cn



Beijing, China. UTC+8

Heliu Zhong

BOCO

zhongheliu@boco.com.cn



Beijing, China. UTC+8





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

Related content

Service Design and Creation (SDC)
Service Design and Creation (SDC)
More like this
Service Design and Creation (SDC) Portal
Service Design and Creation (SDC) Portal
More like this
VID project (5/17/17)
VID project (5/17/17)
More like this
ARC SDC Component Description - Honolulu-R8
ARC SDC Component Description - Honolulu-R8
More like this
ARC SDC Component Description - Kohn-R11
ARC SDC Component Description - Kohn-R11
More like this
VNF Requirements Charter
VNF Requirements Charter
More like this