TQ: Support persisting state to ledger #9310
Merged
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
andrewjstone
force-pushed
the
tq-sprockets-3
branch
from
e727dea to
b19f5cf
Compare
This was referenced Oct 29, 2025
andrewjstone
force-pushed
the
tq-sprockets-2
branch
from
a505cda to
1ac30a3
Compare
andrewjstone
force-pushed
the
tq-sprockets-3
branch
from
b19f5cf to
d1d409c
Compare
andrewjstone
force-pushed
the
tq-sprockets-2
branch
from
4b86d87 to
0ef9d1e
Compare
pietroalbini
approved these changes
Nov 3, 2025
Builds on #9296 This commit persists state to a ledger, following the pattern used in the bootstore. It's done this way because the `PersistentState` itself is contained in the sans-io layer, but we must save it in the async task layer. The sans-io layer shouldn't know how the state is persisted, just that it is, and so we recreate the ledger for every time we write it. A follow up will PR will deal with the early networking information saved by the bootstore, and will be very similar.
andrewjstone
force-pushed
the
tq-sprockets-3
branch
from
ee4485d to
ca8a905
Compare
andrewjstone
added a commit
that referenced
this pull request
Nov 4, 2025
This builds on #9310 This code essentially re-implements the bootstore implementation of early network config replication over sprockets channels. The persistence code of this state still lives in the bootstore, but will eventually move to the `trust-quorum` crate once all customer systems are running only trust quorum. This code does not deal with how the switchover from bootstore to to trust-quorum is made. That will come later with trust-quorum / sled-agent integration.
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.
Builds on #9296
This commit persists state to a ledger, following the pattern used in the bootstore. It's done this way because the
PersistentStateitself is contained in the sans-io layer, but we must save it in the async task layer. The sans-io layer shouldn't know how the state is persisted, just that it is, and so we recreate the ledger for every time we write it.A follow up will PR will deal with the early networking information saved by the bootstore, and will be very similar.