Скачать или смотреть Practical Environment Management: Ansible Configuration

Tony Cook is a Devops Architect at UFG, an insurance company. Over the past 18 months the Devops team has completely redefined how environments are configured, managed, and administrated. Application environments that had taken months to set up can be configured on demand, reducing configuration time, administration time, and allowing purpose driven environment creation.

I intend to start by painting a picture of our old ‘infrastructure management’ where application environments took weeks to months to set up, and were managed and maintained for sometimes years. I usually start the presentation by clicking ‘start’ and explaining we will end up with 15 servers, then jumping into:

I will break down the idea of an insurance company needing ‘stable’ test environments to ensure as much quality as possible when going to production. We have a lot of dependencies, especially a mainframe that does overnight batch processing, giving us small windows to do deployments. We were on a cadence of taking one Saturday per month to turn everything off, perform updates, and turn everything on.

I will then contrast this with our current model, going back to the servers in Tower that are 12 application servers and 3 SQL servers, with all dependencies, IP, DNS, backup, GMSA, etc features working. The power of creating an application environment allows us to avoid patching, updating, questions like ‘Who changed something in QA, why does it work in Dev not in QA?’ and create environments specifically for purposes like Performance testing.