Page Status: Updated for R7 - Jul, 22, 2020

Component Status: ArchCom Review done on the 28th of July 2020

SDC High Level Component Definition and Architectural Relationships 

Main change : Make DCAE Designer optional for Guilin (eg : make it enable/disable via helm chart, retire in next release) → replaced by DCAE-MOD

2. SDC Component Description:

SDC is the Centralized ONAP Design Time Platform

• SDC Provides Service Provider a seamless design time user experience

  • Allow SP to configure for its design environment including user roles and design workflows

  • Import generic ONAP management functions (MS, Flows, Policies) from ONAP developed software and SP’s adaptations (1) (2)

  • Onboard & Design resource level network functions (VNF, PNF) (3)

  • Compose Service models with resources (4)

  • Design Service Provider specific Management Flows and Policies for the Resource or Service Model (5)

• SDC integrates multi design tools into one platform

  • Provide ONAP development a “Pluggable framework” for easy design tools integration

• SDC Provides a common Catalog for designed objects

  • Support robust catalog cataloging capabilities for storage and management of ONAP standard compliant data models

• Provide linkage & management of SP’s Test/validation process & artifacts for certification of the designed models (6)

• Distributes models to runtime for execution (7)

 3 SDC Target Functional Architecture

Open

SDC provides 3 functionally distinct layers with modular software, integrated with internal APIs

4. SDC Current Release API definitions

Open

SDC provides the following interfaces:

Note:   xxxI interface is a SDC internal interface.  xxxxE interface is a SDCE external interface

The current API documents can be found at:

• https://docs.onap.org/projects/onap-sdc/en/latest/consumedapis.html

• https://docs.onap.org/projects/onap-sdc/en/latest/offeredapis.html

SDC consumes the following interfaces:

5. Guilin Functional View

The SDC Guilin view is:

Guilin changes :

• Disable DCAE Designer (replaced by DCAE-MOD) and make it optional, retire in next release

6 SDC Architecture Evolution (optional item)

The goals of the SDC evolution are:

• Seamless Design Time user experience based on user’s roles and design workflow

• Pluggable Framework to integrate multiple external developed design tools into SDC

• One consolidated Design Catalog with common models in SDC to drive ONAP runtime

• Support for HELM and TOSCA

7 SDC Overall ONAP Architecture Principle Compliance

8 The SDC near term focus on architecture deficiencies are (optional):

User experience:

• Workflow Congfigurator to define service provide specific design workflow

• Workflow guided, role-based user experience

• Function-based (rather than tool based) GUI

Application Layer for Tool Plug-ins

• Provide Plug-in Framework for design tools

• Support standard-based VNF package onboarding tool plug-ins

• Support Onboarding Helm packages

• Provide Data Mapping/Translation/Enrichment to ONAP Standard Internal Model

• Provide tools to support Service Provider's test & validation environment/process for model certification

• Near term tasks: Integrate Policy Designer, CDS - Retire DCAE DS as now replaced by DCAE-MOD

Catalogue & Data Management

• Support common data model as defined by the modelling team

• Model Data Lifecycle Management

• Runtime Distribution Version Management

9 SDC - Current System Deployment Architecture

User Experience layer (Frontend Jetty Server)

• supplies the static content of web pages, and all resources that required by the GUI

• serves as a proxy for the REST API requests coming from the GUI

• Every request originating from the GUI is passed to the Jetty front-end server before it is executed.

Application Layer (Backend Jetty Server)

• Containers all the application logic for the SDC.

Catalog/Data Management Layer

• Cassandra is used to store audit data, artifacts and data model objects.