Skip to content

WIP - TELCODOCS-780 - Promote bond CNI to GA - taking over from Kevin #48271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

WIP - TELCODOCS-780 - Promote bond CNI to GA - taking over from Kevin #48271

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 22 additions & 7 deletions modules/nw-sriov-cfg-bond-interface-with-virtual-functions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ Bond-CNI can be created using SR-IOV virtual functions and placing them in the c
* The SR-IOV operator must be installed and configured to obtain virtual functions in a container.
* To configure SR-IOV interfaces, an SR-IOV network and policy must be created for each interface.
* The SR-IOV operator creates a network attachment definition for each SR-IOV interface, based on the SR-IOV network and policy defined.
* The `linkState` is set to the default value `auto` for the SR-IOV virtual function.

[id="nw-sriov-cfg-creating-bond-network-attachment-definition_{context}"]
== Creating a bond network attachment definition
Expand All @@ -35,12 +36,12 @@ apiVersion: "k8s.cni.cncf.io/v1"
"cniVersion": "0.3.1",
"name": "bond-net1",
"ifname: "bond0" <2>
"mode": "active-backup",
"failOverMac": 1, <3>
"linksInContainer": true, <4>
"mode": "active-backup", <3>
"failOverMac": 1, <4>
"linksInContainer": true, <5>
"miimon": "100",
"mtu": 1500,
"links": [ <5>
"links": [ <6>
{"name": "net1"},
{"name": "net2"}
],
Expand All @@ -56,9 +57,21 @@ apiVersion: "k8s.cni.cncf.io/v1"
----
<1> The type is `bond`.
<2> The `ifname` attribute specifies the name of the bond interface.
<3> The `failover` attribute is mandatory for active-backup mode.
<4> The `linksInContainer=true` flag tells the Bond CNI that the interfaces required are to be found inside the container. By default Bond CNI looks for these interfaces on the host which does not work for integration with SRIOV/Multus.
<5> The `links` section defines which interfaces will be used to create the bond. By default, Multus names the attached interfaces as: "net", plus a consecutive number, starting with one.
<3> The `mode` attribute specifies the bonding mode.
+
[NOTE]
====
The bonding modes supported are:

* `balance-rr` - 0
* `active-backup` - 1
* `balance-xor` - 2

For `balance-rr` or `balance-xor` modes, you must set the `trust` mode to `on` for the SR-IOV virtual function.
====
<4> The `failover` attribute is mandatory for active-backup mode.
<5> The `linksInContainer=true` flag informs the Bond CNI that the interfaces required are to be found inside the container. By default Bond CNI looks for these interfaces on the host which does not work for integration with SRIOV and Multus.
<6> The `links` section defines which interfaces will be used to create the bond. By default, Multus names the attached interfaces as: "net", plus a consecutive number, starting with one.

[id="nw-sriov-cfg-creating-pod-using-interface_{context}"]
== Creating a pod using a bond interface
Expand Down Expand Up @@ -107,3 +120,5 @@ link/ether 9e:23:69:42:fb:8a brd ff:ff:ff:ff:ff:ff <2>
----
<1> The `net1` interface is based on an SR-IOV virtual function.
<2> The `net2` interface is based on an SR-IOV virtual function.


6 changes: 0 additions & 6 deletions networking/hardware_networks/using-pod-level-bonding.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,11 @@ toc::[]


:FeatureName: Bond Container Network Interface (CNI)
include::snippets/technology-preview.adoc[leveloffset=+1]

Bonding at the pod level is vital to enable workloads inside pods that require high availability and more throughput. With pod-level bonding, you can create a bond interface from multiple single root I/O virtualization (SR-IOV) virtual function interfaces in a kernel mode interface. The SR-IOV virtual functions are passed into the pod and attached to a kernel driver.

One scenario where pod level bonding is required is creating a bond interface from multiple SR-IOV virtual functions on different physical functions. Creating a bond interface from two different physical functions on the host can be used to achieve high availability and throughput at pod level.

[NOTE]
====
The current functionality of Bond CNI is available only in active-backup mode - for further details, see link:https://bugzilla.redhat.com/show_bug.cgi?id=2037214[*BZ#2037214*].
====

For guidance on tasks such as creating a SR-IOV network, network policies, network attachment definitions and pods, see xref:../../networking/hardware_networks/configuring-sriov-device.adoc#configuring-sriov-device[Configuring an SR-IOV network device].

include::modules/nw-sriov-cfg-bond-interface-with-virtual-functions.adoc[leveloffset=+1]