Replicated control plane: three control hosts with Raft over the ledger, term-fenced feed

Open
#155 1 comment 0 reactions 0 assignees View on GitHub

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

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.

  • openraft over 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.