Shipping Servers Continuously with Ansible, Packer and Terraform

Since server configuration has become code for quite a while now under the DevOps regime, we should be able to ship it with the same frequency as we ship code. Only the end artefact would be a VM, instead of a deployable code archive. This session will cover how we can achieve this with Ansible, Packer, A CI service (wercker) and Terraform.

Transcript

1. SHIPPING SERVERS CONTINUOUSLY with Ansible, Packer and Terraform at
2. @hashfyre 0.5 DevOps* team at Razorpay *Can we play a D&D campaign instead?
4. COOL SOUNDING BUZZWORDS …with cooler logos and these are…
5. WHAT’S AN-SIBLE? • Hark back to Ursula Le Guin’s Rocannon's World (1966) • FTL comm channel • Just started reading EarthSea, don’t ask me about ^
6. CONFIG MANAGEMENT • Move over #!/bin/bash because YAML is cooler? • Kinda better at scale • Agentless, uses ssh • Python!
7. PACKER’EM UP • Packs disks into re-usable images • Uses Ansible, Chef, even Bash as a provisioner • Industry scale iso-maker? • Golang!
8. TERRAFORM • We’sa coming Elon Musk • Planet AWS is ours to colonize • Graph theory FTW! • It’s just a DAG for resources • Golang again, ‘ow quaint!
9. !SECRET SAUCE + = AMIs git commit == image Localhost
10. MAKE IT CONTINUOUS. + = Baker a Docker based CI service
11. LAYERING WITH PIPELINES servers ~ onions 5~10 mins
12. BLUE GREEN _________ ____________ + AMIs {Instance Launch Config AutoScaling group Load Balancer Destroy the old instances, they died heroes lookup
13. 3 STEP DEPLOY ~# git push ~# terraform plan ~# terraform apply
14. WHAT WE LEARNT }Take a bunch of buzzwords Shake’em well Add glue to taste Expecto Serverus!
15. QUESTIONS?
16. @hashfyre I made my own cool logo, Take that.