This is a working wiki to capture the ONAP architecture component descriptions
SDC: Service Design and Creation:
1 SDC High Level Component Definition and Architecteral Relationships
...
...
@startuml
component SDC [
<b>Service Design and Creation</b>
]
[DMAAP] as DMAAP #lightgrey
Package "SDC service descriptor recievers" {
[DCAE] as DCAE #lightgrey
[SDNC] as SDNC #lightgrey
[Service orchestrator] as SO #lightgrey
[AAI] as AAI #lightgrey
[SDNC] as SDNC #lightgrey
[APPC] as APPC #lightgrey
[CLAMP] as CLAMP #lightgrey
[POLICY] as POLICY #lightgrey
[Multi-Cloud] as MC #lightgrey
}
Interface "SDCE-1" as SDCE1
Interface "SDCE-2" as SDCE2
Interface "SDCE-3" as SDCE3
Interface "SDCE-4" as SDCE4
Interface "SDCE-5" as SDCE5
Interface "SDCE-6" as SDCE6
SDCE1 <- SDC
Note left of SDCE1: VF Designer Interface
SDCE2 <- SDC
Note left of SDCE2: Service Designer Interface
SDCE3 <- SDC
Note left of SDCE3: DCAE Designer Interface
SDCE4 <- SDC
Note left of SDCE4: Service Test Interface
SDCE5 <- SDC
Note left of SDCE5: Service Test Interface
SDC->SDCE6
note top of SDCE6: Artifact Distribution Interface
SDCE6 <- DMAAP
DMAAP -> APPC
DMAAP -> CLAMP
DMAAP -> DCAE
DMAAP -> SDNC
DMAAP -> AAI
DMAAP -> POLICY
DMAAP -> MC
@enduml
draw.io Diagram | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
SDC provides 3 functionally distinct layers with modular software, integrated with internal APIs
4. SDC Current Release API definitions
SDC provides the following interfaces:
Interface Name | Interface DefinitionD |
---|---|
SDCE-1 | VNF is on-boarded thru VNF Onboarding GUI |
SDCI-1 | VNF is stored in Design CatalogVNF is stored in Design Catalo |
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 |
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
...
- https://onap.readthedocs.io/en/latest/submodules/sdc.git/docs/consumedapis.html
- https://onap.readthedocs.io/en/latest/submodules/sdc.git/docs/offeredapis.html
SDC consumes the following interfaces:
Interface | PurposePu |
---|---|
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. Dublin Functional View
The SDC dublin view is:
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
...
7 SDC Overall ONAP Architecture Principle Compliance
...
8 The SDC near term focus on architecture deficincies 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
...
9 SDC - Current System Deployment Architecture
User Experience layer (Frontend Jetty Server)
...