Skip to content

Complete policy rollover across remaining backends #5394

Open

Description

@auser

Parent and dependency

#5386. Follow #5391 and the Firecracker and HVF slices. All backends are a final acceptance requirement, not a permanent Firecracker-only feature.

Targets

libkrun on its supported hosts; QEMU's opt-in dev/test path; explicit Wasm/browser portability paths. Preserve ADR-001/ADR-024 tier restrictions: policy rollover is not a new egress or isolation claim for a backend that lacks those capabilities. Keep mock as test-only.

Acceptance

  • For each selectable backend, trace actual policy/launch/effect owner and implement the same committed-generation and atomic authority switch through its supported lifecycle; use typed refusal for genuinely unsupported requested guarantees while that target is unfinished.
  • For targets without a live handoff, design/implement a safe versioned replacement or honestly restricted lifecycle that still enforces the user's policy change before reporting success. Never silently continue with an old grant or substitute a stronger backend.
  • Add backend-specific happy/failure/crash witnesses, with real hardware/runtime evidence where a claim requires it. Measure readiness including admission and replacement separately.
  • Reconcile CLI/SDK documentation, backend capability matrix, and Design and implement the optional distributed host interface #5097 local/managed host-interface parity. Do not close Define host-trusted evidence freshness across workload transitions #5386 or claim universal support until all applicable targets meet their contract.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions