ONAP Service Design intro

hi my name is Michael and oh I'm the project technical lead leading service design and creation SDC is an IDE for network service creation as an IDE SDC provides the tools for designing services and to create the necessary artifacts for the service orchestration before you start working with onap you have to model your service the modern is done in SDC SDC provides a graphical interface for users to model their services SDC provides a set of visual tools for that you can use by dragging and dropping different components onto the SDC canvas you can actually model your service you can see what connects to where what are the capabilities and requirements each each vnf provides to your service SDC provides a way for vendors to unboard the vnfs into the SDC catalog once there they become building blocks for SDC these building blocks can be later reused across different services that service providers need and want to create for next release we are already working on including additional designers like policy designer and clamp designer before as the C you had to manually go across different files and configure small parameters across different number of files and then collect them SDC comes to solve this problem in onap SDC is the design time component it handles all the design time activities other components not up are responsible for receiving the caesar SDC distribute and keeping it for runtime activities under SDC you have a multiple number of designers as you can see in the diagram as the C includes different designers that each and every one of them adds different artifacts to this Tosca Caesar that is later distributed as an example for our one as this includes the main of vnf and service creation designer in addition we also have a workflow designer for next release we are already working on including additional designers like policy designer and clamp designer then vnf package for our one is retrieved from the vnf sdk which serves as a repository for the vendor packages this package one son boarded into SDC we add to it the vendor metadata and then it is added to the SDC catalog from this point we start the service design the packages that are uploaded are used as building blocks in that service the designer connects the different vnfs and adds deployment artifacts to them SDC allows different artifacts to be added to the service or to the VF the artifacts can be informational type or deployment that informational tab includes documentation and such that the vendor can provide for the vnf itself deployment artifacts can be heat files that are used for orchestration or different configuration files that are used for the application itself after the design of the service is complete we promote the service across the lifecycle up to the point that can be distributed to the random components the distribution is done using a Tosca Caesar the Caesar includes all the Tosca models modeled in SDC and all the artifacts that were added to the service during the design time this Caesar will be used by the different components to orchestrate this service

Channel: ONAP Project

Views: 5,572

Rating: 5 out of 5

Keywords: ONAP, NFV, network automation, Linux Foundation, open source, networking, orchestration

Id: y4r5-jRrpgg

Length: 3min 32sec (212 seconds)

Published: Mon Nov 20 2017