Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


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


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


Figure: Service CSAR Distribution-1

  1. SUBSCRIBING – SO, DCAE, A&AI, SDN-C, APP-C, VF-C have subscribed to the SDC Artifact distribution

  2. CSAR DISTRIBUTION to SO – SDC Distributes to SO using the SDCE-6 interface. 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.



 

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




  • No labels