SDC Casablanca Architecture Alignment

Owned by Michael Lando
Last updated: Aug 07, 2018
2 min read

  1. Architecture Changes since Beijing

    1. As part of the SDC project, we are continuing our work to enhance our modeling capabilities.

    2. As part of SDC we are working to introduce and integrate the flowing plugins:

      1. DCAE-D designer which is responsible for creating the monitoring templates used by DCAE.

      2. Workflow designer which is responsible for creating BPMN workflows used in SO.

      3. CDT tool is also planned to be integrated using the sdc generic plugin framework.

    3. Both components will be part of the SDC ecosystem as separate plugins which are integrated with us.

    4. SDC will be introducing a new ONAP-UI component library. The library will define a set of UI components that can be used across SDC components to create a single look and feel across all components.
      because the different application uses different UI framework the components are defined for angular and react.

    5. SDC got approval to include the runtime catalog as part of our scope, however, because of resource constraints, the work will not be done in Casablanca.

  2. S3P Updates

    2. SDC as a Design-time application will fulfill the needed carrier-grade requirements.

    3. SDC will align to the onap logging 1.2 specifications.

    4. SDC is planning to integrate with AAF.

  3. DM Alignment

    1. SDC will align to the agreement reached in the modeling subcommittee for the Casablanca model requirements.

  4. API Updates

    1. there are no new APIs planned for Casablanca.

    2. SDC supports Swagger by generating a new Swagger file based on annotations in the code.
      the swagger is accessible using this instruction SDC SWAGGER

    3. SDC distribution client SDK APIs are available as Java docs.

    4. SDC Tosca SDK APIs are available as Java docs.

  5. SDC internal architecture Casablanc: