Skip to content

Commit 43cdf51

Browse files
committed
CNV-74970: Update callout formatting for DITA
1 parent 13adcdd commit 43cdf51

18 files changed

Lines changed: 169 additions & 182 deletions

modules/nw-sr-iov-network-node-configuration-examples.adoc

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@
88

99
The following example describes the configuration for an InfiniBand device:
1010

11-
.Example configuration for an InfiniBand device
1211
[source,yaml]
1312
----
1413
apiVersion: sriovnetwork.openshift.io/v1
@@ -33,7 +32,6 @@ spec:
3332

3433
The following example describes the configuration for an SR-IOV network device in a {rh-openstack} virtual machine:
3534

36-
.Example configuration for an SR-IOV device in a virtual machine
3735
[source,yaml]
3836
----
3937
apiVersion: sriovnetwork.openshift.io/v1
@@ -45,13 +43,12 @@ spec:
4543
resourceName: <sriov_resource_name>
4644
nodeSelector:
4745
feature.node.kubernetes.io/network-sriov.capable: "true"
48-
numVfs: 1 <1>
46+
numVfs: 1
4947
nicSelector:
5048
vendor: "<vendor_code>"
5149
deviceID: "<device_id>"
52-
netFilter: "openstack/NetworkID:ea24bd04-8674-4f69-b0ee-fa0b3bd20509" <2>
50+
netFilter: "openstack/NetworkID:ea24bd04-8674-4f69-b0ee-fa0b3bd20509"
5351
# ...
5452
----
55-
<1> When configuring the node network policy for a virtual machine, the `numVfs` parameter is always set to `1`.
56-
<2> When the virtual machine is deployed on {rh-openstack}, the `netFilter` parameter must refer to a network ID. Valid values for `netFilter` are available from an `SriovNetworkNodeState` object.
57-
53+
* When configuring the node network policy for a virtual machine, the `numVfs` parameter is always set to `1`.
54+
* When the virtual machine is deployed on {rh-openstack}, the `netFilter` parameter must refer to a network ID. Valid values for `netFilter` are available from an `SriovNetworkNodeState` object.

modules/nw-sriov-configuring-device.adoc

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -69,13 +69,13 @@ spec:
6969
deviceType: vfio-pci
7070
isRdma: false
7171
----
72-
** `metadata.name` specifies a name for the `SriovNetworkNodePolicy` object.
73-
** `metadata.namespace` specifies the namespace where the SR-IOV Network Operator is installed.
74-
** `spec.resourceName` specifies the resource name of the SR-IOV device plugin. You can create multiple `SriovNetworkNodePolicy` objects for a resource name.
75-
** `spec.nodeSelector.feature.node.kubernetes.io/network-sriov.capable` specifies the node selector to select which nodes are configured. Only SR-IOV network devices on selected nodes are configured. The SR-IOV Container Network Interface (CNI) plugin and device plugin are deployed only on selected nodes.
76-
** `spec.priority` is an optional field that specifies an integer value between `0` and `99`. A smaller number gets higher priority, so a priority of `10` is higher than a priority of `99`. The default value is `99`.
77-
** `spec.mtu` is an optional field that specifies a value for the maximum transmission unit (MTU) of the virtual function. The maximum MTU value can vary for different NIC models.
78-
** `spec.numVfs` specifies the number of the virtual functions (VF) to create for the SR-IOV physical network device. For an Intel network interface controller (NIC), the number of VFs cannot be larger than the total VFs supported by the device. For a Mellanox NIC, the number of VFs cannot be larger than `127`.
72+
** `metadata.name` defines a name for the `SriovNetworkNodePolicy` object.
73+
** `metadata.namespace` defines the namespace where the SR-IOV Network Operator is installed.
74+
** `spec.resourceName` defines the resource name of the SR-IOV device plugin. You can create multiple `SriovNetworkNodePolicy` objects for a resource name.
75+
** `spec.nodeSelector.feature.node.kubernetes.io/network-sriov.capable` defines the node selector to select which nodes are configured. Only SR-IOV network devices on selected nodes are configured. The SR-IOV Container Network Interface (CNI) plugin and device plugin are deployed only on selected nodes.
76+
** `spec.priority` is an optional field that defines an integer value between `0` and `99`. A smaller number gets higher priority, so a priority of `10` is higher than a priority of `99`. The default value is `99`.
77+
** `spec.mtu` is an optional field that defines a value for the maximum transmission unit (MTU) of the virtual function. The maximum MTU value can vary for different NIC models.
78+
** `spec.numVfs` defines the number of the virtual functions (VF) to create for the SR-IOV physical network device. For an Intel network interface controller (NIC), the number of VFs cannot be larger than the total VFs supported by the device. For a Mellanox NIC, the number of VFs cannot be larger than `127`.
7979
** `spec.nicSelector` selects the Ethernet device for the Operator to configure. You do not need to specify values for all the parameters.
8080
+
8181
[NOTE]
@@ -85,12 +85,12 @@ If you specify `rootDevices`, you must also specify a value for `vendor`, `devic
8585
====
8686
+
8787
If you specify both `pfNames` and `rootDevices` at the same time, ensure that they point to an identical device.
88-
** `spec.nicSelector.vendor` is an optional field that specifies the vendor hex code of the SR-IOV network device. The only allowed values are either `8086` or `15b3`.
89-
** `spec.nicSelector.deviceID` is an optional field that specifies the device hex code of SR-IOV network device. The only allowed values are `158b`, `1015`, `1017`.
90-
** `spec.nicSelector.pfNames` is an optional field that specifies an array of one or more physical function (PF) names for the Ethernet device.
91-
** `spec.nicSelector.rootDevices` is an optional field that specifies an array of one or more PCI bus addresses for the physical function of the Ethernet device. Provide the address in the following format: `0000:02:00.1`.
92-
** `spec.deviceType` specifies the driver type. The `vfio-pci` driver type is required for virtual functions in {VirtProductName}.
93-
** `spec.isRdma` is an optional field that specifies whether to enable remote direct memory access (RDMA) mode. For a Mellanox card, set `isRdma` to `false`. The default value is `false`.
88+
** `spec.nicSelector.vendor` is an optional field that defines the vendor hex code of the SR-IOV network device. The only allowed values are either `8086` or `15b3`.
89+
** `spec.nicSelector.deviceID` is an optional field that defines the device hex code of SR-IOV network device. The only allowed values are `158b`, `1015`, `1017`.
90+
** `spec.nicSelector.pfNames` is an optional field that defines an array of one or more physical function (PF) names for the Ethernet device.
91+
** `spec.nicSelector.rootDevices` is an optional field that defines an array of one or more PCI bus addresses for the physical function of the Ethernet device. Provide the address in the following format: `0000:02:00.1`.
92+
** `spec.deviceType` defines the driver type. The `vfio-pci` driver type is required for virtual functions in {VirtProductName}.
93+
** `spec.isRdma` is an optional field that defines whether to enable remote direct memory access (RDMA) mode. For a Mellanox card, set `isRdma` to `false`. The default value is `false`.
9494
+
9595
[NOTE]
9696
====

modules/nw-sriov-device-discovery.adoc

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@
44
// * virt/vm_networking/virt-connecting-vm-to-sriov.adoc
55

66
:_mod-docs-content-type: REFERENCE
7-
[id="discover-sr-iov-devices_{context}"]
7+
[id="nw-sriov-device-discovery_{context}"]
88
= Automated discovery of SR-IOV network devices
99

1010
The SR-IOV Network Operator searches your cluster for SR-IOV capable network devices on worker nodes.
11-
The Operator creates and updates a SriovNetworkNodeState custom resource (CR) for each worker node that provides a compatible SR-IOV network device.
11+
The Operator creates and updates a `SriovNetworkNodeState` custom resource (CR) for each worker node that provides a compatible SR-IOV network device.
1212

1313
The CR is assigned the same name as the worker node.
1414
The `status.interfaces` list provides information about the network devices on a node.
@@ -19,18 +19,14 @@ Do not modify a `SriovNetworkNodeState` object.
1919
The Operator creates and manages these resources automatically.
2020
====
2121

22-
[id="example-sriovnetworknodestate_{context}"]
23-
== Example SriovNetworkNodeState object
24-
2522
The following YAML is an example of a `SriovNetworkNodeState` object created by the SR-IOV Network Operator:
2623

27-
.An SriovNetworkNodeState object
2824
[source,yaml]
2925
----
3026
apiVersion: sriovnetwork.openshift.io/v1
3127
kind: SriovNetworkNodeState
3228
metadata:
33-
name: node-25 <1>
29+
name: node-25
3430
namespace: openshift-sriov-network-operator
3531
ownerReferences:
3632
- apiVersion: sriovnetwork.openshift.io/v1
@@ -41,7 +37,7 @@ metadata:
4137
spec:
4238
dpConfigVersion: "39824"
4339
status:
44-
interfaces: <2>
40+
interfaces:
4541
- deviceID: "1017"
4642
driver: mlx5_core
4743
mtu: 1500
@@ -79,5 +75,5 @@ status:
7975
vendor: "8086"
8076
syncStatus: Succeeded
8177
----
82-
<1> The value of the `name` field is the same as the name of the worker node.
83-
<2> The `interfaces` stanza includes a list of all of the SR-IOV devices discovered by the Operator on the worker node.
78+
* The value of the `name` field is the same as the name of the worker node.
79+
* The `interfaces` stanza includes a list of all of the SR-IOV devices discovered by the Operator on the worker node.

0 commit comments

Comments
 (0)