ARC SDC Component Description - Oslo-R15

Page Status: Updated for Oslo Jul 31, 2024 
Component Status:  

Last Reviewed on:

Certified by: @Byung-Woo Jun 

SDC High Level Component Definition and Architectural Relationships 

 

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)

    • Note: in addition, ETSI compliant models/packages will be distributed to the Modeling etsicatalog (ETSI Catalog Manager) 

 3 SDC Target Functional Architecture

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

ONAP Portal though shown in above image is to be removed.

4. SDC Current Release API definitions

SDC provides the following interfaces:

Interface Name

Interface Definition

API Spec (Swagger)

Interface Name

Interface Definition

API Spec (Swagger)

SDCE-1

VNF is on-boarded through VNF Onboarding GUI

SDCE-1.json

SDCI-1

VNF is stored in Design Catalog

 

SDCE-2

Service designer creates a service model from Design Catalog items

SDCE-2-SDCE-5.json

SDCI-2 

Designer Studio stores and retrieves Design Catalog items

 

SDCE-3 

Ops designer creates monitoring templates with mS data flows → replaced by DCAE-MOD

 

SDCI-3 

DCAE Designer Studio stores and retrieves monitoring flow with mS elements

 

SDCE-4 

Service tester certifies service models for distribution

SDCE-4.json

SDCE-5 

Service tester distributes service models

SDCE-2-SDCE-5.json

SDCE-6 

Distribution Engine publishes service notification to DMaaP.

ONAP components subscribe to service notification from DMaaP

SDCE-6.json

SDCE-7 

ONAP components retrieve service models from the Design Catalog

SDCE-7.json

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

The current API documents can be found at:

SDC consumes the following interfaces:

Interface

Purpose

API Spec (Swagger)

Interface

Purpose

API Spec (Swagger)

VNFSDKE-3

Upload VNF/PNF packagess for test purpose, and retrieve VNF/PNFs packages from the marketplace.Se

 

VNFSDKE-4VN

Request VNF/PNF validation tests and obtain the result

 

5. New Capabilities in this Release

 

See SDC Release planning for R11 : SDC Kohn R11 Release Planning (link between REQ JIRA and SDC Epics/Stories)

 

6.Kohn Functional View

The SDC Kohn view is (note ONAP Portal to be removed):

7 SDC Architecture Evolution (optional item)

 

8 SDC Overall ONAP Architecture Principle Compliance

 

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

  • Support onboarding of ASD CSARs

  • Migrate to Strimzi from Message Router

  • Multi-tenancy

10 SDC - Current System Deployment Architecture - OOM Helm view

 

 

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.

 

 

  File Modified

File serviceDesign_R13

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_R13.png

Jul 31, 2024 by Byung-Woo Jun

File serviceDesign_R11

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_R11.png

Jul 31, 2024 by Byung-Woo Jun

File serviceDesign_R10

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_R10.png

Jul 31, 2024 by Byung-Woo Jun

File serviceDesign_R9

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_R9.png

Jul 31, 2024 by Byung-Woo Jun

File serviceDesign_r7

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_r7.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-27_20-6-11.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-27-9.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-26-24.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-20-39.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-18-47.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-17-48.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-11-45.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2021-1-20_16-10-28.png

Jul 31, 2024 by Byung-Woo Jun

PNG File SDC deploy.png

Jul 31, 2024 by Byung-Woo Jun

JPEG File SDCevol.JPG

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-9-50.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-24_23-6-25.png

Jul 31, 2024 by Byung-Woo Jun

PNG File image2019-2-27_20-27-43.png

Jul 31, 2024 by Byung-Woo Jun

File serviceDesign_R15

Jul 31, 2024 by Byung-Woo Jun

PNG File serviceDesign_R15.png serviceDesign_R15 exported to image

Jul 31, 2024 by Byung-Woo Jun