...
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
Note:
- ETSI SOL001-based model orchestration leveraging Helm Processor needs to be sort out further.
- Helm Processor realization (e.g., MultiCloud??, EMCO?? others??) will be discussed
- Placement realization (e.g., OOF?? others??) will be discussed
...
- Onboard package – this will ingest the package, and verify the integrity and authenticity of the package etc.
- SDC supports ASD packages in addition to ETSI packages
- both ASD and ETSI packages conform to ETSI SOL004
- SDC transforms vendor ASD to internal ASD
- Store relevant information in repo – for internal organization and making the package available for deployment.
- SDC creates Service CSAR for the ASD AND ETSI VNF/CNFD
- Descriptors will be stored in the Catalog Manager Repository
- Helm Charts will be stored in the Helm Repository
- Images will be stored in the Image Repository
- Receive deployment order, along with required parameters. The required parameters are the ones specified in the ASD under “lifecycleParameters”.
- SO receives incoming Service Requests and retrieves the corresponding Service Catalog
- So validates required parameters
- Fetch descriptors from Service package.
- SO decomposes incoming Service Requests into Resources
- If the resource is for CNF and ASD-based models, SO follows the ASD orchestration path
- If the resource is for ETSI-based models, SO delegates its orchestration to SO NFVO or VFC
- SO delegates ASD orchestration to the Helm Processor (Helm v3)
- SO passes Descriptor (ASD) information and required parameters (e.g., lifecycleParameters) to the Helm Processor
- Helm Processor handles internal ASD-based NF or application
- Helm Processor retrieves Helm Charts from the Repository
- Using received parameters and default values already in the chart to construct the value files.
- With this input Helm performs a chart render, i,e. translates the charts into concrete K8S resources descriptions.
- In the placement use case, the concrete K8S workload description (pod, daemonset, deployment, replicaset, statefulset, job, cronjobs, etc) and the ASD will be used by internal logic of orchestrator for placement decision.
- Perform placement decision – the placement function can parse the workload descriptors and ASD and use that information to select the appropriate cluster in the selected O-Cloud.
- Use Helm to install the application on a particular cluster with the values constructed in the Helm Processor
- Helm Processor do dry-run before sending its requests to K8S
SDC Onboarding
- Package Delivery: A vendor delivers an SOL004-based ASD package
- Pre-Onboarding for validation: TBD
- Onboarding: SDC brings in and stores resources such as xNF, xApp and rApp into ONAP for later use in services.
Onboarding Information Flow
Note: ASD package validation is not addressed here. TBD
PlantUML Macro | ||
---|---|---|
| ||
@startuml
participant VENDOR
participant ONAPUSER
participant SDC
autonumber
group ASD PACKAGE DELIVERY
hnote over ONAPUSER : Vendor Package Delivery
VENDOR -> ONAPUSER : ASD Package Delivery
end
group Create a resource
hnote over SDC : Options to create a resource in SDC
group Onboarding
group Options
hnote over SDC : Two onboarding options
group PACKAGE ONBOARDING
hnote over SDC : Create a VSP model using onboarding ASD package
ONAPUSER -> SDC : onboarding an ASD package
SDC -> SDC : Create an internal model with Metadata added
SDC -> SDC : Transform onboarding artifacts into SDC onboarding
SDC -> SDC : Transform onboarding descriptor into internal descriptor\n(proposal: use ASD models as internal models)
SDC -> SDC : License Model Files Added
end
group Manual ASD VSP creation
hnote over SDC : Manual create a ASD VSP model
ONAPUSER -> SDC : Create a VSP
SDC -> SDC : Create an internal model with Metadata added
ONAPUSER -> SDC : Update internal descriptor proprieties
ONAPUSER -> SDC : License Model Files Added
ONAPUSER -> SDC : Artifacts Added
end
end
end
group Create a resource
group Create resource from a VSP
hnote over SDC : Create resource model from a VSP
ONAPUSER -> SDC : Create a VSP
SDC -> SDC : Transform a VSP into a resource model
SDC -> SDC : update internal descriptor properties
SDC -> SDC : update License Model Files
ONAPUSER -> SDC : Additional Artifacts Added (Manual/Optional)
end
group Manual create an ASD resource
hnote over SDC : Manual create ASD Resources
SDC -> SDC : create an internal ASD model with Metadata added
ONAPUSER -> SDC : Update internal descriptor properties
ONAPUSER -> SDC : License Model Files Added
ONAPUSER -> SDC : Additional Artifacts Added (Manual/Optional)
end
end
end
@enduml |
Interfaces
SDC Onboarding
SDC and Catalog Manager
SDC and Helm Repository
...