Page Status:
...
Updated for Istanbul
Component Status:
...
ArchCom Reviewed
Last Reviewed on:
Certified by: Christophe Closset
SDC High Level Component Definition and Architectural Relationships
...
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
2. SDC Component Description:
...
- 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 the following interfaces:
| Interface Name | Interface DefinitionDDefinition | API Spec (Swagger) |
|---|---|---|
SDCE-1 | VNF is on-boarded thru through VNF Onboarding GUI | SDCE-1.json |
SDCI-1 | VNF is stored in Design CatalogVNF is stored in Design CataloCatalog | |
SDCE-2 | Service designer creates a service model from Design Catalog items | SDCE-2-SDCE-5.json |
SDCI-2 | Designer 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 DCAE Designer Studio stores and retrieves monitoring flow with mS elements | |
SDCE-4 | Service Service tester certifies service models for distribution | SDCE-4.json |
SDCE-5 | Service 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 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
...
SDC Release planning for R8 : SDC R8 Release Planning (link between REQ JIRA and SDC Epics/Stories)
1) Use Case Impact :
No new use case impacting SDC for
...
I release
2) Functional Impact :
ARC reviews of new functional features :
| Requirement | Description | Arch Review link | ArchComm decision  | Arch Impact ? | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SDC Multi Model Support Istanbul |
| Approved | No , enhancements to existing feature | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| PNF Software Upgrade enhancement |
| Approved | No, enhancements to existing feature | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| ETSI-Alignment for Honolulu |
| Approved | No, enhancements to existing feature | ||||||||||||||||||||||||||||||||||||||||||||||||||||
. New internal APIs to manage the models. Retro-compatible changes for any other API. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ONAP /3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu) |
| Approved | No, enhancements to existing feature |
| ONAP to support Multi Tenancy (part 2) |
| Approved | No, enhancements to existing featureCNF orchestration - Istanbul Enhancements |
Full Arch review status for functional : HonoluluIstanbul-R8 R9 Functional Requirements Architecture Reviews
3) Non Functional Impact
| Requirement | Description | Arch Review link | ArchComm decision | Arch Impact | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JIRA|||||||||||||||||||||||||||||||||||||
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | ||||||||||||||||||||||||||||||||||||
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | ||||||||||||||||||||||||||||||||||||
| key | REQ-443 | Best Practice (to apply to new code) |
| Pending review | No, mostly only about ensuring proper encryption algorithms |
| Best Practice (to apply to new code)CONTINUATION OF PACKAGES UPGRADES IN DIRECT DEPENDENCIES | ||||||||||||||||||||||||||||||
| N/A (Arch review not required) | No, select most appropriate version for new dependency, if any |
| Global Requirement (apply to all code) |
| Closed | No, already done on SDC | ||||||||||||||||||||||||||||||
| Global Requirement (apply to all code) |
| Closed | No, already done on SDC | |||||||||||||||||||||||||||||||||
| CONTINUATION OF CII BADGING SCORE IMPROVEMENTS FOR SILVER LEVEL |
Full Arch review status for non functional : HonoluluIstanbul-R8 R9 NonFunctional Requirements Architecture Reviews
6.
...
Istanbul Functional View (No change)
The SDC Honolulu Istanbul view is:
7 SDC Architecture Evolution (optional item)
...