Replicated control plane: three control hosts with Raft over the ledger, term-fenced feed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- distributed-systems
Research direction
Read docs/research/24-control-plane-ha.md sections 5.3 and 6.2, then check what phases 1–4 establish and whether they show this work is needed. The issue calls for Raft replication, term-fenced feeds and placement destroys, leader-only control tasks, and replicated access tokens; it does not name implementation files or tests. Done means control service continues through the loss of one control host without human intervention.
Written by the indexing model from the issue text.
Description
Phase 5 of the control-plane HA plan (docs/research/24-control-plane-ha.md §5.3, §6.2). Build only if phases 1–4 show it is needed.
openraftover the ledger's commands (deterministic: the leader stamps time and ids), the vault replicated with it.- Only the leader publishes the feed, issues grants and reconciles; feed frames carry the term and nodes refuse lower terms; placement destroys are term-fenced.
- A stateless console on every control host behind one name; one Claude login refresher, access token replicated, never the refresh token.
Keeps working once shipped: everything through the loss of one control host, without a human.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 190
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from public/wicket
-
Don't break the machines: node health alerts, admission control, reserved headroom, volume lifecycle, collection trackingPossibly taken @public claimed this today. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement parked
Difficulty 5/5 Over a week Newbie friendliness 12/100
public/wicket#371 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
Windowed egress caps and standard OTLP decision records (from AgentCore, Strands Box and Dogwood)Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day