-
Notifications
You must be signed in to change notification settings - Fork 59
Support measurement_corpus #7906
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -251,6 +251,8 @@ pub enum WriteError { | |
#[source] | ||
error: Box<NestedEngineError<ControlPlaneZonesSpec>>, | ||
}, | ||
#[error("error creating directory: {error}")] | ||
CreateDirError { error: std::io::Error }, | ||
} | ||
|
||
impl From<NestedEngineError<ControlPlaneZonesSpec>> for WriteError { | ||
|
@@ -297,6 +299,12 @@ pub enum ControlPlaneZonesStepId { | |
/// Writing the MUPdate override file. | ||
MupdateOverride, | ||
|
||
/// Creating Measurement directory | ||
CreateMeasurementDir, | ||
|
||
/// Writing a measurement corpus | ||
MeasurementCorpus { name: String }, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this structure precludes anything I'm about to say. I'm just writing a note as I think about this. We've talked about stacking multiple versioned corpuses so each TUF repo doesn't need to include the measurements for all versions. This would allow us to check for version N and N-1 measurement values without having to put both of them in one TUF repo. However, for installinator, for a mupdate of a single sled on an existing rack, we'd probably want to be able to include the last few versions of measurements in a TUF repo or have some other way to stack when doing a fresh install. The problem with the former is that we won't always require strict release upgrading from version N-1 to N in the future. The problem with the latter is we now need to be able to source the different manifests from wicket. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Including previous versions of measurements in a TUF repo would get a little tricky and require some manual hand holding unless our automation gets a lot smarter. What I was planning to do is rotate the measurements from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Makes sense. As long as we can handle sleds running either old (for some specific set of old) or new software, this should work fine. |
||
|
||
/// Writing the zone manifest. | ||
ZoneManifest, | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.