Make your environment sane with Ansible Automation
summary
Automates a messy fleet of roughly 300 GlassFish instances and ~300 MySQL installs by switching from per-server shell scripts to agentless SSH via Ansible, pushing playbooks in Git with SSH keys and sequential, linear runs. Builds provisioning playbooks, role-based config, and a YAML-driven, idempotent user definitions file so creates become repeatable; deletions remain manual. Outcome: consistent, testable lifecycle automation that replaces dozens of bespoke scripts and scales deployment of new customer servers.
AI-written summary · about
chapters (14)
- 0:00Ansible automation intro
- 3:57Messy inherited environment
- 10:43Why Ansible was right
- 13:59First process to automate
- 16:09App server provisioning
- 19:23User lifecycle automation
- 23:00Automation best practices
- 26:31Q&A: Role and playbook sizing
- 28:34Q&A: YAML editor
- 29:48Q&A: Many playbooks
- 31:55Q&A: User removal
- 33:40Q&A: Missing files
- 34:23Q&A: Playbook structure
- 35:46Closing remarks
related talks
39mAnsible - Your First Step Into Server Provisioning
43mAutomated server management with open source tools
16mAnsible
39mContinuous Deployment with Ansible
36mGentle Introduction to Ansible
37mAnsible 101
36mMake You Ops-Life Easy – ansible usecases you didn´t out of track
31mGetting more done in less time