(WIP) OSDOCS-16311:SR-IOV Concepts and Procedures #101830
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@tedaveryredhat: This pull request references OSDOCS-16311 which is a valid jira issue. In 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
the
size/L
|
🤖 Wed Nov 26 16:47:27 - Prow CI generated the docs preview: https://101830--ocpdocs-pr.netlify.app/ |
tedaveryredhat
changed the title
openshift-ci
bot
added
the
do-not-merge/work-in-progress
tedaveryredhat
force-pushed
the
OSDOCS-16311
branch
from
9ff52e7 to
b9addf0
Compare
tedaveryredhat
force-pushed
the
OSDOCS-16311
branch
from
b9addf0 to
e8a6cab
Compare
openshift-ci
bot
added
size/XL
tedaveryredhat
force-pushed
the
OSDOCS-16311
branch
from
e8a6cab to
755215f
Compare
|
@tedaveryredhat: This pull request references OSDOCS-16311 which is a valid jira issue. In 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. |
| .Prerequisites | ||
|
|
||
| * You have the required RPM package or deployment manifests containing the SR-IOV device plugin and the CNI provider. | ||
| * You have configured the underlying network interface controllers (NICs) to expose VFs. |
There was a problem hiding this comment.
I feel this indicates we want the users to create the VFs beforehand, which isn't the case, the operator does that for us. In my experience, there wasn't any need to preconfigure the system in any way before deploying the operator, and OpenShift docs also do not list such a prerequisite, so I would remove this point altogether.
|
|
||
| . Restart the {microshift-short} service to deploy the SR-IOV resources in the `sriov-network-operator` namespace. | ||
|
|
||
| . Deploy the `NetworkNodePolicy` custom resource definition (CRD) to specify the desired VF configuration based on the available hardware. |
There was a problem hiding this comment.
I've been referring to this wrong, to be exact, it's called SriovNetworkNodePolicy.
tedaveryredhat
force-pushed
the
OSDOCS-16311
branch
from
755215f to
4213647
Compare
|
@tedaveryredhat: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
4 participants
Version(s):
4.21
Issue:
https://issues.redhat.com/browse/OSDOCS-16311
Link to docs preview:
https://101830--ocpdocs-pr.netlify.app/microshift/latest/microshift_networking/microshift-sriov.html
QE review: