Page Status: Reviewed by PTL - JAN-20-2021 / Feb-5-2021
Component Status: Pending ArchCom Review
Last Reviewed on:
Certified by: Christophe Closset
SDC High Level Component Definition and Architectural Relationships
...
SDC consumes the following interfaces:
| Interface | PurposePuPurpose | 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
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 H release
2) Functional Impact :
ARC reviews of new functional features :
| Requirement | Description | Arch Review link | ArchComm decision  | Arch Impact ? | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ONAP CNF orchestration - Honolulu Enhancements |
| 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 | ||||||||||||||||||||
| 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 feature |
Full Arch review status for functional : Honolulu-R8 Functional Requirements Architecture Reviews
3) Non Functional Impact
| Requirement | Description | Arch Review link | ArchComm decision | Arch Impact | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Best Practice (to apply to new code) |
| Pending review | No, mostly only about ensuring proper encryption algorithms | ||||||||||||||||||||
| Best Practice (to apply to new code) |
| 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 |
Full Arch review status for non functional : Honolulu-R8 NonFunctional Requirements Architecture Reviews
6.Honolulu Functional View (No change)
The SDC Honolulu view is:
...
7 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
...
8 SDC Overall ONAP Architecture Principle Compliance
...
9 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
...
- Support common data model as defined by the modelling team
- Model Data Lifecycle Management
- Runtime Distribution Version Management
...
10 SDC - Current System Deployment Architecture - OOM Helm view
User Experience layer (Frontend Jetty Server)
...