Automate all the things! Devops is the new hotness in our industry. The “infrastructure as code” mantra makes intuitive sense and has caught fire. I’ve learned some things to help the fire keep us warm instead of burning the house down.

Automate all the things! Devops is the new hotness in our industry. The “infrastructure as code” mantra makes intuitive sense and has caught fire. I’ve learned some things to help the fire keep us warm instead of burning the house down. I’ll talk about: * Why we should automate deployments * Windows vs. Linux in the deployment space * Cattle vs. Pets * Chef compared and contrasted with Octopus Deploy * When infrastructure should and should not be code

Technical Requirements

I’ll bring my laptop. All I’ll need is an internet connection.

Qualifications

I’m leading a transition from Chef to Octopus Deploy at my company. We are primarily a Microsoft .NET shop with some Linux appliances such as Couchbase and RabbitMQ. My team supports 40 separate environments on private cloud infrastructure. We must deploy 50+ correctly configured applications of all types to an environment on demand. This is a hard space to get right and we’ve learned a lot of painful lessons. I’ve written about our experience with Chef and Octopus here.