...
The current efforts focus on leveraging the design and runtime functions of ONAP to support the CNFs through helm charts.
| View file | ||||
|---|---|---|---|---|
|
New component capabilities for Guilin, i.e. the functional enhancements, if applicable
SDC:
K8s Adapter - On-board the helm and process it as an artifacts of the CSAR to be distributed
On-board Helm Charts
Resource model to include type
(Design CNFs over helm)
Distribute them
SO:
Wont consume the Helm by itself but parse it and push it forward to other ONAP components
Parse the CSAR, extract helm
SOL003 adapter enhancements
New K8s Adapter (Interface to K8s Proxy)
(Model driven workflow)
K8s plugin :
Separation from MultiCloud
Perhaps call it as K8s Proxy
Support new API for the SO interaction
AAI:
Persist the Service instance
(Persist CNF as a resource)
ETSI Catalog DB:
Persist the ETSi VNFM data (IFA-29 and IFA-40 )
Persist Images
K8s Adapter :
A new adapter (pod) inside SO
This would be used to interact with the K8s plugin
New or modified interfaces
...
If they are modified, are they backwards compatible?
Yes, the existing functionalities around the K8s would still be functional.
Interface naming (point to an example)
...