Topic Leader(s)
- Ranny Haiby, Catherine Lefevre (Moderator)
- Fernando Oliveira, Byung-Woo Jun
- Lukasz Rajewski, Seshu Kumar Mudiganti, Konrad Bańka
Topic Overview
| Excerpt |
|---|
25m, Fernando Oliveira Byung-Woo Jun, 25m Lukasz Rajewski Seshu Kumar Mudiganti, Konrad Bańka ; 10m Q&A This session will present the features developed in Honolulu and will share the requirement candidates for the Istanbul release, followed by a proposal of "Simplified CNF modeling". |
Slides & Recording
| Info | ||
|---|---|---|
| ||
|
Agenda (TBC)
- What we did for Honolulu
- CNFO
- Native CNF (re)configuration supported in CDS
- Access to k8splugin Day2 APIs in CDS
- Query API in k8splugin
- Healthcheck API in k8splugin aka "helm test"
- vFW CNF use case with Day 2 and pod-deployment health check examples
- ETSI CNF
- CNFO
- What would be our plan for Istanbul
- CNFO
- Helm package validation in SDC
- Helm3, helm hooks in k8splugin
- CNF status verification as a part of the CNF deployment process
- CNF health check workflow in SO
- Runtime k8s information in AAI
- ETSI CNF
- CNFO
- <Simplified CNF modeling or ETSI CNF data modeling>
- <Direct CNF orchestration thru MultiCloud and/or helm package distribution thru CNF-Adapter>