Page History

Proposal for enhancements to better integrate the K8S workloads with ONAP - and CDS

View file
name CDS - K8s profile creation options.pptx height 250

Observation in Macro flow with Helm chart:

1. As shown in below we need to pass the model information (vnf and vf model info) to SDC payload...for Heat templet SDC will generate the model info, but in case of Helm (charts and dummy templet, shown in below file) SDC will generate the limited info... So the point is how we can pass the vf-module info here...
   1. if we use one vnf and one vf module info also (helm model info)... how SO will pass the information to multi-cloud for vf instantiation, Macro flow didn't integrated with V2 version (HPA and k8s-plugin service). If we resolve this it will instantiate the pods through Macro-flow.
   2. current macro flow has SO and CDS integration (like Config assign) and with auto heat-bridge, it will get the VM details. so CDS will do the configuration with Ansible/python script which are available in the CBA package. In case of Helm chart we need to fill the gap between SO and Multi-cloud for instantiation. Till service-instance and generic-vnf creation is fine, at the time of vf-creation we need to transfer the flow to multi-cloud, so that it will start the instantiation.
   3. After instantiation need to configure the pods, so need to fill the gap between Multi-cloud/k8s to CDS.

...

2. IN CDS we are using Net box for IP inventory (every time auto increment in IP value for instantiation), Here we are creating the pods, so how we can handle the IP concept here.
3. In case of Macro flow we need to the supplement json information as User_directives at the time of vf-module creation automatically (now we are passing manually through VID).

         In above payload we can add the user_directive data,

                   "userParams": [ { "Homing_Solution": "none" },

GRGR-API Issue with Helm chart:

...

                  vf_module_name is missing from sdnc-directives, so Multi-cloud throwing error at the time of vf-module creation through VID. If we add the vf_module_name in the SDNC_Dircetives it will resolve the issue.

Macro flow with Heat (v1): 

created the stack successfully... with v1 version of vnf and multicloud as orchestrator...

Attached success logs of BPMN and Openstack...

Image Added

Macro flow with Heat (v2): 

Failed to create the stack... Due to v2 version of vnf and multicloud as orchestrator...

just for reference added the logs of BPMN and Openstack with v2 version and orchestrator as Multicloud...

Macro flow with Helm (v2 version):

Need to modify the CBA package according to the Helm charts.