...
PlantUML Macro | ||
---|---|---|
| ||
@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 : Service CSAR Distribution note left: Using DMaaP SO --> SO : Store CSAR SO -> SDC: Distribution Response end note over SDC, AAI #FFAAAA 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 group Distribute to CLAMP hnote over CLAMP: Listner SDC -> CLAMP : Service CSAR Distribution note left: Using DMaaP CLAMP --> CLAMP: Store CSAR CLAMP -> SDC: Distribution Response end group Distribute to POLICY hnote over POLICY: Listner SDC -> POLICY : Service CSAR Distribution note left: Using DMaaP POLICY --> POLICY: Store CSAR POLICY -> SDC: Distribution Response end group Distribute to MultiCloud hnote over MC: Listner SDC -> MC: Service CSAR Distribution note left: Using DMaaP MC --> MC: Store CSAR MC-> SDC: Distribution Response 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 == Servicethat CSARwant Distribution == to unregister @enduml |
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.
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.
STORE CSAR – SO stores the distributed package.
- SO RESPONDS - SO responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – DCAE stores the distributed package.
- DCAE RESPONDS - DCAE responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – A&AI stores the distributed package.
- A&AI RESPONDS - A&AI responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – SDN-C stores the distributed package.
- SDN-C RESPONDS - SDN-C responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – APP-C stores the distributed package.
- APP-C RESPONDS - APP-C responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – CLAMP stores the distributed package.
- CLAMP RESPONDS - CLAMP responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – POLICY stores the distributed package.
- POLICY RESPONDS - POLICY responds to the SDC Distribution exchange using SDCE-6.
- 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.
- STORE CSAR – Multi-Cloud stores the distributed package.
- Multi-Cloud RESPONDS - Multi-Cloud responds to the SDC Distribution exchange using SDCE-6.
- 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.
...