Page History

...

@startuml
participant VIDCLIENT
participant SO
participant AAI
participant OOF
autonumber 

group SERVICE CREATION REQUEST
	hnote over SO : SO/VIDCLIENT API
	hnote over VIDCLIENT : Svc Model ID, input parameters, Recipe ID
	VIDCLIENT -> SO : Service Creation Request	
end

group INVENTORY RECORD CREATION
	hnote over AAI : AAI API
	SO -> AAI : Inventory Record Creation Request
	AAI -> AAI : Create Inventory Record
	hnote over AAI: INVENTORY RECORD
	AAI -> SO : Inventory Record Creation Response	
end

group HOMING REQUEST
	hnote over SO : xNF Resources, Service ID
	SO -> OOF : Homing Assignment Request
	OOF -> OOF: Homing Assignment
	OOF -> SO : Homing Assignment Response
end

@enduml

...

1. SERVICE CREATION REQUEST – User at the VID CLIENT or OSS requests for a Service instance to be created from the available services that could be instantiated. The user picks the service and finds the corresponding identifier. The user identifies the Service Model ID (what to deploy) and Service Recipe ID (how deploy). There is one Identifier per service that they wish to make an instance of. There is a catalog of available to Services that the user can select from in VID.

   When the user wishes to create a Service Model, it is given a human-friendly name and a UUID is associated with the Service Model. Resources & how they are connected to the service are defined. When the user instantiates Service Model (service instances), they are given names and UUIDs are generated. When an INSTANCE of a service model is to be created, ONAP uses the UUIDs. There is a catalog of service models & list of service recipes that can be used. The user can select: (1) Macro Work-Flows and Recipes for service deploy, or (2) A la carte services: the user deploys resources manually or, (3) Macro Generic Resource flows which use "building blocks" to create recipes. The user can pick Specific Service (Generic) and GR (generic resource) flows, or custom a la carte recipes. The user Selects which recipes to use. There is a Catalog available at VID terminal and SDC makes this catalog available. The user can Create a service, distribute the service, and then it appears VID. The user sees a List of service model, he can search, and then Deployservice, distribute the service, and then it appears VID. The user sees a List of service model, he can search, and then Deploy.

         CLIENT - The client that invokes this flow can be one of four types of clients. These components are described at this wiki: ARC Service Orchestrator Component Description - Dublin

1. VID - ONAP GUI
2. UUI - User Interface
3. CLI - Command Line Interface
4. External API / NBI - External API (North bound interface)

         INFORMATION PASSED - The user inputs the Service Model ID and associated input parameters, and Service Recipe ID (the BPMN Workflow ID). The service recipe ID is distributed with the SDC Service CSAR package and is received by SO.

INVENTORY RECORD CREATION

...

@startuml
participant SO
participant MultiCloud
participant SDNC
participant OpenStack
 
autonumber 8

group CLOUD RESOURCE REQUEST
	hnote over MultiCloud : Resources API
	hnote over SO : Resources Needed
	SO -> MultiCloud : Cloud Resources Request
	MultiCloud -> MultiCloud : Assign Cloud Resources
	hnote over MultiCloud: VM ID
	MultiCloud -> SO : Cloud Resources Response
end

group NETWORK ASSIGNMENTS
	hnote over SO : SO API
	SO -> SDNC : Network Assignment Request
	SDNC -> SDNC : Perform Network Assignments
	hnote over SDNC: AAI Update
	SOSDNC -> SDNCSO : Network Assignments Response	
end

group INSTANTIATION REQUEST
	hnote over SO : xNF Resources, VFM ID
	SO -> OpenStack : Instantiation Request
	OpenStack -> OpenStack: VNF#1 Instantiations
	OpenStack -> OpenStack: VNF#n Instantiations
	OpenStack -> SO : Instantiation Response
end

@enduml

...

• <<interface name (e.g. SDCE-6) >> https://wiki.onap.org/display/DW/SDC+Distribution+client+AID 

•