...

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

2. 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.

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

4. 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.

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

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

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

8. MCLOUD INSTANTIATION REQUEST – MCloud performs VNF instantiations.

9. 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 

group ASSOCIATED RESOURCES
	hnote over SO : Service Instance ID, Configuration information
 	SO -> SO : 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

1. ASSOCIATE RESOURCES WITH SERVICE – Ala 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.

2. 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??)

3. CONTROLLER: ACTIVATE SERVICE – The controller (SDN-C, SDN-R, VF-C, APP-C) to activate the service.

4. CONTROLLER: CONFIGURE SERVICE – The controller configures the service, and configures the associated xNF resources.

5. 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.

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

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

8. SO/A&AI UPDATE RECORDS – SO updates the appropriate A&AI records with activation information. [What info is saved and in which records: Service vs VNF/PNF??]

9. USER NOTIFIED - SO notifies service initiator that the service is active.<< what >> – Flow description accor

4. Post Condition

The post-conditions are:

...