Federation Release Readiness
Entry point for the CloudEdge Event Federation release status.
Phase completion
| Phase | Scope | Status | Evidence |
|---|---|---|---|
| Phase 1 | Event envelope, EventGroup, SQLite store, CLI | done | checkpoint |
| Phase 1.5 | EventPeer, EventSubscription Kinds + validation | done | checkpoint |
| Phase 2 | Peer delivery, HMAC, retry, prune | done | transport evidence |
| Phase 3 | Subscription → plugin → RemoteAddressClaim | done | subscription evidence |
| Phase 4 | Provider actionPlan plugins, dry-run | done | ADR 0007 |
| Phase 5 | Provider action execution (gated) | done | AWS, Azure, OCI |
| P1 | Federation pipeline observability (14 OTel metrics) | done | observability how-to |
| P2 | Doctor federation checks, delivery summary | done | changelog |
| P3 | FederationSLO Kind, SLO JSON, remediation plan | done | PR #541 |
| P4 | Operational qualification & release candidate | in progress | this document |
Architecture references
Qualification harness
The reusable qualification harness is at scripts/cloudedge-federation-qualification.sh.
scripts/cloudedge-federation-qualification.sh \
--evidence-dir /tmp/fed-qual \
--cycles 2 \
--duration 300 \
--scenarios healthy,partition,ttl-refresh,restart,subscription,config-fault,security,multi-group
8 scenarios are defined:
- healthy — baseline delivery + doctor PASS
- partition — peer network partition → SLO violation → recovery
- ttl-refresh — TTL refresh re-push across partition boundary
- restart — eventd restart recovery (sender + receiver)
- subscription — subscription plugin failure + recovery
- config-fault — expected-peer / config fault detection via doctor
- security — HMAC / timestamp / malformed event rejection
- multi-group — per-group SLO isolation
Evidence template: evidence/federation-p4-operational-qualification-TEMPLATE.md
Auto-remediation readiness
See federation-remediation-readiness-matrix.md for the P5+ readiness classification of all 7 remediation actions.
Summary: 2 actions are ready for auto-execute (retry-failed-deliveries, force-repush-stale-ttl), 4 are inspect-only, 1 is not ready (configure-peer-endpoint requires operator approval).
Documentation convergence
| Document | Status |
|---|---|
| ADR 0006 | Updated — P1-P3 reflected, FederationSLO Kind listed |
| ADR 0007 | Updated — Phases 5.0-5.1 marked DONE |
| Checkpoint | Historical note added |
| Changelog | P1-P3 + Phase 5 entries added to Unreleased |
| Observability how-to | Updated with P3 per-group SLO contract |
Release criteria
- All 8 qualification scenarios PASS on at least one provider pair
- Doctor JSON output matches FederationSLO contract
- Remediation plan output is deterministic and diff-stable
- No secrets in evidence files
- Documentation converged (all rows above = Updated)
- CI green on qualification branch
- Evidence committed to
docs/releases/evidence/