Nomad as a HashiCorp Operating System
summary
A minimal Linux image runs Nomad as PID 1 with a tiny kernel and static Go binaries, boots from disk or PXE, and becomes a Nomad client in about 2–10 seconds (network/DHCP usually dominates). Images are roughly 60–80MB (kernel ~8–10MB), idle memory ~20MB RAM. Jobs can pull artifacts to run podman/docker daemons, no systemd or SSH is required, and the setup already boots and runs on cloud VMs and HP c7000 blade hardware.
AI-written summary · about
chapters (7)
- 0:00Introduction to Nomad OS
- 2:13Creating a minimal Nomad Linux
- 7:11Building the Nomad kernel
- 12:49Physical hardware and HPC use
- 18:25Security and attack profile
- 23:01Simplified provisioning with Nomad
- 27:17Experiment results and demo
related talks
12mNomad: Lightweight Orchestration That Complements Kubernetes
53mBootiful workload orchestration with Hashicorp Nomad
13mNomad: Past, Present, and Future [Abridged] 2022
26mNomad: Past, Present, and Future
36mHow Nomad can shoot you in the foot, and what to do to dodge it
31mOrchestration with Nomad
45mNo Internet - No Problem? Air-Gapped Kubernetes on Bare Metal
28mTalos Linux: One (Immutable) OS to Rule Them All