How We Manage Infrastructure Across 1,000+ Servers Using ansible
summary
Describes managing infrastructure for over 1,000 servers using Ansible to keep Git-stored configuration synchronized with live servers. Explains the scaling problem: applying configuration was fast with few hosts but became too slow as host count grew, and covers the approaches and practices used to make configuration application efficient and reliable at large scale.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:09Ansible selection criteria
- 3:13GitLab CI tag issues
- 4:59Switching to Kubernetes-like
- 6:27First failure with adoption
- 8:17Ansible performance issues
- 10:48Python agent solution
- 13:40Blocking manual changes
- 15:49Agent installation on servers
- 17:16Rerun utility
- 18:40Security issues and antibouncer
- 21:55Ansible project structure
- 23:40AVX for tasks
- 25:45Monitoring and alerts
- 26:06Results and achievements
- 27:29Q&A
related talks
01h 00mDon't fear the devops. Taming servers infrastructure with Ansible
49mWhen PowerShell Is Better Than Ansible? Recipes for Managing 1,000+ Servers
31mPractices to Improve the Performance, Scale and Efficiency of Your Ansible Playbooks
36mMake your environment sane with Ansible Automation
36mMake You Ops-Life Easy – ansible usecases you didn´t out of track
17mManaging Infrastructure with Python, Fabric and Ansible
37mAnsible 101
39mContinuous Deployment with Ansible