Versions Compared

Old Version 26

changes.mady.by.user Stephen terrill

Saved on

compared with

New Version Current

changes.mady.by.user Benjamin Cheung

Saved on

Key

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

...

WHEN EXECUTED: After Design Time (before Run Time). When SDC Service CSAR package has been composed and is ready for distribution by SDC from a user at the Deployment Studio.

PURPOSE: To distribute the SDC Service CSAR to the run-time components

INFORMATION PASSED: Service CSAR package.

ACTORS:

  • Service Designer
  • Operations Specialist
  • SDC (Deployment Studio)


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

...


The following text describes each of the steps in the above flow. More details and exceptions can be described in the detailed descriptions. Wiki page links can also be linked for a reader to explore more.

  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. CSAR DISTRIBUTION to SO . This is performed by all recipients of the CSAR. This allows the ONAP platform component to receive the message which will contain the package later on.

  2. SDC DISTRIBUTION NOTIFICATION (with 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. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  4. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.

  5. STORE CSAR  – PACKAGE – SO stores the distributed package.

  6. DISTRIBUTION STATUS UPDATE (with SO RESPONDS)- SO responds to the SDC Distribution exchange using SDCE-6.
  7. CSAR Distribution to DCAE SDC DISTRIBUTION NOTIFICATION (with 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.
  8. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  9. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  10. STORE CSAR – PACKAGE – DCAE stores the distributed package.
  11. DCAE RESPONDS DISTRIBUTION STATUS UPDATE (with DCAE)- DCAE responds to the SDC Distribution exchange using SDCE-6.
  12. CSAR SDC DISTRIBUTION to NOTIFICATION (with A&AI) - SDC Distributes service CSAR to A&AI using the SDCE-6 interface,  the A&AI  listner listener 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.
  13. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  14. STORE CSAR – RESPOND WITH ARTIFACT- The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  15. STORE CSAR PACKAGE – A&AI stores the distributed package.
  16. DISTRIBUTION STATUS UPDATE (with A&AI RESPONDSAI)- A&AI responds to the SDC Distribution exchange using SDCE-6.
  17. CSAR DISTRIBUTION  to SDNSDC DISTRIBUTION NOTIFICATION (with SDN-C ) - SDC Distributes service CSAR to SDN-C using the SDCE-6 interface,  the SDN-C UEB  listner listener 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. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  19. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  20. STORE CSAR – PACKAGE – SDN-C stores the distributed package.
  21. DISTRIBUTION STATUS UPDATE (with SDN-C RESPONDSC) - SDN-C responds to the SDC Distribution exchange using SDCE-6.
  22. CSAR DISTRIBUTION  to APPSDC DISTRIBUTION NOTIFICATION (with APP-C ) - SDC Distributes service CSAR to APP-C using the SDCE-6 interface,  the APP-C listner listener 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 –
  23. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  24. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  25. STORE CSAR PACKAGE – APP-C stores the distributed package.
  26. DISTRIBUTION STATUS UPDATE (with APP-C RESPONDSC) - APP-C responds to the SDC Distribution exchange using SDCE-6.
  27. CSAR DISTRIBUTION  to CLAMPSDC DISTRIBUTION NOTIFICATION (with CLAMP) - SDC Distributes service CSAR to CLAMP using the SDCE-6 interface,  the CLAMP listner listener 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 –
  28. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  29. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  30. STORE CSAR PACKAGE – CLAMP stores the distributed package.
  31. CLAMP RESPONDS DISTRIBUTION STATUS UPDATE (with CLAMP) - CLAMP responds to the SDC Distribution exchange using SDCE-6.
  32. CSAR DISTRIBUTION  to POLICYSDC DISTRIBUTION NOTIFICATION (with POLICY) - SDC Distributes service CSAR to POLICY using the SDCE-6 interface,  the POLICY listner listener 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.
  33. REQUEST ARTIFACT - The ONAP platform component can request for the artifacts required by the component.
  34. STORE CSAR – POLICY RESPOND WITH ARTIFACT- The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  35. STORE CSAR PACKAGE – POLICY stores the distributed package.
  36. POLICY RESPONDS DISTRIBUTION STATUS UPDATE (with POLICY) - POLICY responds to the SDC Distribution exchange using SDCE-6.
  37. CSAR DISTRIBUTION  to Multi-CloudSDC DISTRIBUTION NOTIFICATION (with MULTICLOUD) - 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.
  38. STORE CSAR – Multi-Cloud stores the distributed package.
  39. Multi-Cloud RESPONDS - Multi-Cloud responds to the SDC Distribution exchange using SDCE-6.
  40. 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

 

  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. REQUEST ARTIFACT- The ONAP platform component can request for the artifacts required by the component.
  8. RESPOND WITH ARTIFACT - The artifacts or SDC CSAR Package is retrieved from the DMaaP Bus. SDC responds with the package.
  9. STORE CSAR PACKAGE – Multi-Cloud stores the distributed package.
  10. DISTRIBUTION STATUS UPDATE (with MULTICLOUD) - Multi-Cloud responds to the SDC Distribution exchange using SDCE-6.
  11. UN-REGISTER FROM CSAR DISTRIBUTION - At any time, any module can unregister un-register 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


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.
  • SO will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package. 
  • DCAE has successfully received and stored the SDC Service CSAR Package.
  • DCAE will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package.
  • A&AI has successfully received and stored SDC Service CSAR package .
  • A&AI will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package.
  • SDN-C has successfully received and stored SDC Service CSAR package .
  • SDN-C will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package.
  • APP-C has successfully received and stored SDC Service CSAR package .
  • APP-C will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package. 
  • CLAMP has successfully received and stored SDC Service CSAR package .
  • CLAMP will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package. 
  • POLICY has successfully received and stored SDC Service CSAR package .
  • POLICY will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package. 
  • Multi-cloud has successfully received and stored SDC Service CSAR package .
  • Multi-cloud will contain (in local storage) all of the artifacts & components of the SDC Service CSAR Package. 

5. References