Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Sled Agent] [Bootstrap Agent] Distinguish between "package-specific" and "sled-specific" configurations #822

Open
Tracked by #824
smklein opened this issue Mar 28, 2022 · 1 comment
Open
Tracked by #824

[Sled Agent] [Bootstrap Agent] Distinguish between "package-specific" and "sled-specific" configurations #822

smklein opened this issue Mar 28, 2022 · 1 comment
Assignees
@smklein
Labels
bootstrap services For those occasions where you want the rack to turn on Sled Agent Related to the Per-Sled Configuration and Management

Comments

@smklein
Copy link
Collaborator

smklein commented Mar 28, 2022

Basically, make sure we can configure different sleds without requiring repackaging
@smklein smklein added Sled Agent Related to the Per-Sled Configuration and Management bootstrap services For those occasions where you want the rack to turn on labels Mar 28, 2022
@smklein smklein mentioned this issue Mar 28, 2022
Open
13 tasks
@smklein smklein self-assigned this Mar 28, 2022
@smklein
Copy link
Collaborator Author

smklein commented Apr 14, 2022

Perhaps, more importantly, "just shrink the config" where we can, as the control plane is capable of managing more state.

@smklein smklein mentioned this issue Apr 14, 2022
Merged
7 tasks
@jgallagher jgallagher mentioned this issue May 2, 2022
Merged
@smklein smklein mentioned this issue Jun 8, 2022
Merged
smklein added a commit that referenced this issue Jun 21, 2022
@smklein
[nexus] Split Nexus configuration (package vs deployment) (#1174)
00e8bed 
This is a major part of #822

This PR splits the Nexus configuration into "things known at package time" and "things known at deployment".

Due to hardcoded configurations, the two have historically been conflated. However, there are a number of
parameters which will only be known at deployment time, including:

- The addresses Nexus should use on the underlay (these are derived from the sled's /64, which is variable)
- The UUID of the Nexus instance (multiple Nexus instances may be executing simultaneously)
- The rack subnet
- (While it is still an IP address) the IP address of CRDB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smklein smklein

Labels
bootstrap services For those occasions where you want the rack to turn on Sled Agent Related to the Per-Sled Configuration and Management
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smklein