noironetworks / aci-containers / 5417 / 1
57%
master: 63%

LAST BUILD BRANCH: named-port-hpp
DEFAULT BRANCH: master
Ran
Files 72
Run time 12s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 57.008% (-0.09%) from 57.099%
5417.1

push

travis-ci-com

bashokba 
Enable smart nic ovs harward offloading:
Overview:
OVS based software solution is CPU intensive and results in low bandwidth utilization.
Mellanox Accelerated Switching And Packet Processing (ASAP2) technology allows to offload ovs-dataplane to Mellanox ConnectX-4, Mellanox ConnectX-6, Mellanox ConnectX-6 dpu NIC hardware
and keeping ovs-control plain unmodified. In this model, VF representator is attached to ovs bridge and Vfs are moved to pod's namespace

Using network-attachment-definition-client as third party resource which is maintain by k8snetworkplumbingwg
and their clientset and types.go are imported as a module
To obtain allocated resource information for a pod, kubelet client queries podresource service API and retrieve the pci address assigned to the pod

ACI CNI Host Agent code changes
1.Network attachment definition Informers and event handlers in Host-agent env.go
2.Network attachment definitio event-handler would consist of func add, update and delete method
3.Add method will retrieve the information from the Network attachment definition CR and store the data to a map
4.Update method will retrieve the information from the CR and store the data to a map
5.Delete method will delete the CR from the map
6.defaultAnnot = "v1.multus-cni.io/default-network"
7.resourceNameAnnot = "k8s.v1.cni.cncf.io/resourceName"
8.Network attachment definition annotation for pod if acicni used as secondary network = "k8s.v1.cni.cncf.io/networks"
9.Network attachment definition annotation for pod if acicni used as default network = "v1.multus-cni.io/default-network"
10.Pod's annotation (k8s.v1.cni.cncf.io/networks or v1.multus-cni.io/default-network ) stored in a map to check if network attachment definition exists
11.Implementation of Pod resource API call to retrieve the pci address allocated to the pod in netattachdef.go
12.Moving VF to pod's namespace, assigning VF representative to ovs bridge, moving VF back to host namespace in setup.go

For more inform... (continued)

11470 of 20120 relevant lines covered (57.01%)

0.63 hits per line

Source Files on job 5417.1