1. Scope

DESCRIPTION: This flow describes the distribution of the SDC Service CSAR. The SDC Service CSAR is a package of artifacts and output from design time that is created by the various design time GUIs. It captures the things associated with a service that has been defined in design time. This is then distributed to ONAP run-time components.

WHEN EXECUTED: After Design Time (before Run Time)

PURPOSE: To distribute the SDC Service CSAR.

ACTORS:

• Service Designer
• Operations Specialist

Image Added

2. Pre-Conditions

The preconditions are:

• PNFD and VNFD have been mapped to platform data/information model.
• SDC contains the verified service and resource descriptors
• Associated resources (PNF, VNF, ANF) used by services have been properly onboarded.
• Services have been defined in design time, and associated templates, control loops, blueprints have been incorporated into the service
• SDC has composed the Service Design CSAR package ready for distribution.
• The Certification Studio has certified the Package ready for distribution
• The Deployment Studio operator has identified the Service Design CSAR package for distribution

3. Information Flow

Test flow with plantUML

@startuml
participant SDC
participant SO
participant DCAE
participant AAI
Participant SDNC
Participant APPC



autonumber 



== Subscribe to Servie CSAR Distribution == 
Group Subscribe to Service CSAR Distribution
SO-->SO: ..

Autonumber resume

group Distribute to SO
	hnote over SO : SO Listner
	SDC --> SO : Service CSAR Distribution 
	note left: Using DMaaP
	SO --> SO : Store CSAR
	SO --> SDC: Distribution Response
end


note over SDC, AAI
	The flow to DCAE is not correct. DCAE SCH does not get the CSAR itself;
	 SCH get the blueprint through the SDC distribution client 
	(the URL is notified by the SDC and the client library is used to retrieve it)
end note
group Distribute to DCAE
 	hnote over DCAE : Service Change Handler 


 	SDC <--> DCAE: Service CSAR Distribution
  	note left : Using DMaaP
	DCAE --> DCAE : Store CSAR
	DCAE --> SDC: Distribution Response
end




group Distribute to AAI
	hnote over AAI: AAI Listner
	SDC <--> AAI : Service CSAR Distribution  	
	note left: Using DMaaP
	AAI --> AAI : Store CSAR
	AAI --> SDC: Distribution Response
end



group Distribute to SDNC
 	hnote over SDNC: UEB Listner
 	SDC <--> SDNC : Service CSAR Distribution
	note left: Using DMaaP
 	SDNC --> SDNC : Store CSAR
 	SDNC --> SDC: Distribution Response
end


group Distribute to APPC  	
	hnote over APPC: Listner
  	SDC <--> APPC : Service CSAR Distribution
 	note left: Using DMaaP
  	APPC --> APPC: Store CSAR
  	APPC --> SDC: Distribution Response
end

@enduml

4. Post Condition

The post-conditions are:

• The SDC Service CSAR package contains the (1) Service Descriptor, (2) Resource Descriptor, (3) Service Artifacts, (4) Templates and blueprints associated with the service.
• SO has successfully received and stored SDC Service CSAR package (4).
• SO will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package (3). 
• DCAE has successfully received and stored the SDC Service CSAR Package.(7)
• DCAE will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package (6).
• A&AI has successfully received and stored SDC Service CSAR package (10).
• A&AI will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package (9).
• SDN-C (SDN-R) has successfully received and stored SDC Service CSAR package (13).
• SDN-C will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package (12).
• APP-C has successfully received and stored SDC Service CSAR package (16).
• APP-C will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package (15). 

5. References . References

• https://wiki.onap.org/display/DW/SDC+Distribution+client+AID