Distribution in SDC By Michael Lando 2018 2

Distribution in SDC By Michael Lando 2018 -2 -26

ONAP distribution model • The ONAP distribution model is based on a publisher subscriber model. • SDC defines two topics in Dmaap, one for publishing notification and one for reading notification status events. • Using the distribution client, a component can easily subscribe to receive notifications regarding services distributed from SDC. • The distribution client allows the applications to define what type of artifacts they want to download from a service. • The component can choose to receive specific artifact types or to receive the whole CSAR package.

ONAP distribution model Diagram Dashboard OA&M (VID) OPS USER (SDC) UUI REST DCAE Micro Services Bus / DMaa. P Artifact download request External API Handler (Jersey) Authentication filter Distribution Management Request Handler Catalog Business logic Service Business logic Artifact Dao Titan Dao Data Store (Cassandra) Artifacts All CSAR artifacts Data model Distribution Engine Distribution Business logic Notification Management REST Micro Services Bus / DMaa. P Internal API Handler (Jersey) Get Services request CSAR REST SDC CLAMP VFC REST SDC Distribution Client SO REST SDC Distribution Client A&AI REST SDC Distribution Client APP-C SDC Distribution Client SDN-C SDC Distribution Client 3

Distribution flow • Once a distribution client receives a notification, it will access an SDC instance defined in it, to pull the artifacts. • The retrieved artifacts will be download from SDC using REST API. • Once the artifacts are downloaded the application posts a status regarding the download statues. • Since the SDC publishes notifications we need the statues to show the state of the distribution across the different applications.

Distribution flow Operations SDC UI Rest API to activate distribution SDC Distribution engine SDC Catalog n ion t u b tri Dis tio a c i if not tus Message Broker Distribution noti fi Distribution S tatus a St n o i ut ib tr Dis cation GET REST API to pull needed artifacts Distribution Client

Suggested internal component flow • since SDC provides a CSAR package as one of the artifacts, SDC created a parser to allow the different components a singe SDK to read the CSAR instead of implementing there own logic. - Our vision is a single self contained/self explanatory package. • The application can create a logic based on the received/extracted artifact type. • In case of CSAR the artifact will be passed to the SDC parser. • The parser will parse the CSAR and allow retravel of different part of it. - In the future the parse will expose functionality to retrieve artifacts from the package • Other artifacts can be passed to the application logic for handling.

internal component flow diagram Work mod for SO/SDCN/ soon A&AI Component SDC Catalog GET needed artifacts Component logic Other artifacts Distribution Client CSAR artifact Component logic SDC-TOSCA (Parser)