...

@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
	SO -> SDNC : 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

8. SO/OPENSTACK: CLOUD RESOURCE REQUEST – SO requests Openstack (Blazer) with a cloud resources request to OOF. OOF performs the NVF Orchestration. Does OOF do this? Is this not done? MEC instances.

9. OPENSTACK: ASSIGN CLOUD RESOURCES – Openstack Blazer assigns cloud resources based on the needs of the service. Assignments are balanced against NFV compute resources in each region, what is currently used/reserved and total capability. Compute resources availability to deploy a VM are consider. The NFV-Orchestration is defined in ETSI NFV.  SO can trigger a reservation request. NFV orchestration can create instances of different types. NFV orchestration has a policy. OpenStack Blazer, reservations localized to the cloud instance. SO > Multi-Cloud performs the Resource assignments. SO does not call Openstack directly. A resource is something that can't just sprawl everywhere. When ONAP is homing it is looking a home for a resource (a cloud instance). Geo-diversity is not yet modeled. ANF. MCloud: Translates generic requirements of resources into VIM-specific APIs to get that resource.

10. SO/OPENSTACK: CLOUD RESOURCE RESPONSE – Openstack responds with the allocated resources.

11. SO/SDN-C NETWORK ASSIGNMENTS – SO requests SDN-C to perform the Network Assignments needed by the Service instance. Can a Subnet, Network Port be assigned? (Virtual MAC, IP address), connect to VM. VM > create port > connect to VM.

12. SDN-C NETWORK ASSIGNMENTS – SDN-C performs Network Assignments needed by the Service instance.

13. SO/SDN-C NETWORK ASSIGNMENTS – SDN-C responds to SO with the Network Assignments needed by the Service instance and the status (success/fail).

14. SO/MCLOUD INSTANTIATION REQUEST – SO requests M-Cloud to perform the VNF instantiations needed by the Service instance.

15. MCLOUD INSTANTIATION REQUEST – MCloud performs VNF instantiations. There might be "multiple" of these VNF Instantiations depending on the number of VNF resources associated with the service. VNF-Adaptor is used.

16. SO/MCLOUD INSTANTIATION RESPONSE – MCloud responds to SO with the VNF instantiations needed by the Service instance and the status (success/fail)

Continuation of SO Service Instantiation Flow:

@startuml

participant VID
participant SO
participant Controller

autonumber 2018

group ASSOCIATED RESOURCES FOR VNFs
	hnote over SO : Service Instance ID, Configuration information
 	SO -> AAI : Associated Resource Created
end

group ASSOCIATED RESOURCES FOR PNFS
	hnote over SO : Service Instance ID, Configuration information
 	SO -> AAI : Associated Resource Created
end

group CONFIGURE & ACTIVATE SERVICE
	hnote over Controller : Service Instance ID, Configuration information
	SO -> Controller : Activate Service
	Controller -> Controller : Configure Associated Resources
	Controller -> Controller : A&AI Updates
	Controller -> Controller : DCAE Monitoring Activated
	Controller -> Controller : Activate Service (State)
	Controller -> SO : Service Activated	
end

group USER RESPONSE
	hnote over SO : Service Instance UUID
	SO -> VID : Service Creation Response, Inform User
end

@enduml

17. ASSOCIATE RESOURCES WITH SERVICE – A la carte Create resource. Macro W/F needs service instance ID associate resource w/ Service Instance. When instantiate PNF service (PNF name) subscribe ID. Update instance in A&AI. Create a relation object where service instance ID & PNF instance ID. Relation modeled service instance + resources. Resource and can see which services it is used. VNFs create service have UUID of service instance. At creation of VNF create the Instance object.

https://wiki.onap.org/display/DW/VNF+and+PNF+Building+Block+Strategy

CPE, BBS, starts when you startup the PNF. Cloud environment creates a VNF. Registered/discovered PNF, build a homing service PNF. How will this work w/ 5G RAN. BBS U/C, registering the Box, customer starting up the box. Waiting for registration event. When receive the registration configure the network, additionalfield has domain-specific information to calculate best configuration of network to configure the PNF. After homing, SO creates a resource level sub-flow w/ a globally unique UUID in A&AI. In that that in sub-flow there is a correlation done with VES. The configuration that takes place happen in the resource level sub-flows. Svc instantion, correlation ID in A&AI. VES w/ correlation ID SO does the correlation (Plug n Plug)

18. SO/CONTROLLER: ACTIVATE SERVICE REQUEST – SO requests the controller (SDN-C, SDN-R, VF-C, APP-C) to activate the service. (Where does SO get data to configure a service??). SO determines the order in which to instantiate the xNF resources. Right now SO does networks first then VNFs. Eventually this should be model-driven from TOSCA. Heirarchical resource creation & nested services.

19. CONTROLLER: ACTIVATE xNF – The controller (SDN-C, SDN-R, VF-C, APP-C) to activate the xNF resources associated with the service.

...

20. CONTROLLER: CONFIGURE xNF – The controller configures the service, and configures the associated xNF resources associated with the service.

...

21. A&AI Published to DMaaP - A&AI publishes on DMaaP that a new service is active, How does it know? A change in status? #1 when dealing with VNFs, the contents of A&AI created when doing something in VID. Create a VNF in a service. Record in A&AI is created immediately. (no VMs are deployed). Same for VF modules. Get back info from OpenStack, HEAT. States are then updated. #2 BBS event CPEauthenticated. BBS & Service, send registration w/ SO & Controller configure networking. Sending CPE authenticated (event means running, active, successfully configured). Go to service instance mark it as “activated”. Confirm end-user can use the services. W/F specific to services. Refer to generic building blocks. TOSCA Modeling of nodes. TOSCA orchestrator has plug-ins for clouds. Cloud specific parameters, unable to create a node in AWS/Azure. A&AI can be configured to “announce” a state change of a service.

...

22. DCAE LISTENING - DCAE is listening for a new service notifications and starts to monitor the service.

23. SO/CONTROLLER: ACTIVATE SERVICE RESPONSE – The controller responds with the Service configuration, and responds to the activation service request back to SO.

24. SO/A&AI UPDATE RECORDS – SO updates the appropriate A&AI records with activation information.

25. USER NOTIFIED - SO notifies service initiator that the service is active. In this example flow, it would be the user at the VID who gets informed that the Service is available and active.

4. Post Condition

The post-conditions are:

...