-
Notifications
You must be signed in to change notification settings - Fork 66
Omicron dev for simulating multiple racks (Just a Bunch of Racks / JBOR) #9533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
internet-diglett
wants to merge
21
commits into
main
Choose a base branch
from
omicron-dev-for-multi-rack
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+895
−67,997
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Is this part of some plan for regional clusters we've figured out? |
Contributor
Author
Apologies for the confusion, this is primarily for allowing us to validate deployment configurations for multiple individual racks. I've updated the description accordingly. |
internet-diglett
added a commit
to oxidecomputer/maghemite
that referenced
this pull request
Jan 8, 2026
This change is primarily a part of a larger effort to make the switch zone services location aware by having them communicate with their local MGS. This is also required to allow us to deploy some form of the daemon in our test context in omicron. --- Related: * oxidecomputer/omicron#8999 * oxidecomputer/omicron#9533
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With customers managing large deployments of individual racks, it is useful to have a fast way to spin up multiple concurrent control planes with the related networking daemons for configuration validation. This also gives us an opportunity to address some of the issues noted in omicron#8999.
TODO
omicron-devor similar tool to enable deploying multiple copies of the control plane servicestopology-questmodels to drive shape / initial configuration of "JBOR" deploymentmgdorfrr) to increase configuration testing fidelityRelated: #8999