Skip to content

fix: bump max instance vcpu to 254#3108

Merged
david-crespo merged 1 commit intomainfrom
sudomateo-patch-1
Mar 6, 2026
Merged

fix: bump max instance vcpu to 254#3108
david-crespo merged 1 commit intomainfrom
sudomateo-patch-1

Conversation

@sudomateo
Copy link
Contributor

@sudomateo sudomateo commented Mar 6, 2026

The Oxide control plane already supports 254 vCPUs per instance as of oxidecomputer/omicron#9385, Turin only of course. Bumped the console code to match.

Closes #3109

@vercel
Copy link

vercel bot commented Mar 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
console Ready Ready Preview Mar 6, 2026 5:00pm

Request Review

The Oxide control plane already supports 254 vCPUs per instance as
of oxidecomputer/omicron#9385, Turin only of
course. Bumped the console code to match.

Closes #3109
@david-crespo
Copy link
Collaborator

david-crespo commented Mar 6, 2026

Thanks! As we discussed in DMs, I had this in #2974 and then we bumped it back down to 128 since we hadn't shipped any 254 thread sleds yet. That was January, so I guess the plan was to bump it back up pretty soon, and it seems we failed to schedule that.

@david-crespo david-crespo merged commit 557e093 into main Mar 6, 2026
7 checks passed
@david-crespo david-crespo deleted the sudomateo-patch-1 branch March 6, 2026 17:09
@AlejandroME AlejandroME added this to the 19 milestone Mar 6, 2026
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.

Support 254 vCPUs per instance

3 participants