Skip to content

Instance jumbo frames setting#3235

Draft
david-crespo wants to merge 4 commits into
mainfrom
instance-jumbo-frames
Draft

Instance jumbo frames setting#3235
david-crespo wants to merge 4 commits into
mainfrom
instance-jumbo-frames

Conversation

@david-crespo
Copy link
Copy Markdown
Collaborator

WIP to get a feel for it. See oxidecomputer/omicron#10472. It's pretty good as-is — the worst part is that we don't currently have a way of fetching the system-level jumbo frames setting, which would let us hide this setting on the instance page if it was off system-wide (probably true for the majority of users). It feels bad to have a setting on the page that will never work, but at least the copy makes it reasonably clear. We could either add a silo-level network settings endpoint that makes this setting available to end users OR cheat by making the system-level endpoint readable by any logged-in user.

image

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 2, 2026

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

Project Deployment Actions Updated (UTC)
console Ready Ready Preview Jun 2, 2026 5:08pm

Request Review

@benjaminleonard
Copy link
Copy Markdown
Contributor

Rather than making the system endpoint accessible, can we add some sort of environment endpoint that plumbs it through for developers also.

One other example could be the cpu_platform. Perhaps we expose if Turin or Milan are available to specify.

@david-crespo
Copy link
Copy Markdown
Collaborator Author

Yeah, that’s interesting. My instinct is to avoid putting together networking and CPU settings in the same endpoint, but it would also be silly to have 3 different endpoints with one setting each.

The new jumbo frames settings card adds a second Save button to the
instance settings tab, so the bare getByRole('button', { name: 'Save' })
in instance-auto-restart.e2e.ts hit a strict-mode violation in CI.
david-crespo added a commit that referenced this pull request Jun 3, 2026
…rue (#3238)

Straightforward. The interesting bit here is the addition of an
`msw-flags` cookie that we can use in the test to flip `contact_support:
true` instead of hang it off a particular test user, which I tried and
felt wrong. We can also use it for the jumbo frames setting in #3235
until we have an operator UI for flipping the setting (which we should
probably have?).

## `contact_support: false`

<img width="1210" height="860" alt="image"
src="https://github.com/user-attachments/assets/bedb6e0f-ceef-47d0-a938-85f9449451d0"
/>


## `contact_support: true`

<img width="1211" height="862" alt="image"
src="https://github.com/user-attachments/assets/c35996b4-2c1c-41b7-80ca-141418db833c"
/>
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