MIG GPU topic #313
MIG GPU topic #313
Conversation
|
First-draft PR, for when we are ready to move forward. cc: @nwneisen |
| 1. Obtain the default MKE 4 configuration file: | ||
|
|
||
| ``` | ||
| mkectl init |
There was a problem hiding this comment.
Redirect the output to actually save it to a file mkectl init > mke4.yaml
| mkectl apply -f <mke-configuration-file> | ||
| ``` | ||
|
|
||
| 4. Optional. You can apply a profile to a node using the `nvidia.com/mig.config: |
There was a problem hiding this comment.
This is the part that is a little up in the air for this. I don't think the profiles are optional and when a node doesn't have one, MIG will just stay disabled on that node.
I'm also trying to think if there is a way for us to do this for them. For example, if they are in single mode and provide a profile in the mke config, we apply it to all their GPU nodes. But then we will likely run in to customers who don't want all their GPUs to be MIG. And then there's handling mixed mode..
No changes ATM but this is the part of MIG that is still in flux
No description provided.