-
Notifications
You must be signed in to change notification settings - Fork 26
NO-JIRA: JN-2789: added H200 support #131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NO-JIRA: JN-2789: added H200 support #131
Conversation
|
@MenD32: This pull request explicitly references no 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. |
elmiko
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this makes sense to me, i do wonder if we shouldn't have some warning log message when we are skipping the accelerator validation. if there is no quota, or resource exhaustion, i'm not sure the user will be able to easily detect that.
|
@MenD32 any thoughts about this question ? also, cc @damdo ptal |
damdo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
One nit
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I think this is somewhat broader then just H200 support, since this also affects other machine-types (g2, g4, a4, etc...). So I'm not sure how machine-api-provider should work with those... |
|
/retest |
damdo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
@MenD32 do you have a Jira card to track this? |
|
/hold |
|
No, where should I open one? |
|
@MenD32 probably on your team's Jira board |
|
My team doesn't currently work on RH's Jira, so IDK if there'd integration between the GitHub and the Jira instance. Nevertheless I'll create an issue |
|
@MenD32: No Jira issue with key JN-2789 exists in the tracker at https://issues.redhat.com/. 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. |
Added a JIRA ticket reference |
|
TY, I am chatting internally to see how best we test/verify this cc. @elmiko |
|
Thanks for rebasing @MenD32 It looks like you created a merge commit for this, whereas we normally do a full rebase instead. |
Signed-off-by: Amit Mendelevitch <[email protected]>
Co-authored-by: Damiano Donati <[email protected]>
de6fa97 to
495f894
Compare
for some reason it still wanted a merge after the rebase, I just redid the rebase and now it seems that its fine |
damdo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/unhold
|
/jira refresh |
|
@damdo: No Jira issue with key JN-2789 exists in the tracker at https://issues.redhat.com/. 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. |
|
@damdo: The referenced Jira(s) [JN-2789] could not be located, all automatically applied jira labels will be removed. 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. |
|
@sunzhaohua2: This PR has been marked as verified by 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. |
|
@MenD32: This pull request explicitly references no 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. |
|
Adding NO-JIRA as JN-2789 is not picked up by the OCP robot |
|
/tide refresh |
Currently OpenShift cannot create H200 machines since they are part of the
a3machineFamily but don't have a quota in the gcp compute library.