(Note: this section is optional - you can do SDC work for your own service - but demo.sh init will prepopulate a vFW and vLB for you)
The process of readying a Vendor Software Product for distribution is a complex workflow which not only requires a number a discrete steps but, in order to keep operations compartmentalized, involves a number of different "roles".
In order to keep things more manageable, the overall tutorial has been broken up into three major sections:
- Part 1: Creating a new licensing model
- Part 2: Onboarding a new Virtual Function (VF) which uses the licensing model
- Part 3: Distributing a new VSP based on the VF
This tutorial presumes that you have already completed the previous tutorial on instantiating the base ONAP stack and have been able to successfully access and log into the ONAP Portal.
The goal of this tutorial is not to provide a deep introduction to the design of VFs or VSPs, but to demonstrate both the use of the SDC (Service Design & Creation) component of ONAP in the creation and distribution of VSPs, and also to illustrate the general workflow and roles involved.
4 Comments
jianming wang
Does the part3 title should be distributing a new Service other than "VSP" ?
checked In that link , I see only service can be distribute.
As in the Glossary, In ONAP, a VSP is a Resource.
Yogini Avsare
yes, I agree, Part 3 should be distributing new service and not the VSP
Michael O'Brien
I understand that the entire SDC onboarding workflow is not required for the vFirewall demo - demo.sh init will populate SDC - I need to verify this before marking this section as optional
/michael
Nishi Mathur
I would like to confirm two aspects with respect to Amsterdam Release
1) Is it possible to distribute the VNF Model rather than a Service model to various components
2) Is it possible for SDC to distribute the VNF model for an external service designer / orchestrator.