API != REST - procmail to the rescue
summary
A workshop-on-demand system uses an SMTP-based API instead of HTTPS: the public Netlify front-end sends emails with verbs like create/reset/cleanup, postfix receives them and procmail filters route parameters from subject/body into scripts. Those scripts run shell, Ansible playbooks and jupyterhub APIs to provision per-student environments, generate passwords, and queue cleanup after four-hour sessions. Ten workshops exist now, deployment and nightly convergence run via Ansible playbooks, and the email queueing model proves reliable for asynchronous provisioning and teardown.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:48Bruno Cornec
- 1:35Frederic Passron
- 3:04Workshop on Demand
- 7:35procmail
- 10:17infrastructure
- 11:58demo
- 19:03wrap up
related talks
21mAPI != REST - procmail to the rescue
36mSelf-service Network Automation Using Slack
25mNetwork Automation Tools & Technology
35mBeyond Inbound: Unlocking the Secrets of API Egress Traffic Management.
42mAutomation for Bureaucracies
50mJust Enough Network Automation to Get You Started
31mNetwork Automation Architecture: Platform vs Power Tools
01h 25mCloud-Native Building Blocks: An Interactive Envoy Proxy Workshop
