Ansible and infrastructure as code

99f481c5ef312c5f3d299b5957a22a07?s=47 Andreas Mosti
December 09, 2016
Programming
0
640

Ansible and infrastructure as code

A talk about how Ansible and Infrastructure as code

99f481c5ef312c5f3d299b5957a22a07?s=128

Andreas Mosti

December 09, 2016
Tweet

Want more?

99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
58
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
75
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
190
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
2
160
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
1
83
766b9746b59e6f09e280cd33cf4ed419?s=48 skipperchong
0
75
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
5
150
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
4
160
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
2
220
C35e01544a0dd94a2cf1619ee8a42ebb?s=48 clairelew
2
440
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
1
120
B3ace07412a5178ea778e7eec161fc0a?s=48 jcasabona
4
200

Transcript

  1. 1.

    and infrastructure as code

  2. 2.

    Motivation

  3. 3.

    • Test environment hell • Inconsistent server farms • «What

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

    Snowflake vs. Phoenix Server

  6. 6.

    Infrastructure as code

  7. 7.

    • Reproducible environments • Servers in source control • Imutable

    infrastructure • Safety!
  8. 8.

    Baked vs. Fried servers

  9. 9.

    The usual suspects

  10. 10.
    None
  11. 11.
    None
  12. 12.

    Why Ansible?

  13. 13.

    Cross platform

  14. 14.

    Open Source

  15. 15.

    Agentless

  16. 16.

    Most important:

  17. 17.

    The correct abstraction (for us)

  18. 18.

    Playbooks push Database Appserver Build agent

  19. 19.
    None
  20. 20.

    Ansible keeps state

  21. 21.
    None
  22. 22.
    None
  23. 23.

    Let’s dive into it