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:

...

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).

GR-API Issue with Helm chart:

         In above payload we can add the user_directive data,

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

GR-API Issue with Helm chart:

1.  when I am trying to create vf- when I am trying to create vf-module (Helm-chart, GR-API and version—v2) through VID, it failed due to vf module name missing in the SDNC-Directives.
2. we adding the User_ Directives data also inside SDNC_ Directives, is there any purpose in it?

...

                  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.