every new system should have a target blueprint #5222
Assignees
Comments
jgallagher
added a commit
that referenced
this issue
Mar 15, 2024
) I would like to test that after an RSS handoff, the initial blueprint we created in RSS and set in the Nexus handoff matches the blueprint we would generate from the first inventory collections. I can do that by hand on `madrid`, but I'm not sure there's a good way to do that in an automated test. Is this something I could lean on a4x2 to check? This does not modify the `services` table or the `services` field of the RSS handoff. Removing those will come in a followup PR that will need an accompanying note for deployed systems (i.e., instructions to set a blueprint so the current users of `services` will continue to function by checking the current target blueprint). Closes #5222.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blueprints represent the canonical configuration of various subsystems, like the set of Omicron zones deployed on sleds. Every system should have one.
On today's ad hoc update call we discussed a plan where RSS would construct a Blueprint describing its ServicePlan and pass that off to Nexus during the initial handoff. This would then be made the initial target blueprint, presumably disabled. This way, we could always assume a system has a target blueprint.
The text was updated successfully, but these errors were encountered: