feat(deploy_tee): genesis-ceremony polls for cohort readiness#55
Merged
Conversation
The ceremony's two probes — each node's reth serving block 0 and
summit's getPublicKeys — only answer after a node finishes its
root_key → LUKS open → summit keygen boot tail, and both previously
read once and aborted, so the operator had to hand-time the ceremony
against the slowest node. Both probes now poll until every node
answers (5s interval, 15 min ceiling, pending-list progress every
30s), making the ceremony itself the cohort barrier: it can run
straight after `configure` in one sitting.
One deliberate asymmetry: an unreachable node is retried (that's the
normal boot tail), but a node that *answers* with the wrong genesis
hash fails immediately with the full per-node ✓/✗ listing — waiting
can't fix a node booted from a stale image or different genesis.
README, from the first 4-node founding: show cohort configure
(--genesis/--join) as the founding path, document the ceremony's
readiness wait, note tdx-init's one-shot listener ("listener never
came up" on an already-configured node means reboot it first), and
record the stack-per-node provisioning rationale.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The ceremony's two probes — each node's reth serving block 0 and summit's getPublicKeys — only answer after a node finishes its root_key → LUKS open → summit keygen boot tail, and both previously read once and aborted, so the operator had to hand-time the ceremony against the slowest node. Both probes now poll until every node answers (5s interval, 15 min ceiling, pending-list progress every 30s), making the ceremony itself the cohort barrier: it can run straight after
configurein one sitting.One deliberate asymmetry: an unreachable node is retried (that's the normal boot tail), but a node that answers with the wrong genesis hash fails immediately with the full per-node ✓/✗ listing — waiting can't fix a node booted from a stale image or different genesis.
README, from the first 4-node founding: show cohort configure (--genesis/--join) as the founding path, document the ceremony's readiness wait, note tdx-init's one-shot listener ("listener never came up" on an already-configured node means reboot it first), and record the stack-per-node provisioning rationale.