Skip to content

Instantly share code, notes, and snippets.

@pimlock
Created September 19, 2026 00:36
Show Gist options
  • Select an option

  • Save pimlock/5e51d4eddfd1303730d57f7674f466b8 to your computer and use it in GitHub Desktop.

Select an option

Save pimlock/5e51d4eddfd1303730d57f7674f466b8 to your computer and use it in GitHub Desktop.
OpenShell PR 3273: durable configuration completion architecture and interaction flows

Durable configuration completion — PR #3273

PR #3273 · head 262be8a9e8a42ae4363e8602193b620c60740a76 · stacked on #3265 · part of #1731.

A successful database write means the desired configuration is durable. It does not mean the sandbox has applied it. This PR gives a sandbox-scoped policy/settings update a durable operation that records what happened after the write.

1. Boundaries

flowchart LR
    C[CLI or SDK] --> G[Gateway: authorize and validate]
    G --> T[Database transaction]
    T --> D[(Desired state + operation)]
    D --> R[Indexed operation reconciler]
    G --> Q[Bounded delivery queue]
    R --> Q
    Q --> B[Build current snapshot and associate exact target]
    B --> S[Authenticated supervisor stream]
    S --> A[Supervisor applies configuration]
    A --> V[Gateway validates result correlation]
    V --> O[(Commit terminal operation)]
    O --> W[Wake waiter or read operation]
    W --> C
Loading

The database transaction covers desired state, relevant sandbox metadata/resource-version checks and the operation. Network delivery and runtime application happen afterward. No database transaction remains open while waiting for the supervisor.

#3265 supplies streamed delivery, admission, provider readiness and request replay. #3273 adds durable policy/settings completion and recovery around that delivery path. Provider receipts share a storage envelope but use separate completion logic and stay outside sandbox-operation retry indexes. Global updates do not receive this sandbox-operation contract and reject WAIT_FOR_COMPLETION.

2. One update, two return points

sequenceDiagram
    participant C as Caller
    participant G as Gateway
    participant D as Database
    participant S as Supervisor
    C->>G: UpdateConfig(policy/settings, consistency, request_id)
    G->>G: Authorize scope and validate mutation and wait mode
    G->>D: Atomically commit desired state + operation
    D-->>G: Operation identity
    G->>D: Record mutation replay response before waiting
    alt COMMIT_ONLY or unspecified
        G-->>C: Committed response + operation
    else WAIT_FOR_COMPLETION
        G->>G: Subscribe and check durable operation
    end
    G->>G: Build snapshot and associate exact target before send
    G->>S: Configuration update (update ID, sequence, revision)
    S->>S: Apply and determine outcome
    S-->>G: Correlated component result
    G->>G: Validate current session and result correlation
    G->>D: CAS terminal operation for matching target
    G->>G: Notify local waiters after commit
    opt Waiting caller is still connected
        G-->>C: Terminal state and apply outcome
    end
Loading

The diagram shows logical stages; commit-only callers may receive their response before delivery starts. Mutation replay is recorded separately from the desired-state transaction and before the caller's completion wait. request_id replays admission; the sandbox-scoped idempotency_key identifies the original operation. They are distinct contracts. Wait preferences do not change mutation identity.

WAIT_FOR_COMPLETION replaces the WAIT_FOR_APPLY symbol at wire value 2. “Completion” includes failure, supersession, cancellation and inactivity. The protobuf field remains named consistency, but selects the return point rather than a database isolation level. wait_timeout is a protobuf Duration; zero uses the server default of 60 seconds.

3. Completion is more than success

stateDiagram-v2
    [*] --> Pending: active sandbox mutation commits
    Pending --> Applied: Applied / IgnoredDuplicate / Degraded
    Pending --> Superseded: newer target or IgnoredStale
    Pending --> Failed: rejected or unsupported apply result
    Pending --> Inactive: sandbox stopped or completed
    Pending --> Cancelled: sandbox deleting or deleted
    [*] --> Inactive: inactive at admission
    [*] --> Cancelled: deleting at admission
Loading

State and outcome are separate: Applied with outcome Degraded must remain visible to the caller. RetainedLocalOverride, FailedRetainedLastKnownGood, FailedClosed, Unsupported and an unspecified apply outcome map to Failed. An operation reaches its terminal state through a conditional durable update; a stale result cannot complete a different target.

The snapshot's config_revision is an equality token. Policy/settings revisions provide the ordered desired-state targets; the opaque token is not a sequence number.

4. Timeout, restart and unchanged updates

flowchart TD
    P[(Committed pending operation)] --> T[RPC wait times out or client disconnects]
    T --> K[Operation remains durable]
    K --> R[Indexed reconciler claims due work with CAS]
    R --> Q[Queue latest snapshot for the sandbox]
    Q --> M{Target still matches?}
    M -->|Newer desired target| X[Superseded]
    M -->|Matches| S[Send and await correlated result]
    S --> F[(Persist terminal outcome)]
    F --> G[Read operation or replay request]
Loading

A wait timeout does not cancel or roll back the committed mutation. A caller can look up the operation; a retry with the same request identity can recover its committed response and choose commit-only behavior. Local notifications reduce latency; database polling lets waiters observe completion across gateway replicas or restarts. Recovery scans indexed due work in bounded batches and uses conditional claims/retry deadlines. Delivery may coalesce or repeat; there is no exactly-once network delivery guarantee.

An unchanged policy/settings request still creates a durable operation targeting the existing revisions. It allocates no new desired-state revision. A matching pending operation requires an acknowledgement even if the session already acknowledged an identical snapshot; ordinary duplicate suppression must not strand this new waiter.

5. Startup and security boundaries

Protocol revision 3 is required between this gateway and supervisor. Configuration preparation/admission and runtime readiness remain separate: accepting startup configuration does not itself mark the sandbox Ready. The supervisor launches the workload/relay and sends SupervisorRuntimeReady for the current activated configuration/session.

Operation lookup is workspace-authorized. Operation records retain revision identifiers, state/outcome, timestamps and bounded sanitized errors, not configuration or credential payloads. Provider credentials can exist in the in-memory/transport snapshot and must not be copied into the operation or diagnostic artifacts.

Source map

This explanation is pinned to the head above. It describes control flow and invariants, not a performance benchmark. pr-3273-summary.html in this gist provides standalone diagrams without external scripts.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>PR 3273 — Durable configuration completion</title><style>body{margin:0;background:#0d1117;color:#e6edf3;font:16px/1.65 system-ui,sans-serif}header,main{max-width:1120px;margin:auto;padding:28px}h1{font-size:36px;line-height:1.2}h2{margin-top:38px}a{color:#79c0ff}code{color:#a5d6ff;overflow-wrap:anywhere}figure,.card{margin:20px 0;padding:18px;background:#161b22;border:1px solid #30363d;border-radius:12px}svg{width:100%;height:auto;min-width:760px}svg text{fill:#e6edf3;font:17px system-ui,sans-serif}svg .edge{font-size:14px;fill:#9aa7b4}.diagram{overflow-x:auto}figcaption,.meta{color:#9aa7b4;font-size:14px}nav{display:flex;gap:18px;flex-wrap:wrap}li{margin:8px 0}footer{border-top:1px solid #30363d;padding:24px 0} @media(max-width:600px){header,main{padding:18px}h1{font-size:28px}figure{padding:8px}}</style></head><body><header><p class="meta">NVIDIA / OpenShell · PR #3273 · ready for review · 2026-09-18</p><h1>Durable configuration completion</h1><p>Commit the intent. Track what the sandbox actually did.</p><p class="meta">Head <code>262be8a9e8a42ae4363e8602193b620c60740a76</code><br>Stack: #3244 → #3265 → #3273 · Issue #1731</p><p><a href="https://github.com/NVIDIA/OpenShell/pull/3273">Pull request</a> · <a href="https://github.com/NVIDIA/OpenShell/pull/3265">Parent PR</a></p></header><main><nav><a href="#boundaries">Boundaries</a><a href="#flow">Interaction flow</a><a href="#states">Outcomes</a><a href="#recovery">Recovery</a><a href="#sources">Source map</a></nav><div class="card">A database commit makes desired policy/settings durable. This PR adds a durable operation so callers can also observe runtime completion. <code>WAIT_FOR_COMPLETION</code> can finish with success, degradation, failure, supersession, inactivity or cancellation.</div>
<section id="boundaries"><h2>1. The transaction ends before delivery</h2><figure><div class="diagram"><svg viewBox="0 0 1080 350" role="img" aria-label="Durable write and asynchronous completion"><title>Durable write and asynchronous completion</title><defs><marker id="arrow0" markerWidth="9" markerHeight="9" refX="8" refY="4" orient="auto"><path d="M0,0 L8,4 L0,8" fill="#58a6ff"/></marker></defs><path d="M230,85 L310,85" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow0)"/><path d="M570,85 L690,85" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow0)"/><text x="630.0" y="76.0" text-anchor="middle" class="edge">commit</text><path d="M865,125 L865,240" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow0)"/><text x="865.0" y="173.5" text-anchor="middle" class="edge">async</text><path d="M690,280 L570,280" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow0)"/><text x="630.0" y="271.0" text-anchor="middle" class="edge">result</text><path d="M310,280 L230,280" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow0)"/><rect x="20" y="45" width="210" height="80" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="125.0" y="79.0" text-anchor="middle">Caller</text><text x="125.0" y="103.0" text-anchor="middle">CLI / SDK</text><rect x="310" y="45" width="260" height="80" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="440.0" y="79.0" text-anchor="middle">Gateway</text><text x="440.0" y="103.0" text-anchor="middle">Authorize + validate</text><rect x="690" y="45" width="350" height="80" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="865.0" y="79.0" text-anchor="middle">One database transaction</text><text x="865.0" y="103.0" text-anchor="middle">Desired state + operation</text><rect x="690" y="240" width="350" height="80" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="865.0" y="274.0" text-anchor="middle">Delivery + supervisor</text><text x="865.0" y="298.0" text-anchor="middle">Build → send → apply</text><rect x="310" y="240" width="260" height="80" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="440.0" y="274.0" text-anchor="middle">Database</text><text x="440.0" y="298.0" text-anchor="middle">Terminal operation</text><rect x="20" y="240" width="210" height="80" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="125.0" y="274.0" text-anchor="middle">Caller</text><text x="125.0" y="298.0" text-anchor="middle">Wait / read result</text></svg></div><figcaption>Blue: delivery/control flow. Green: durable records and returned results. Amber: alternate paths and outcomes.</figcaption></figure><p>Desired state, relevant sandbox metadata/resource-version checks and the operation commit atomically in SQLite or PostgreSQL. Network delivery and application happen afterward. #3265 supplies streamed delivery, admission, provider readiness and request replay; #3273 adds durable sandbox policy/settings completion.</p><p>Global updates reject this wait mode. Provider receipts share storage infrastructure but keep separate completion logic and are excluded from sandbox retry indexes.</p></section>
<section id="flow"><h2>2. One update, two return points</h2><figure><div class="diagram"><svg viewBox="0 0 1080 450" role="img" aria-label="One update through commit, delivery and completion"><title>One update through commit, delivery and completion</title><defs><marker id="arrow1" markerWidth="9" markerHeight="9" refX="8" refY="4" orient="auto"><path d="M0,0 L8,4 L0,8" fill="#58a6ff"/></marker></defs><path d="M275,90 L275,135" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow1)"/><path d="M520,170 L560,170" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow1)"/><path d="M275,205 L275,250" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow1)"/><path d="M540,310 L540,355" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow1)"/><rect x="30" y="30" width="1020" height="60" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="540.0" y="66.0" text-anchor="middle">1 Authorize workspace, resolve sandbox, validate policy/settings</text><rect x="30" y="135" width="490" height="70" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="275.0" y="164.0" text-anchor="middle">2 Atomic desired-state + operation commit</text><text x="275.0" y="188.0" text-anchor="middle">Then record request replay response</text><rect x="560" y="135" width="490" height="70" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="805.0" y="164.0" text-anchor="middle">COMMIT_ONLY: return operation</text><text x="805.0" y="188.0" text-anchor="middle">WAIT_FOR_COMPLETION: keep waiting</text><rect x="30" y="250" width="1020" height="60" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="540.0" y="286.0" text-anchor="middle">3 Build snapshot → associate exact target → send to current supervisor session</text><rect x="30" y="355" width="1020" height="60" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="540.0" y="391.0" text-anchor="middle">4 Apply → validate correlated result → CAS terminal record → notify waiter</text></svg></div><figcaption>The sequence is logical: asynchronous delivery may overlap the caller's response.</figcaption></figure><p><code>COMMIT_ONLY</code> returns after commit; <code>WAIT_FOR_COMPLETION</code> waits for a terminal operation. The operation identity is captured in request replay before waiting. <code>request_id</code> governs replay admission; the sandbox-scoped <code>idempotency_key</code> identifies the original operation. Wait preferences do not change mutation identity.</p><p>The new symbol replaces <code>WAIT_FOR_APPLY</code> at wire value 2. The field remains named <code>consistency</code>, but selects a completion boundary, not database isolation. <code>wait_timeout</code> is a protobuf Duration; zero defaults to 60 seconds.</p></section>
<section id="states"><h2>3. Completion does not always mean applied</h2><figure><div class="diagram"><svg viewBox="0 0 1080 330" role="img" aria-label="Pending operations have five terminal states"><title>Pending operations have five terminal states</title><defs><marker id="arrow2" markerWidth="9" markerHeight="9" refX="8" refY="4" orient="auto"><path d="M0,0 L8,4 L0,8" fill="#58a6ff"/></marker></defs><path d="M540,90 L112,200" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow2)"/><path d="M540,90 L322,200" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow2)"/><path d="M540,90 L540,200" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow2)"/><path d="M540,90 L757,200" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow2)"/><path d="M540,90 L967,200" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow2)"/><rect x="390" y="25" width="300" height="65" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="540.0" y="63.5" text-anchor="middle">Pending</text><rect x="20" y="200" width="185" height="95" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="112.5" y="241.5" text-anchor="middle">Applied</text><text x="112.5" y="265.5" text-anchor="middle">May be Degraded</text><rect x="230" y="200" width="185" height="95" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="322.5" y="241.5" text-anchor="middle">Failed</text><text x="322.5" y="265.5" text-anchor="middle">Rejected outcome</text><rect x="440" y="200" width="200" height="95" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="540.0" y="241.5" text-anchor="middle">Superseded</text><text x="540.0" y="265.5" text-anchor="middle">Newer target</text><rect x="665" y="200" width="185" height="95" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="757.5" y="241.5" text-anchor="middle">Inactive</text><text x="757.5" y="265.5" text-anchor="middle">Stopped / complete</text><rect x="875" y="200" width="185" height="95" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="967.5" y="241.5" text-anchor="middle">Cancelled</text><text x="967.5" y="265.5" text-anchor="middle">Deleting / deleted</text></svg></div><figcaption>Inactive or deleting sandboxes can enter Inactive or Cancelled directly at admission.</figcaption></figure><p>Applied, IgnoredDuplicate and Degraded outcomes map to <code>Applied</code>; degradation remains a separate visible outcome. IgnoredStale maps to <code>Superseded</code>. RetainedLocalOverride, FailedRetainedLastKnownGood, FailedClosed, Unsupported and unspecified outcomes map to <code>Failed</code>.</p><p>The gateway validates the current session, update ID, sequence and requested revision before a conditional terminal write. <code>config_revision</code> is an equality token; ordered policy/settings revisions determine the desired target. A stale result cannot complete a different target.</p></section>
<section id="recovery"><h2>4. Timeouts and unchanged requests still need completion</h2><figure><div class="diagram"><svg viewBox="0 0 1080 350" role="img" aria-label="Recovery and unchanged-update interactions"><title>Recovery and unchanged-update interactions</title><defs><marker id="arrow3" markerWidth="9" markerHeight="9" refX="8" refY="4" orient="auto"><path d="M0,0 L8,4 L0,8" fill="#58a6ff"/></marker></defs><path d="M320,82 L390,82" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow3)"/><path d="M690,82 L760,82" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow3)"/><path d="M320,277 L390,277" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow3)"/><path d="M690,277 L760,277" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow3)"/><path d="M910,125 L910,235" fill="none" stroke="#58a6ff" stroke-width="2" marker-end="url(#arrow3)"/><text x="910.0" y="171.0" text-anchor="middle" class="edge">send</text><rect x="20" y="40" width="300" height="85" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="170.0" y="76.5" text-anchor="middle">Timeout / disconnection</text><text x="170.0" y="100.5" text-anchor="middle">Committed operation survives</text><rect x="390" y="40" width="300" height="85" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="540.0" y="76.5" text-anchor="middle">Indexed reconciler</text><text x="540.0" y="100.5" text-anchor="middle">Claim due work with CAS</text><rect x="760" y="40" width="300" height="85" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="910.0" y="76.5" text-anchor="middle">Current snapshot</text><text x="910.0" y="100.5" text-anchor="middle">Associate exact target</text><rect x="20" y="235" width="300" height="85" rx="10" fill="#161b22" stroke="#d29922" stroke-width="2"/><text x="170.0" y="271.5" text-anchor="middle">Unchanged request</text><text x="170.0" y="295.5" text-anchor="middle">New operation, same revisions</text><rect x="390" y="235" width="300" height="85" rx="10" fill="#161b22" stroke="#58a6ff" stroke-width="2"/><text x="540.0" y="271.5" text-anchor="middle">Require fresh acknowledgement</text><text x="540.0" y="295.5" text-anchor="middle">Bypass duplicate suppression</text><rect x="760" y="235" width="300" height="85" rx="10" fill="#161b22" stroke="#3fb950" stroke-width="2"/><text x="910.0" y="271.5" text-anchor="middle">Correlated result</text><text x="910.0" y="295.5" text-anchor="middle">Persist terminal state</text></svg></div><figcaption>A newer desired target can supersede the operation instead of following the matching-target send path.</figcaption></figure><p>A timeout does not cancel or roll back the mutation. Indexed, bounded reconciliation recovers due operations with conditional claims and retry deadlines. Local waiter notifications are backed by database polling for cross-replica completion and restarts. Callers can read the operation or retry the same request identity.</p><p>An unchanged update creates an operation using existing desired revisions. While that operation is pending, the stream must request a fresh acknowledgement even if an identical snapshot was previously acknowledged. Otherwise duplicate suppression can strand the waiter.</p><p>Delivery may repeat or coalesce. This is not an exactly-once delivery protocol. The database transaction does not extend into the supervisor.</p></section>
<section><h2>5. Startup and security</h2><p>Gateway and supervisor require protocol revision 3. Startup configuration acceptance is separate from runtime readiness: after workload/relay launch the supervisor sends <code>SupervisorRuntimeReady</code> for the current activated configuration/session.</p><p>Operation reads are workspace-authorized. Records store revisions, state/outcome, timestamps and bounded sanitized errors, not configuration or credentials. In-memory/transport snapshots may contain provider credentials; they must stay out of operation records and logs.</p></section>
<section id="sources"><h2>Source map at the reviewed head</h2><ul><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/proto/openshell.proto">proto/openshell.proto</a> — Public update/wait/operation contract.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/grpc/policy.rs">crates/openshell-server/src/grpc/policy.rs</a> — Admission, mutation and response construction.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/grpc/mutation_replay.rs">crates/openshell-server/src/grpc/mutation_replay.rs</a> — Durable request replay.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/config_update_operation.rs">crates/openshell-server/src/config_update_operation.rs</a> — Target association, terminal transitions, wait and recovery.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/config_delivery.rs">crates/openshell-server/src/config_delivery.rs</a> — Bounded queue, snapshot build and stream delivery.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/supervisor_session.rs">crates/openshell-server/src/supervisor_session.rs</a> — Session correlation and acknowledgement handling.</li><li><a href="https://github.com/NVIDIA/OpenShell/blob/262be8a9e8a42ae4363e8602193b620c60740a76/crates/openshell-server/src/provider_config_operation.rs">crates/openshell-server/src/provider_config_operation.rs</a> — Provider receipt completion.</li></ul></section><footer>Prepared from the PR diff and source at the pinned head. The companion Markdown contains Mermaid sequence and state diagrams. Live-test evidence is published separately; this page makes no capacity claim.</footer></main></body></html>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment