COSI: The Common Operating System Interface
summary
COSI defines a concrete API for node configuration — modeled resources as Protocol Buffer definitions mapped to DNS, network, kernel, mounts and more, with bi‑directional gRPC CRUD/get/list/watch semantics. A plugin architecture runs each low‑level plugin continuously (like controllers) and a Rust reference implementation orchestrates them as an engine/runtime (can run as PID 1 or in a container). Demo shows mount create/delete reconciling successfully and an eBPF generator emitting kernel events for USB/ACPI that drove real-time notifications.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:24What is COSI
- 1:00Reimagining operating systems
- 1:20Why COSI
- 2:06Priorities
- 3:47Agenda
- 4:22History of Unix
- 5:36Multiuser timesharing
- 6:30Unstructured files
- 6:57Linux
- 8:39Container Operating Systems
- 11:19Protobufs
- 12:33Plugins
- 13:31Generators
- 14:05Core Concepts
- 16:42Demo
- 17:01Generator
- 20:52Outro
related talks
39mContainer Storage Interface: Present and Future
28mCNI, CRI, and OCI - Oh My! [I]
27mCoCoS - Remote configuration with super powers
31mCRI-O: The Runtime Control Room
37mCRI-O: Under the Hood
31mBuilding an Interconnected Ecosystem
24mEnhancing CRI-O With CDI: Streamlining Device Integration in Kubernetes
54mOCF for Resource-Constrained Environments