Steps to reproduce
Configure the oci backend and run dstack apply with a run that requests an H100 (or H200, L40S, A100-v2, B200, B300, RTX PRO 6000) in a region and tenancy that has quota for it.
Actual behaviour
No OCI offer is ever selected for those GPUs. SUPPORTED_SHAPE_FAMILIES in src/dstack/_internal/core/backends/oci/compute.py still lists only the shapes that existed when Bare Metal support landed (#1325): BM.GPU3., BM.GPU4., BM.GPU.A10. plus the VM families. Every newer shape that gpuhunt already catalogs (BM.GPU.H100.8, BM.GPU.H200.8, BM.GPU.L40S.4, BM.GPU.A100-v2.8, BM.GPU.B200.8) is filtered out by _supported_instances. #2343 asked for H100 and was closed as non-priority; its blocker (Fabric Manager, #2348) was fixed in #2355, so the images now install open kernel modules and Fabric Manager.
Separately, the gpuhunt OCI provider dropped OCI's AMD shapes and the newest NVIDIA shapes, and published GB200 under its display name (fix in dstackai/gpuhunt#262).
Expected behaviour
Runs that request these GPUs get OCI offers when the tenancy has quota. We run OCI GPU capacity (A10 and A100 today, H100-class shapes on the roadmap) and want to schedule it through dstack rather than by hand.
dstack version
master (branch off 68e701d0's parent)
Additional information
I have a change ready that adds the x86-64 NVIDIA families to the allowlist and records why AMD (no ROCm image) and Grace GB200/GB300 (arm64 hosts, x86 images only) stay out, plus a note on why SUPPORTED_REGIONS is fixed (the Marketplace listings carrying the dstack images are regional). PR to follow.
Steps to reproduce
Configure the
ocibackend and rundstack applywith a run that requests an H100 (or H200, L40S, A100-v2, B200, B300, RTX PRO 6000) in a region and tenancy that has quota for it.Actual behaviour
No OCI offer is ever selected for those GPUs.
SUPPORTED_SHAPE_FAMILIESinsrc/dstack/_internal/core/backends/oci/compute.pystill lists only the shapes that existed when Bare Metal support landed (#1325):BM.GPU3.,BM.GPU4.,BM.GPU.A10.plus the VM families. Every newer shape that gpuhunt already catalogs (BM.GPU.H100.8,BM.GPU.H200.8,BM.GPU.L40S.4,BM.GPU.A100-v2.8,BM.GPU.B200.8) is filtered out by_supported_instances. #2343 asked for H100 and was closed as non-priority; its blocker (Fabric Manager, #2348) was fixed in #2355, so the images now install open kernel modules and Fabric Manager.Separately, the gpuhunt OCI provider dropped OCI's AMD shapes and the newest NVIDIA shapes, and published GB200 under its display name (fix in dstackai/gpuhunt#262).
Expected behaviour
Runs that request these GPUs get OCI offers when the tenancy has quota. We run OCI GPU capacity (A10 and A100 today, H100-class shapes on the roadmap) and want to schedule it through dstack rather than by hand.
dstack version
master (branch off
68e701d0's parent)Additional information
I have a change ready that adds the x86-64 NVIDIA families to the allowlist and records why AMD (no ROCm image) and Grace GB200/GB300 (arm64 hosts, x86 images only) stay out, plus a note on why
SUPPORTED_REGIONSis fixed (the Marketplace listings carrying the dstack images are regional). PR to follow.