Ansible and infrastructure as code

Ansible and infrastructure as code

A talk about how Ansible and Infrastructure as code

99f481c5ef312c5f3d299b5957a22a07?s=128

Andreas Mosti

December 09, 2016
Tweet

Transcript

  1. and infrastructure as code

  2. Motivation

  3. • Test environment hell • Inconsistent server farms • «What

    are we releasing on?» • Platform requirements • We need new machines quickly • Developers waste time!
  4. None
  5. Snowflake vs. Phoenix Server

  6. Infrastructure as code

  7. • Reproducible environments • Servers in source control • Imutable

    infrastructure • Safety!
  8. Baked vs. Fried servers

  9. The usual suspects

  10. None
  11. None
  12. Why Ansible?

  13. Cross platform

  14. Open Source

  15. Agentless

  16. Most important:

  17. The correct abstraction (for us)

  18. Playbooks push Database Appserver Build agent

  19. None
  20. Ansible keeps state

  21. None
  22. None
  23. Let’s dive into it