Orchestrator spec and reference impl#357
Conversation
| AwaitingReady --> Recovering : VerificationFailed [required]\n/ RestoreGoldenImage | ||
|
|
||
| state Operational { | ||
| [*] --> Ready |
There was a problem hiding this comment.
Can you elaborate on why this is a valid starting point? I see why PowerOnReset starts the process, but I do not get how the prior steps can be skipped to takt this, second entry point?
There was a problem hiding this comment.
I've dropped the [*] --> Ready line from the diagram — it wasn't adding information the diagram doesn't already show explicitly elsewhere (PreSupervision --> Ready and AwaitingReady --> Ready), and removing it
avoids the misreading. misleading as drawn. The only real initial pseudostate is at the top of the diagram:
[*] --> PowerOnReset. That's the sole entry — every run starts there
|
Do you plan to realize your state machine implementation based on https://github.com/typeconstructor/rot-reducer? |
|
Hi, @leongross , yes I am typeconstructor |
Add two new documents — a narrative walkthrough of the orchestrator state machine (orchestrator-sm-walkthru.md) and a reference transitions table (orchestrator-sm-transitions.md) — and expand the existing state machine document with superstate handler descriptions. Register both new pages in SUMMARY.md.
2 participants
No description provided.