TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… by StephenJamesSmith · Pull Request #85507 · openshift/openshift-docs

StephenJamesSmith · 2024-11-26T18:24:02Z

[TELCODOCS-1956]: Move NVIDIA GPU architecture content to Hardware accelerator overview

This topic has already been reviewed and published and has been moved from the Architecture section to the Hardware accelerators section.. Changes for new technology may be expected.

Jira: https://issues.redhat.com/browse/TELCODOCS-1956

Version(s): openshift-4.17+, openshift-4.16.z

Link to docs preview: https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/nvidia-gpu-architecture

SME: @egallen
QE: @wabouhamad

openshift-ci-robot · 2024-11-26T18:24:07Z

@StephenJamesSmith: This pull request references TELCODOCS-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.17" instead.

Details

In response to this:

[TELCODOCS-1956]: Move NVIDIA GPU architecture content to Hardware accelerator overview

This topic has been reviewed and published and was in the Architecture section. Changes for new technology expected.

Jira: https://issues.redhat.com/browse/TELCODOCS-1956

Version(s): openshift-4.17+, openshift-4.16.z

Link to docs preview:

SME: @egallen
QE: @bthurber

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.

ocpdocs-previewbot · 2024-11-26T18:40:16Z

🤖 Thu Dec 05 14:57:35 - Prow CI generated the docs preview:

https://85507--ocpdocs-pr.netlify.app/
https://85507--ocpdocs-pr.netlify.app/openshift-dedicated/latest/architecture/nvidia-gpu-architecture-overview.html
https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/nvidia-gpu-architecture.html
https://85507--ocpdocs-pr.netlify.app/openshift-rosa/latest/architecture/nvidia-gpu-architecture-overview.html

ocpdocs-vale-bot · 2024-11-26T18:41:21Z

hardware_accelerators/about-hardware-accelerators.adoc

+include::modules/nvidia-gpu-vsphere.adoc[leveloffset=+3]
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/nvaie-with-ocp.html#openshift-container-platform-on-vmware-vsphere-with-nvidia-vgpus[OpenShift Container Platform on VMware vSphere with NVIDIA vGPUs]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

ocpdocs-vale-bot · 2024-11-26T18:41:22Z

hardware_accelerators/about-hardware-accelerators.adoc

+include::modules/nvidia-gpu-kvm.adoc[leveloffset=+3]
+[role="_additional-resources"]
+.Additional resources
+* link:https://computingforgeeks.com/how-to-deploy-openshift-container-platform-on-kvm/[How To Deploy OpenShift Container Platform 4.13 on KVM]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

ocpdocs-vale-bot · 2024-11-26T18:41:23Z

hardware_accelerators/about-hardware-accelerators.adoc

+.Additional resources
+
+* link:https://docs.nvidia.com/ngc/ngc-deploy-on-premises/nvidia-certified-systems/index.html[NVIDIA-Certified Systems]
+* link:https://docs.nvidia.com/ai-enterprise/index.html#deployment-guides[NVIDIA AI Enterprise]


🤖 [error] Vale.Avoid: Avoid using 'AI'.

ocpdocs-vale-bot · 2024-11-26T18:41:24Z

hardware_accelerators/about-hardware-accelerators.adoc

+* link:https://docs.nvidia.com/ai-enterprise/index.html#deployment-guides[NVIDIA AI Enterprise]
+* link:https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/overview.html#[NVIDIA Container Toolkit]
+* link:https://docs.nvidia.com/datacenter/cloud-native/openshift/latest/enable-gpu-monitoring-dashboard.html[Enabling the GPU Monitoring Dashboard]
+* link:https://docs.nvidia.com/datacenter/cloud-native/openshift/latest/mig-ocp.html[MIG Support in OpenShift Container Platform]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

openshift-ci-robot · 2024-11-26T18:48:07Z

@StephenJamesSmith: This pull request references TELCODOCS-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.17" instead.

Details

In response to this:

[TELCODOCS-1956]: Move NVIDIA GPU architecture content to Hardware accelerator overview

This topic has been reviewed and published and has been moved from the Architecture section. Changes for new technology expected.

Jira: https://issues.redhat.com/browse/TELCODOCS-1956

Version(s): openshift-4.17+, openshift-4.16.z

Link to docs preview: https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html#nvidia-gpu-architecture_about-hardware-accelerators

SME: @egallen
QE: @bthurber

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.

ocpdocs-vale-bot · 2024-11-27T17:29:22Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+include::modules/nvidia-gpu-vsphere.adoc[leveloffset=+2]
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/nvaie-with-ocp.html#openshift-container-platform-on-vmware-vsphere-with-nvidia-vgpus[OpenShift Container Platform on VMware vSphere with NVIDIA vGPUs]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

ocpdocs-vale-bot · 2024-11-27T17:29:23Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+include::modules/nvidia-gpu-kvm.adoc[leveloffset=+2]
+[role="_additional-resources"]
+.Additional resources
+* link:https://computingforgeeks.com/how-to-deploy-openshift-container-platform-on-kvm/[How To Deploy OpenShift Container Platform 4.13 on KVM]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

ocpdocs-vale-bot · 2024-11-27T17:29:24Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+.Additional resources
+
+* link:https://docs.nvidia.com/ngc/ngc-deploy-on-premises/nvidia-certified-systems/index.html[NVIDIA-Certified Systems]
+* link:https://docs.nvidia.com/ai-enterprise/index.html#deployment-guides[NVIDIA AI Enterprise]


🤖 [error] Vale.Avoid: Avoid using 'AI'.

ocpdocs-vale-bot · 2024-11-27T17:29:25Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+* link:https://docs.nvidia.com/ai-enterprise/index.html#deployment-guides[NVIDIA AI Enterprise]
+* link:https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/overview.html#[NVIDIA Container Toolkit]
+* link:https://docs.nvidia.com/datacenter/cloud-native/openshift/latest/enable-gpu-monitoring-dashboard.html[Enabling the GPU Monitoring Dashboard]
+* link:https://docs.nvidia.com/datacenter/cloud-native/openshift/latest/mig-ocp.html[MIG Support in OpenShift Container Platform]


🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{product-title}' rather than the plain text product term 'OpenShift Container Platform', unless your use case is an exception.

openshift-ci-robot · 2024-11-27T17:35:39Z

@StephenJamesSmith: This pull request references TELCODOCS-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.17" instead.

Details

In response to this:

[TELCODOCS-1956]: Move NVIDIA GPU architecture content to Hardware accelerator overview

This topic has been reviewed and published and has been moved from the Architecture section. Changes for new technology expected.

Jira: https://issues.redhat.com/browse/TELCODOCS-1956

Version(s): openshift-4.17+, openshift-4.16.z

Link to docs preview: https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/nvidia-gpu-architecture

SME: @egallen
QE: @bthurber

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.

egallen · 2024-11-27T17:43:29Z

LGTM. Feel free to merge.

bthurber · 2024-11-27T19:08:11Z

@wabouhamad should be assigned for QE.

StephenJamesSmith · 2024-12-02T18:22:48Z

@wabouhamad Please review and comment/lgtm.

openshift-ci-robot · 2024-12-02T18:23:17Z

@StephenJamesSmith: This pull request references TELCODOCS-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.17" instead.

Details

In response to this:

[TELCODOCS-1956]: Move NVIDIA GPU architecture content to Hardware accelerator overview

This topic has been reviewed and published and has been moved from the Architecture section. Changes for new technology expected.

Jira: https://issues.redhat.com/browse/TELCODOCS-1956

Version(s): openshift-4.17+, openshift-4.16.z

Link to docs preview: https://85507--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/nvidia-gpu-architecture

SME: @egallen
QE: @wabouhamad

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.

StephenJamesSmith · 2024-12-02T18:36:42Z

@egallen Wondering if we should add a "Supported hardware" section with a table that lists the supported NVIDIA GPUs and hardware? This table could be updated as needed. WDYT?

wabouhamad

/lgtm

StephenJamesSmith · 2024-12-04T19:10:54Z

/label telco

lpettyjo

Otherwise, LGTM!

lpettyjo · 2024-12-05T14:20:54Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+
+NVIDIA supports the use of graphics processing unit (GPU) resources on {product-title}. {product-title} is a security-focused and hardened Kubernetes platform developed and supported by Red Hat for deploying and managing Kubernetes clusters at scale. {product-title} includes enhancements to Kubernetes so that users can easily configure and use NVIDIA GPU resources to accelerate workloads.
+
+The NVIDIA GPU Operator leverages the Operator framework within {product-title} to manage the full lifecycle of NVIDIA software components required to run GPU-accelerated workloads.


I would choose a more accessible word instead of "leverage". Maybe "uses" or "takes advantage of".

lpettyjo · 2024-12-05T14:22:16Z

modules/nvidia-gpu-architecture.adoc

+[id="nvidia-gpu-architecture_{context}"]
+= NVIDIA GPU architecture
+
+NVIDIA supports the use of graphics processing unit (GPU) resources on {product-title}. {product-title} is a security-focused and hardened Kubernetes platform developed and supported by Red Hat for deploying and managing Kubernetes clusters at scale. {product-title} includes enhancements to Kubernetes so that users can easily configure and use NVIDIA GPU resources to accelerate workloads.


Same comment as above.

No change on this one. The wording was chosen by devs because of unique relationship between OpenShift and partner accelerators.

…lerators section

openshift-ci · 2024-12-05T14:47:04Z

New changes are detected. LGTM label has been removed.

openshift-ci · 2024-12-05T15:06:43Z

@StephenJamesSmith: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

StephenJamesSmith · 2024-12-05T15:40:47Z

/label merge-review-needed

adellape

LGTM

adellape · 2024-12-05T18:34:48Z

hardware_accelerators/nvidia-gpu-architecture.adoc

+include::modules/nvidia-gpu-csps.adoc[leveloffset=+2]
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.nvidia.com/ai-enterprise/deployment-guide-cloud/0.1.0/aws-redhat-openshift.html[Red Hat Openshift in the Cloud]


The "Openshift" (lowercase "S") typo in the destination page is a bummer. :[

@adellape I'm opening another PR on the Accelerators section next week. I can fix this then, if that's ok.

adellape

LGTM

adellape · 2024-12-05T18:35:32Z

/cherrypick enterprise-4.18

adellape · 2024-12-05T18:35:34Z

/cherrypick enterprise-4.17

adellape · 2024-12-05T18:35:36Z

/cherrypick enterprise-4.16

openshift-cherrypick-robot · 2024-12-05T18:36:21Z

@adellape: new pull request created: #85888

Details

In response to this:

/cherrypick enterprise-4.18

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.

openshift-cherrypick-robot · 2024-12-05T18:36:24Z

@adellape: new pull request created: #85889

Details

In response to this:

/cherrypick enterprise-4.17

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.

openshift-cherrypick-robot · 2024-12-05T18:36:29Z

@adellape: new pull request created: #85890

Details

In response to this:

/cherrypick enterprise-4.16

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.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 26, 2024

openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 26, 2024

ocpdocs-vale-bot reviewed Nov 26, 2024

View reviewed changes

StephenJamesSmith force-pushed the TELCODOCS-1956 branch 2 times, most recently from 4932764 to 7f2824d Compare November 27, 2024 17:06

ocpdocs-vale-bot reviewed Nov 27, 2024

View reviewed changes

StephenJamesSmith changed the title ~~TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce…~~ [WIP] TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… Nov 27, 2024

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 27, 2024

wabouhamad reviewed Dec 4, 2024

View reviewed changes

openshift-ci bot assigned wabouhamad Dec 4, 2024

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2024

StephenJamesSmith changed the title ~~[WIP] TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce…~~ TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… Dec 4, 2024

openshift-ci bot added telco Label for all Telco PRs and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Dec 4, 2024

lpettyjo added this to the Continuous Release milestone Dec 5, 2024

lpettyjo added branch/enterprise-4.17 branch/enterprise-4.18 labels Dec 5, 2024

lpettyjo reviewed Dec 5, 2024

View reviewed changes

lpettyjo added branch/enterprise-4.16 peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Dec 5, 2024

TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce…

6c75b8b

…lerators section

StephenJamesSmith force-pushed the TELCODOCS-1956 branch from 7f2824d to 6c75b8b Compare December 5, 2024 14:46

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2024

openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Dec 5, 2024

adellape self-assigned this Dec 5, 2024

adellape added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Dec 5, 2024

adellape reviewed Dec 5, 2024

View reviewed changes

adellape approved these changes Dec 5, 2024

View reviewed changes

adellape merged commit 5446032 into openshift:main Dec 5, 2024

openshift-cherrypick-robot mentioned this pull request Dec 5, 2024

[enterprise-4.18] TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… #85888

Merged

openshift-cherrypick-robot mentioned this pull request Dec 5, 2024

[enterprise-4.17] TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… #85889

Merged

openshift-cherrypick-robot mentioned this pull request Dec 5, 2024

[enterprise-4.16] TELCODOCS-1956: Move NVIDIA GPU architecture content to Hardware Acce… #85890

Merged

adellape removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Dec 5, 2024


		NVIDIA supports the use of graphics processing unit (GPU) resources on {product-title}. {product-title} is a security-focused and hardened Kubernetes platform developed and supported by Red Hat for deploying and managing Kubernetes clusters at scale. {product-title} includes enhancements to Kubernetes so that users can easily configure and use NVIDIA GPU resources to accelerate workloads.

		The NVIDIA GPU Operator leverages the Operator framework within {product-title} to manage the full lifecycle of NVIDIA software components required to run GPU-accelerated workloads.

Conversation

StephenJamesSmith commented Nov 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Nov 26, 2024 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Nov 26, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Nov 26, 2024 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Nov 27, 2024 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

egallen commented Nov 27, 2024

Uh oh!

bthurber commented Nov 27, 2024

Uh oh!

StephenJamesSmith commented Dec 2, 2024

Uh oh!

openshift-ci-robot commented Dec 2, 2024 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

StephenJamesSmith commented Dec 2, 2024

Uh oh!

wabouhamad left a comment

Choose a reason for hiding this comment

Uh oh!

StephenJamesSmith commented Dec 4, 2024

Uh oh!

lpettyjo left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Dec 5, 2024

Uh oh!

openshift-ci bot commented Dec 5, 2024

Uh oh!

StephenJamesSmith commented Dec 5, 2024

Uh oh!

adellape left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

StephenJamesSmith Dec 5, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

adellape left a comment

Choose a reason for hiding this comment

Uh oh!

adellape commented Dec 5, 2024

StephenJamesSmith commented Nov 26, 2024 •

edited

Loading

openshift-ci-robot commented Nov 26, 2024 •

edited by openshift-ci bot

Loading

ocpdocs-previewbot commented Nov 26, 2024 •

edited

Loading

openshift-ci-robot commented Nov 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Nov 27, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 2, 2024 •

edited by openshift-ci bot

Loading

StephenJamesSmith Dec 5, 2024 •

edited

Loading