Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. REGISTER for distribution – SO, DCAE, A&AI, SDN-C, APP-C, VF-C register for distribution of the SDC Artifact distribution via the registration service of the SDCE-6 interface. 

  2. CSAR DISTRIBUTION to SO – SDC Distributes to service CSAR SO using the SDCE-6 interface. The SO listener retrieves the SDC CSAR package. SDC distributes the Service Distribution CSAR package which includes all of the artifacts, templates and resources related to the service created in design time. SDC publishes a topic onto DMaaP. Any RT component that has subscribed to that topic can get that package.

  3. STORE CSAR – SO stores the distributed package.

  4. SO RESPONDS - SO responds to the SDC Distribution exchange using SDCE-6.
  5. CSAR Distribution to DCAE - SDC Distributes service CSAR to DCAE using the SDCE-6 interface,  the DCAE Service Change Handler retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  6. STORE CSAR – DCAE stores the distributed package.
  7. DCAE RESPONDS - DCAE responds to the SDC Distribution exchange using SDCE-6.
  8. CSAR DISTRIBUTION to A&AI - SDC Distributes service CSAR to A&AI using the SDCE-6 interface,  the A&AI  listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  9. STORE CSAR – A&AI stores the distributed package.
  10. A&AI RESPONDS - A&AI responds to the SDC Distribution exchange using SDCE-6.
  11. CSAR DISTRIBUTION  to SDN-C - SDC Distributes service CSAR to SDN-C using the SDCE-6 interface,  the SDN-C UEB  listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  12. STORE CSAR – SDN-C stores the distributed package.
  13. SDN-C RESPONDS - SDN-C responds to the SDC Distribution exchange using SDCE-6.
  14. CSAR DISTRIBUTION  to APP-C - SDC Distributes service CSAR to APP-C using the SDCE-6 interface,  the APP-C listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  15. STORE CSAR – APP-C stores the distributed package.
  16. APP-C RESPONDS - APP-C responds to the SDC Distribution exchange using SDCE-6.
  17. CSAR DISTRIBUTION  to CLAMP- SDC Distributes service CSAR to CLAMP using the SDCE-6 interface,  the CLAMP listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  18. STORE CSAR – CLAMP stores the distributed package.
  19. CLAMP RESPONDS - CLAMP responds to the SDC Distribution exchange using SDCE-6.
  20. CSAR DISTRIBUTION  to POLICY- SDC Distributes service CSAR to POLICY using the SDCE-6 interface,  the POLICY listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  21. STORE CSAR – POLICY stores the distributed package.
  22. POLICY RESPONDS - POLICY responds to the SDC Distribution exchange using SDCE-6.
  23. CSAR DISTRIBUTION  to Multi-Cloud- SDC Distributes service CSAR to Multi-Cloud using the SDCE-6 interface,  the Multi-Cloud listner retrieves the SDC CSAR package, SDC distributes the Service Distribution CSAR package which includes all of the artifacts, including templates and resources related to the service created at design time.
  24. STORE CSAR – Multi-Cloud stores the distributed package.
  25. Multi-Cloud RESPONDS - Multi-Cloud responds to the SDC Distribution exchange using SDCE-6.
  26. Unregister from CSAR distribution. At any time, any module can unregister from the reception of the CSAR using the Register for distribution service of SDCE-6 interface.

3b (temp) Alternative flow representation

PlantUML Macro
titleSDC Service Distribution-1
@startuml
participant SDC
participant "SDC Artifact Consumer" as Consumer

autonumber 

== Register to Service CSAR Distribution == 

Consumer-->Consumer: Register for Distribution

note right: performed by all receptiants of the CSAR
note right: This includes SO, SDC, DCAE, AAI, SDNC, APPC, CLAMP, POLICY, MultiCloud

== Service CSAR Distribution == 



group Distribute to SDC artifact consumer
	hnote over Consumer: Consumer Listner
	SDC -> Consumer: SDC Distribution Notification
	note left: Using DMaaP
	note right: Can be any consumer (SO, SDC, DCAE, AAI, SDNC, APPC, CLAMP, POLICY, MultiCloud)
	Consumer -> SDC: Request Artifact(Artifact Type)
	SDC -> Consumer: Repond (with Artifact)
	Consumer -> Consumer: Store Artifact
	Consumer -> SDC: Distrubution Status Update
end

== Un Register to Service CSAR Distribution (optional, at any time) == 
Consumer --> Consumer : UnRegister for Distribution
note right: performed by all receptiants of the CSAR that want to unregister


@enduml

 

  1. REGISTER for distribution – SO, DCAE, A&AI, SDN-C, APP-C, VF-C register for distribution of the SDC Artifact distribution via the registration service of the SDCE-6 interface. 
    Note: This is only done once, not once per distribution request.
  2. CSAR Ready NOTIFICATION to Consumer– SDC informs the consumer that there is a new artifact to be distributed using the Distrbution notification interface of SDCE-6.

  3. CSAR RETRIEVAL request: The cosumer requests to retrieves the artifact using the Artifact retrieval interface of SDCE-6, indicating the required Artifact Type.

  4. CSAR DELIVERY: As a response to (3) SDC delivers the artifact to the consumer using SDCE-6 
  5. STORE CSAR:  The Consumer stores the distributed artifact.
  6. Consumer Status Update- The consumer informs SDC that the artifact has been consumed using the distribution status interface of SDCE-6.
  7. Unregister from CSAR distribution. At any time, any module can unregister from the reception of the CSAR using the Register for distribution service of SDCE-6 interface.
    Note: This is only done if the Consumer does not want to be informed of any more artifacts that are ready to distribute


3c (temp) Alternative flow

...

PlantUML Macro
titleSDC Service Distribution-1
@startuml
participant SDC
participant SO
participant DCAE
participant AAI
Participant SDNC
Participant APPC
Participant CLAMP
Participant POLICY
Participant MC

autonumber 

== Register to Service CSAR Distribution == 

SO-->SO: Register for Distribution

note right: performed by all receptiants of the CSAR

== Service CSAR Distribution == 


group Distribute to SO
	hnote over SO : SO Listner
	SDC -> SO : SDC Distribution Notification
	note left: Using DMaaP
	SO -> SDC : Request Artifcat (Artifact Type)
	SDC ->SO: Respond with Artifact 
	SO --> SO : Store CSAR
	SO -> SDC: Distribution Status Update
end


group Distribute to DCAE
 	hnote over DCAE : Service Change Handler 
	
	SDC -> DCAE : SDC Distribution Notification
 	note left: Using DMaaP
	DCAE -> SDC : Request Artifcat (Artifact Type)
	SDC -> DCAE: RequestRespond Artifcatwith (Artifact Type)
	DCAE --> DCAE : Store CSAR
	DCAE -> SDC: Distribution Status Update
end

group Distribute to AAI
	hnote over AAI: AAI Listner
	SDC -> AAI : SDC Distribution Notification
 	note left: Using DMaaP
 	AAI -> SDC : Request Artifcat (Artifact Type)
	SDC -> AAI : Respond with Artifact 
	AAI --> AAI : Store CSAR
	AAI -> SDC: Distribution Status Update
end

group Distribute to SDNC
 	hnote over SDNC: UEB Listner
	SDC -> SDNC : SDC Distribution Notification
 	note left: Using DMaaP
 	SDNC -> SDC : Request Artifcat (Artifact Type)
	SDC -> SDNC : Respond with Artifact 
	SDNC --> SDNC : Store CSAR
	SDNC -> SDC: Distribution Status Update
end


group Distribute to APPC  	
	hnote over APPC: Listner
  	SDC -> APPC : SDC Distribution Notification
 	note left: Using DMaaP
 	APPC -> SDC : Request 	APPCArtifcat (Artifact Type)
	SDC -> SDCAPPC : RequestRespond Artifcatwith (Artifact Type)
	APPC --> APPC : Store CSAR
	APPC -> SDC: Distribution Status Update
end


group Distribute to CLAMP
	hnote over CLAMP: Listner

	SDC -> CLAMP : SDC Distribution Notification
 	note left: Using DMaaP
 	CLAMP -> SDC : Request Artifcat (Artifact Type)
	SDC -> CLAMP : Respond with Artifact 
	CLAMP --> CLAMP : Store CSAR
	CLAMP -> SDC: Distribution Status Update

end 

group Distribute to POLICY
	hnote over POLICY: Listner

	SDC -> POLICY : SDC Distribution Notification
 	note left: Using DMaaP
 	SDC -> POLICY : Request Artifcat (Artifact Type)
	SDC -> POLICY : Respond with Artifact 
	POLICY --> POLICY : Store CSAR
	POLICY -> SDC: Distribution Status Update

end

group Distribute to MultiCloud
	hnote over MC: Listner
 	SDC -> mc : SDC Distribution Notification
 	note left: Using DMaaP
 	MC-> SDC : Request Artifcat (Artifact Type)
	SDC-> MC : Respond with Artifact 
	MC --> MC : Store CSAR
	MC -> SDC: Distribution Status Update
end 



== Un Register to Service CSAR Distribution (optional, at any time) == 
SO-->SO: UnRegister for Distribution
note right: performed by all receptiants of the CSAR that want to unregister


@enduml

...