openshift-docs
openshift-docs copied to clipboard
openshift
[WIP]TELCODOCS-1957: Hardware accelerator overview
[TELCODOCS-1957]: Hardware accelerator overview
Jira: https://issues.redhat.com/browse/TELCODOCS-1957
Version(s): openshift-4.17, openshift-4.16.z
Link to docs preview: https://82500--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
SME: @egallen QE: @bthurber
@StephenJamesSmith: This pull request references TELCODOCS-1957 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.18." or "openshift-4.18.", but it targets "openshift-4.17" instead.
In response to this:
[TELCODOCS-1957]: Hardware accelerator overview
Jira: https://issues.redhat.com/browse/TELCODOCS-1957
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.
🤖 Fri Nov 22 15:24:48 - Prow CI generated the docs preview:
https://82500--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
@StephenJamesSmith: This pull request references TELCODOCS-1957 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.18." or "openshift-4.18.", but it targets "openshift-4.17" instead.
In response to this:
[TELCODOCS-1957]: Hardware accelerator overview
Jira: https://issues.redhat.com/browse/TELCODOCS-1957
Version(s): openshift-4.17, openshift-4.16.z
Link to docs preview: https://82500--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
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 @bthurber Latest changes added. Still waiting for graphic.
@soflaher Please review and vet for terminology issues. Thx!
Ack, am following up with Rob and Erwan and will get back to you as soon as we agree on the most accurate description.
@StephenJamesSmith response from Rob:
I'm not certain I have the full context, however I can share that I would avoid the validated accelerators statement. ...also I would guide to avoid the word vendor when we are talking about a partner. If the company in question is a partner we should use the word partner i.e. nvidia, amd, intel qualcomm, amazon, ibm are all partners. I can also share that OpenShift AI does not itself include any support for the accelerator hardware. the support for the accelerator hardware comes from the partners in their own software and so they have to validate that their software&hardware are achieveing the desired behaviors.
In RHEL AI, Red Hat is using the partners as a supplier and including their bits in our software product. I have not seen how support actually plays out yet in RHEL AI. Also in RHEL AI, today the hardware systems are published as vendor validated
We are working on moving towards a certification but there are several gaps, which are being addressed
Given Rob's input and @bthurber 's above, some considerations for terminology:
- OpenShift can't follow terminology that OpenShift AI is doing
- Rob recommends using "partner" where someone is a partner, instead of vendor.
- We need to be clear that the partner owns their part of the validation of their stack where our stuff is being used (or at least ensure we aren't explicitly stating support where the onus is on partners)
- Would "partner validated" possibly work?: Red Hat OpenShift provides accelerator tools that enable the following partner-validated hardware accelerators (or maybe "[RH OCP] provides accelerator tools that the following partners validate with their hardware accelerators"?
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@StephenJamesSmith: This pull request references TELCODOCS-1957 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.18." or "openshift-4.18.", but it targets "openshift-4.17" instead.
In response to this:
[TELCODOCS-1957]: Hardware accelerator overview
New main topic.
Jira: https://issues.redhat.com/browse/TELCODOCS-1957
Version(s): openshift-4.17, openshift-4.16.z
Link to docs preview: https://82500--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
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.
@StephenJamesSmith: This pull request references TELCODOCS-1957 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.18." or "openshift-4.18.", but it targets "openshift-4.17" instead.
In response to this:
[TELCODOCS-1957]: Hardware accelerator overview
New main topic. This Assembly will contain included subtopics for hardware accelerators such as NVIDIA, AMD, Intel, and others as they are developed.
Jira: https://issues.redhat.com/browse/TELCODOCS-1957
Version(s): openshift-4.17, openshift-4.16.z
Link to docs preview: https://82500--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/about-hardware-accelerators.html
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.
@StephenJamesSmith: 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.
@adellape: new pull request created: #85352
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.
@adellape: new pull request created: #85353
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.
@adellape: new pull request created: #85354
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.