search

smart-edge-open / converged-edge-experience-kits

Source code for experience kits with Ansible-based deployment.
Apache License 2.0
37 stars 40 forks source link

[OpenNESS 2003] Controller's IP address becomes invalid after deploying the controller and edge nodes in the OpenNESS network edge mode using kubeovn #25

Closed ramesh-dev-code closed 4 years ago

ramesh-dev-code commented 4 years ago

I am trying to deploy the OpenNESS Controller and Edge nodes in network edge mode using kubeovn as the CNI. After the successful deployment of the controller and edge nodes, the controller's IP address and the Kubernetes API server are not reachable. I guess it is due to the OVS-DPDK's default settings. I presume that there should be an option to assign the desired physical network interface to the DPDK. Please help me to resolve this.

Controller/Edge Nodes: CentOS Linux release 7.6.1810 (Core), Kernel version: 3.10.0-957.el7.x86_64

Status of pods on the Controller after deploying the OVS-DPDK and nfd-worker on the edge node image

ramesh-dev-code commented 4 years ago

The above issue is resolved by increasing the hugepage_amount to 2048 for the edge node in the network_edge.yml.