Design
How it is put together
These pages are the repository's design documents, rendered. The text lives in docs/ and is the source of truth. For how workloads run, hold leases and replay, see felixd's design.
- 1NineLives designWhat boots on each machine, how it joins, and which services live on the log.
- 2Cluster topologyWhere Felix and felixd run, and how a cluster comes up.
Open questions
Where these documents name a tool, it is a proposal. The choices still open:
- Linux or our own kernel? Proposal. None yet. Both sides are in the discussion. Discussion #22
- Our own PID 1, or systemd? Proposal. systemd for the first milestones, then see how much of its job moves onto the log. Issue #15
- How are images built? Proposal. mkosi, producing a read-only root. Issue #1
- How does a machine upgrade? Proposal. A/B root partitions that switch on reboot and fall back on a failed boot. Issue #8
- How does a machine prove who it is? Proposal. None yet. This is the first join, before the machine has credentials. Issue #16