Concepts¶
Shared ideas used by operators, DevOps, and developers.
Desired state¶
Git is desired truth. EVE is runtime truth. The Cockpit is derived.
- Why EVE IaC? — desired state + interaction; what this is not
- Architecture — two truths, reconcile as the desired-state machine
- Project structure — marker, modes, sidecars
- YAML —
topology.yml - Import — first adoption of a source lab (not
from_eve)
Reconcile¶
How Git and the managed lab converge. Fail-closed, then progressive. Not a merge.
- Directions —
to_eve(Local wins) /from_eve(repo sync) - Plan / reconcile — picture, two passes, classifications, pipeline
A plan answers in three ways: live_applicable (apply now), requires_stop (confirm this examined plan), unsupported (change the YAML — zero EVE writes).
Interaction as Code¶
Operational. Not a reconcile contract cell.
- Interaction as Code — consoles, Hub, exec/wait/run, capture, traffic
- Live link quality / suspend — runtime NETEM and TAP suspend
- Lab canvas — local schematic, interaction modes, capture tab, traffic matches
- Console sessions —
session_id, observe/interact/exclusive - Exec, wait, run — Hub join, prompt return, timeouts
- Console security — limits and non-goals
Product¶
- Security
- Compatibility — pairing, platforms, documented limits
- Versioning — package version vs
eve-iac/v1 - License — AGPL-3.0-only