Trondheim Developer Conference 2018: Ansible and infrastructure as code

99f481c5ef312c5f3d299b5957a22a07?s=47 Andreas Mosti
October 24, 2018
Technology
0
310

Trondheim Developer Conference 2018: Ansible and infrastructure as code

Slides from my TDC2018 talk about Ansible and infrastructure as code.
https://vimeo.com/296639173

99f481c5ef312c5f3d299b5957a22a07?s=128

Andreas Mosti

October 24, 2018
Tweet

More Decks by Andreas Mosti

See All by Andreas Mosti
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
77
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
77
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
200
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
24
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
17
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
38
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
56
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
640
99f481c5ef312c5f3d299b5957a22a07?s=48 andmos
0
130

Other Decks in Technology

See All in Technology
80a3a3857a55f154d23acb705eff72cc?s=48 star_zero
4
350
42ba906dc35ef460ffcb1b7c3307ef45?s=48 spring_raining
0
1.1k
9ae4f3862d4cb0771cfd36e43252f755?s=48 kurotanshi
0
1.5k
0102ef8594b9d3a74f45dfd5daa5ede4?s=48 yskmjp
0
200
84907687e50c8ac2a09b02e0d1b36ab1?s=48 toricls
14
2.7k
D5a8875907107294786ee8cba72c7f4c?s=48 torufuru
1
520
1b177b37d966f573b1df5d7218a5f560?s=48 k2wanko
1
210
Bf7fe621f4fe1615c228ef8a79b87282?s=48 shirayanagiryuji
2
660
25b30e875da37bab1edc8fbc2fe23df7?s=48 _mossann_t
0
630
961126d9892ae4df45249529a0721571?s=48 sugamasao
2
480
57eb5b1713206c5edb521dde99cc5f30?s=48 key
0
200
F6ceb15fb20b52f49e375cec868a0107?s=48 tokitakumi
3
870

Featured

See All Featured
9fa239b3154a0169d99ab7bf1422dd12?s=48 marcelosomers
220
14k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
446
36k
462dad0dd24c568a32dcdb0ae895ae1b?s=48 rasmusluckow
316
18k
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
165
6.9k
48c098b6579220a67a6ba949be6e4b5a?s=48 revolveconf
197
9.5k
91cefdf141106fa10674aae74ce05890?s=48 yeseniaperezcruz
297
31k
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
10
630
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
165
18k
7edec06b5435e0dac07a353b2cc26253?s=48 geeforr
331
29k
C0b42577cfc2b321be3474618107e933?s=48 samanthasiow
54
6k
A0517b08532aec8ab2aae3f65d40ad86?s=48 hannesfritz
27
890
9cde37f47e4a800ea081ea42de8d749a?s=48 dougneiner
119
7.7k

Transcript

  1. and infrastructure as code

  2. ! Hi TDC, I’m Andreas!

  3. None

  4. Dev/Build Runtime

  5. Dev/Build Runtime

  6. Dev/Build Runtime

  7. Dev/Build Runtime

  8. None
  9. None

  10. The complexity moves

  11. None

  12. Test environment hell

  13. Inconsistent server farms

  14. Platform requirements, «What are we releasing on?»

  15. «We need new environments quickly, in a reproducible fashion»

  16. None
  17. None

  18. The first step: automate the infrastructure

  19. Snowflake vs. Phoenix Servers

  20. Infrastructure as code:

  21. Reproducible Environments

  22. Servers in version control

  23. Configuration management

  24. Explicit process

  25. Safety!

  26. Baked vs. Fried servers

  27. The usual suspects

  28. None
  29. None

  30. Why Ansible?

  31. None
  32. None

  33. Open Source

  34. SSH WinRM

  35. Most important:

  36. The correct abstraction (for us)

  37. None

  38. Playbooks push Database Appserver Build agent

  39. None

  40. Remember: Ansible keeps state

  41. HAProxy DIPS EHR Zookeeper Solr Oracle