Updates on CDN Environment Automation and Managing a CDN Operating System at Scale
summary
Apache Traffic Control automation now supports Postgres 10/12/13 and IPv6, moves Traffic Vault defaults from Riak to Postgres, and advances Traffic Ops API from 1.3 to 2.0. The dataset loader shaves 1–2 hours off environment creation, ATS profile templates are ~90% smaller via normalization and hardware-aware dynamic profiles, and Postgres now allows primary/standby/replica triads. Molecule-based role tests run single-host and triad scenarios locally and in GitHub Actions across CentOS 7/8, with secrets auto-generated to a local file and optional LetsEncrypt integration.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:13Environment automation updates
- 2:58Traffic Control major changes
- 5:06ATS profile and parameter improvements
- 7:56Dataset loader performance gains
- 9:42Traffic Ops database scalability
- 11:47Ansible testing with Molecule
- 25:30Managing OS at scale
- 26:52Ansible push vs pull workflows
- 32:29Ansible pull repository basics
- 33:34Enhancing Ansible pull deployments
- 37:05Security in Ansible pull
- 39:52Summary and Q&A
related talks
10mAutomating content delivery in a DevOps world
36mPostgreSQL: Ups, DevOps...
36mPostgreSQL: Ups, DevOps...
30mFrom repository to production CI/CD infrastructure in a week
13mBuilding reliable infrastructure with Postgres
34mInfrastructure at Scale Using ArgoCD
06mIgnite: Migrating A Legacy App to Modern Infrastructure
47mScaling: from 0 to 25 million users