ARC SDC Component Description - Montreal-R13
Chaker Al-Hakim
Byung-Woo Jun
Page Status: Updated for Montreal Nov 1, 2023
Component Status: ArchCom Reviewed Jun 15, 2021 ; Approved
Last Reviewed on: Jun 15, 2021
Certified by:
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 | |
SDCI-1 | VNF is stored in Design Catalog |
|
SDCE-2 | Service designer creates a service model from Design Catalog items | |
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-5 | Service tester distributes service models | |
SDCE-6 | Distribution Engine publishes service notification to DMaaP. ONAP components subscribe to service notification from DMaaP | |
SDCE-7 | ONAP components retrieve service models from the Design Catalog |
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:
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.
