Control Node: Continuous Delivery & (...) for Elixir
summary
Control Node is an Elixir library that builds CD pipelines as code and demos a working setup: GitHub Actions runs mix release, uploads a tar, CNOPS detects it, pulls the artifact and deploys to test then to two production VMs, and the controller restarts a killed node. Key specifics: stateless design (state rebuilt from pipeline spec), requires SSH access and distinct hostnames, uses EPMD with a custom ssh-tunneled epmd, supports local registries, offers remote Observer connect for debugging, needs Erlang 23+ and ed25519 keys, and targets small–medium fleets (tens to low hundreds of services).
AI-written summary · about
chapters (19)
- 0:00Start
- 0:27Continuous Delivery
- 1:21What Continuous Delivery Is
- 3:28Using Docker in Production
- 5:11Control Node
- 6:15Notable Features
- 6:51Simplicity
- 11:14Demo
- 21:59Release Spec
- 22:37Host Specs
- 22:58Registry
- 23:35Namespace
- 24:32Service Discovery
- 25:27Export Flag
- 26:22Ssh Keys
- 28:57Small and Medium-Sized Service Deployments
- 29:52Scaling Your Services Vertically
- 32:44Does Control Node Require a Separate Vm To Function and Detect Production Node if a Production Node Dies
- 34:18Do You Use It on Production in Your Company
related talks
32mEvent-based Continuous Delivery: The End of the Monolithic Pipeline
17mIntro: CNCF Cross-Cloud CI
37mImport Continuous Delivery
41mAll Things Continuous
17mDriving Continuous Delivery: Trunk-Based Deployment Strategies with PipeCD in Large Scale
47mContinuous Delivery Meets OpenShift
30mModern Continuous Delivery
12mContinuous Deployment in a heavily regulated environment