Skip to content

[JarvisLabs] Support RTX PRO 6000; update API endpoint; remove spot offers#235

Merged
peterschmidt85 merged 2 commits into
mainfrom
jarvislabs-rtx-pro-6000
Jun 11, 2026
Merged

[JarvisLabs] Support RTX PRO 6000; update API endpoint; remove spot offers#235
peterschmidt85 merged 2 commits into
mainfrom
jarvislabs-rtx-pro-6000

Conversation

@peterschmidt85

@peterschmidt85 peterschmidt85 commented Jun 8, 2026

Copy link
Copy Markdown
Contributor
  • Add JarvisLabs RTX PRO 6000 catalog support.
  • Normalize RTX PRO 6000 as RTXPRO6000 and store the original JarvisLabs GPU type in provider_data when needed.
  • Use backendn.jarvislabs.net for JarvisLabs offer discovery. JarvisLabs confirmed backendprod.jarvislabs.net and backendn.jarvislabs.net now point to the same region and function identically.
  • Do not emit JarvisLabs spot VM offers. JarvisLabs confirmed spot instances are only supported for containers/templates, not VMs.

@peterschmidt85 peterschmidt85 changed the title Add JarvisLabs RTX PRO 6000 support Add JarvisLabs RTX PRO 6000 support; fix discovery endpoint Jun 8, 2026
@peterschmidt85 peterschmidt85 requested a review from jvstme June 8, 2026 19:10
@peterschmidt85 peterschmidt85 force-pushed the jarvislabs-rtx-pro-6000 branch from 5e97532 to f5fd15c Compare June 9, 2026 12:16
@peterschmidt85 peterschmidt85 changed the title Add JarvisLabs RTX PRO 6000 support; fix discovery endpoint Add JarvisLabs RTX PRO 6000 support; update discovery endpoint Jun 9, 2026
@peterschmidt85 peterschmidt85 changed the title Add JarvisLabs RTX PRO 6000 support; update discovery endpoint Add JarvisLabs RTX PRO 6000 support; fix discovery endpoint Jun 9, 2026
@peterschmidt85 peterschmidt85 force-pushed the jarvislabs-rtx-pro-6000 branch from f5fd15c to 5e97532 Compare June 9, 2026 12:21
@peterschmidt85 peterschmidt85 force-pushed the jarvislabs-rtx-pro-6000 branch from 5e97532 to e5dd10d Compare June 9, 2026 12:32
@peterschmidt85 peterschmidt85 changed the title Add JarvisLabs RTX PRO 6000 support; fix discovery endpoint Add JarvisLabs RTX PRO 6000 support; update discovery endpoint Jun 9, 2026
@peterschmidt85 peterschmidt85 changed the title Add JarvisLabs RTX PRO 6000 support; update discovery endpoint [JarvisLabs] Support RTX PRO 6000; update API endpoint; remove spot offers Jun 9, 2026
Comment on lines +245 to +246
if gpu_name == gpu_type and any(c.isspace() for c in gpu_type):
return None

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nit) Now that you pass gpu_type in provider_data, it should be possible to normalize GPU names with spaces instead of skipping them (like you suggested in the initial JarvisLabs PR versiom)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’d prefer to keep this fail-closed. provider_data["gpu_type"] solves the create-time token issue once we have a reviewed mapping, but it does not make arbitrary spaced GPU names safe to canonicalize. For example, blindly stripping spaces would map RTX A6000 to RTXA6000, while gpuhunt uses A6000.

So I kept unmapped spaced JarvisLabs GPU types skipped with a warning and renamed the warning from “ambiguous” to “unmapped”. For any spaced JarvisLabs token we verify, we can add an explicit mapping.

@peterschmidt85 peterschmidt85 merged commit d58a4a9 into main Jun 11, 2026
5 checks passed
@peterschmidt85 peterschmidt85 deleted the jarvislabs-rtx-pro-6000 branch June 11, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants