...
- Package Delivery: A vendor delivers an SOL004-based ASD package
- Pre-Onboarding for validation: TBD (out of PoC scope)
- Onboarding: SDC brings in and stores resources such as xNF, xApp and rApp into ONAP for later use in services.
Onboarding Information Flow
...
- ASD specification is relatively simple
- Propose to use ASD specification as the SDC internal model
| Application Service Descriptor | SDC AID DM (Internal Data Model) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Attribute | Qualifier | Cardinality | Content | Description | Attribute | Qualifier | Cardinality | Content | Description | ||
| asdId | M | 1 | Identifier | ||||||||
| asdSchemaVersion | M | 1 | Version | ||||||||
| asdProvider | M | 1 | String | ||||||||
| asdApplicationName | M | 1 | String | ||||||||
| asdApplicationVersion | M | 1 | Version | ||||||||
| asdApplicationInfoName | M / O | 0..1 | String | ||||||||
| asdInfoDescription | M / O | 0..1 | String | ||||||||
| asdExtCpd | M / O | 0..1 | dataType.ExtCpd | ||||||||
| enhancedClusterCapabilities | M / O | 0..1 | dataType.enhancedClusterCapabilities | ||||||||
| deploymentItems | M | 1..N | DeploymentItem | ||||||||
| Application Service Descriptor > DeploymentItems | SDC AID DM (Internal Data Model) - VF Module  | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Attribute | Qualifier | Cardinality | Content | Description | Attribute | Qualifier | Cardinality | Content | Description | ||
| deploymentItemId | M | 1 | Identifier | ||||||||
| artifactId | M | 1 | Identifier (reference to) | ||||||||
| artifactType | M | 1 | String/enum | ||||||||
| deploymentOrder | M | 1 | String | ||||||||
| lifecycleParameters | M | 1 | String | ||||||||
Enhancement of SDC Internal ASD model
- SDC allows SDC designers to customize/add custom properties when it creates internal ASD models
- SDC UI allows the user to define necessary input parameters and add custom resource properties...
- in that case, enhanced ASD can contain most of resource information for the orchestration by SO/Helm v3
- SDC stores the original vendor ASD packages
- SDC allows SDC designers to customize/add custom properties when it creates internal ASD models
Package Distribution
The following depicts SDC Service CSAR distribution and storage.
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
- SDC sends package notifications to DMaaP for its subscribers (Catalog Manager, SO, other ONAP runtime components)
- Catalog Manager queries ASD descriptors once it gets a package notification from SDC via DMaaP
- note: the current ONAP runtime Catalog Manager handles ETSI packages. we may extend it to handle ASD. TBD
- SDC pushes Helm Charts to the target Helm Repository
- SDC pushes Images to the target Image Repository
- Note: SDC will support large-size images
- Catalog Manager, Helm Repository and Image Repository are centralized in the PoC. Domain-specific repositories will be considered in the future.
LCM Orchestration
TBD
Component Functional Enhancements
SDC
CDS
SDNC
SO
SO Helm Adapter (extend the SO K8S Adapter??)
Catalog Manager (extend the ETSI Catalog Manager??)
Helm Process (a.k.a. Helm v3)
Helm Repository
Image Repository
OOF
AAI
Policy
Interfaces
SDC Onboarding
- SDCE-1
SDC and Catalog Manager
- TBD
- should we leverage the Model_catalog component which was designed for ETSI package???
SDC and Helm Repository
- TBD
SDC and Image Repository
- TBD
OSS/BSS (or SO Client) and SO
- SO NBI
SO and Helm Processor
- TBD
Helm Processor and Placement
- TBD
Helm Processor and Helm Client
- TBD
Helm Client and O-Cloud (K8S)
- Kubernetes APIs