[enterprise-4.15] TELCODOCS-1976: Adding content for improved SR-IOV Network Operator node draining#79757
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
do-not-merge/work-in-progress
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Mon Aug 19 09:47:17 - Prow CI generated the docs preview: https://79757--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/hardware_networks/configuring-sriov-device.html |
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
LGTM |
|
/lgtm |
|
/lgtm |
|
@evgenLevin: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
lahinson
added
peer-review-in-progress
| = Configuring parallel node draining during SR-IOV network policy updates | ||
|
|
||
| By default, the SR-IOV Network Operator drains workloads from a node before every policy change. | ||
| The Operator performs this action, one node at a time, to ensure that no workloads are affected by the reconfiguration. |
There was a problem hiding this comment.
| The Operator performs this action, one node at a time, to ensure that no workloads are affected by the reconfiguration. | |
| The Operator completes this action, one node at a time, to ensure that no workloads are affected by the reconfiguration. |
|
|
||
| [NOTE] | ||
| ==== | ||
| A node can only belong to one SR-IOV network pool configuration. If a node is not part of a pool, it is added to a virtual, default, pool that is configured to drain one node at a time only. |
There was a problem hiding this comment.
| A node can only belong to one SR-IOV network pool configuration. If a node is not part of a pool, it is added to a virtual, default, pool that is configured to drain one node at a time only. | |
| A node can belong to only one SR-IOV network pool configuration. If a node is not part of a pool, it is added to a virtual, default pool that is configured to drain one node at a time only. |
| * Install the OpenShift CLI (`oc`). | ||
| * Log in as a user with `cluster-admin` privileges. | ||
| * Install the SR-IOV Network Operator. | ||
| * Nodes have hardware that support SR-IOV. |
There was a problem hiding this comment.
| * Nodes have hardware that support SR-IOV. | |
| * Ensure that nodes have hardware that supports SR-IOV. |
| ---- | ||
| <1> Specify the name of the `SriovNetworkPoolConfig` object. | ||
| <2> Specify namespace where the SR-IOV Network Operator is installed. | ||
| <3> Specify an integer number, or percentage value, for nodes that can be unavailable in the pool during an update. For example, if you have 10 nodes and you set the maximum unavailable to 2, then only 2 nodes can be drained in parallel at any time, leaving 8 nodes for handling workloads. |
There was a problem hiding this comment.
| <3> Specify an integer number, or percentage value, for nodes that can be unavailable in the pool during an update. For example, if you have 10 nodes and you set the maximum unavailable to 2, then only 2 nodes can be drained in parallel at any time, leaving 8 nodes for handling workloads. | |
| <3> Specify an integer number or percentage value for nodes that can be unavailable in the pool during an update. For example, if you have 10 nodes and you set the maximum unavailable value to 2, then only 2 nodes can be drained in parallel at any time, leaving 8 nodes for handling workloads. |
| ---- | ||
| <1> In this example, `pool-1` contains all the nodes with the `worker` role. | ||
|
|
||
| To demonstrate the node draining process using the example scenario from the above procedure, complete the following steps: |
There was a problem hiding this comment.
| To demonstrate the node draining process using the example scenario from the above procedure, complete the following steps: | |
| To demonstrate the node draining process by using the example scenario from the previous procedure, complete the following steps: |
Should this be formatted as a bulleted item like the bulleted item above it on line 124?
|
|
||
| With this update, you can configure the SR-IOV Network Operator to drain nodes in parallel during network policy updates. The option to drain nodes in parallel enables faster rollouts of SR-IOV network configurations. You can use the `SriovNetworkPoolConfig` custom resource to configure parallel node draining and define the maximum number of nodes in the pool that the Operator can drain in parallel. | ||
|
|
||
| For further information, see xref:../networking/hardware_networks/configuring-sriov-device.adoc#configure-sr-iov-operator-parallel-nodes_configuring-sriov-device[Configuring parallel node draining during SR-IOV network policy updates]. |
There was a problem hiding this comment.
| For further information, see xref:../networking/hardware_networks/configuring-sriov-device.adoc#configure-sr-iov-operator-parallel-nodes_configuring-sriov-device[Configuring parallel node draining during SR-IOV network policy updates]. | |
| For more information, see xref:../networking/hardware_networks/configuring-sriov-device.adoc#configure-sr-iov-operator-parallel-nodes_configuring-sriov-device[Configuring parallel node draining during SR-IOV network policy updates]. |
lahinson
added
peer-review-done
|
@amolnar-rh: This pull request references TELCODOCS-1976 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
amolnar-gh
force-pushed
the
TELCODOCS-1976-4.15
branch
from
c705018 to
70b7790
Compare
|
New changes are detected. LGTM label has been removed. |
amolnar-gh
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
amolnar-gh
force-pushed
the
TELCODOCS-1976-4.15
branch
from
70b7790 to
7483cef
Compare
|
@amolnar-rh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
snarayan-redhat
added
merge-review-in-progress
snarayan-redhat
removed
the
merge-review-in-progress
9 participants
Version(s): 4.15
Issue: https://issues.redhat.com/browse/TELCODOCS-1976
Link to docs preview:
QE review:
Additional information:
Cherrypicked from the original main and RN PRs: