Skip to content

WIP: full measurements in reconfigurator#9877

Draft
labbott wants to merge 3 commits intomainfrom
labbott/full_measurement_reconfigurator
Draft

WIP: full measurements in reconfigurator#9877
labbott wants to merge 3 commits intomainfrom
labbott/full_measurement_reconfigurator

Conversation

@labbott
Copy link
Contributor

@labbott labbott commented Feb 18, 2026

This is the full stack of changes to support reference measurements. This is described more fully in RFD 512 but briefly: the goal here is to be able to distribute a set of reference measurements (hashes of what software we expect to be running on the rack) to sprockets so sprockets can appraise the measurements (compare what's actually running on the rack to the expected reference measurements).

Blueprints now have knowledge of measurements (see omicron#9718) and this PR stack is responsible for having reconfigurator update the measurements. Measurements are an artifact in the TUF repo. The high level goals here are

  • Handle going from a blueprint with Unknown measurements (the default when pulling out old blueprints) to a known set of measurements
  • Support reading measurements from the install dataset during a MUPdate override situation
  • Making sure the measurements included on each sled include all the measurements from the old TUF repo and the new TUF repo. This is the only set of software we ever expect to be running.
  • Updating the measurements before performing any other changes to the sled

Big points to check

  • MUPdate override must always work as this will be the recovery path. This will be even more important when measurements are enforced (right now it's logged but the sprockets connection continues)
  • Is this right place for measurements to come first in reconfigurator? Right now we're only measuring RoT and SP but Host OS is coming soon. Will we need changes when that happens?
  • Are there enough test cases with the reconfigurator-cli?
  • The edit counts for measurements with the sled-editor never felt quite right. Is there a better way to check?

@labbott labbott marked this pull request as draft February 18, 2026 13:35
@labbott labbott force-pushed the labbott/full_measurement_reconfigurator branch 2 times, most recently from 59f8771 to a1faf54 Compare February 24, 2026 17:38
@labbott labbott changed the base branch from main to labbott/measurement_blueprints February 24, 2026 20:46
@labbott labbott changed the base branch from labbott/measurement_blueprints to main February 24, 2026 20:47
@labbott labbott force-pushed the labbott/full_measurement_reconfigurator branch from d32f8be to b6ece6d Compare February 25, 2026 20:10
@labbott labbott changed the base branch from main to labbott/measurement_blueprints February 25, 2026 20:10
@labbott labbott changed the base branch from labbott/measurement_blueprints to main February 25, 2026 20:15
@labbott labbott force-pushed the labbott/full_measurement_reconfigurator branch from b6ece6d to 664dfa8 Compare February 25, 2026 20:37
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.

1 participant