How Terraform Fits into the DevOps

At its core, DevOps is a cooperative effort between the business, operations, and development groups of a company. From the definition: “DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.”

In the cycle of a business or product feature making it into production, there are a lot of phases that the feature and code must go through as part of the development and deployment process. From initial code writing, building, and testing, to packaging, releasing, and finally, monitoring and measuring the production performance.

In this talk we’re going to review one part of the typical DevOps cycle which is the “release” section. Specifically, we’re going to talk about how to create the infrastructure needed for a release in an agile, fluid manner. In fact, another way to define DevOps is “agile infrastructure”. We’re going to focus on a tool called Terraform which allows us to easily define and create infrastructure resources using code and well-defined business rules.

About the Speaker:

JP Toto is an infrastructure software developer and occasional speaker (http://ndc-london.com/). He work's at a fairly well known producer of fine sandwiches and fast-casual dining fare (http://www.wawa.com/). He helps automate their infrastructure and spread the gospel of devops (https://en.wikipedia.org/wiki/DevOps).

Working at Wawa keeps him pretty busy and has given him the opportunity to explore a lot of modern API implementations and infrastructure automation. APIs are one of his keenest interests right now and he tries to read up (http://apidigest.com/) on (http://apievangelist.com/blog/) and follow (https://twitter.com/johnsheehan) as (https://twitter.com/darrel_miller) many API resources as possible.

As a fan of open source and he tries to contribute to projects as much as possible – which, he believes, is never often enough. There are some projects (http://jptoto.jp/projects/) he works on from time to time which you can read more about here (http://jptoto.jp/projects/).

At a previous position, with Wildbit (http://www.wildbit.com/), he and his team were faced with a challenge when deciding how to store email messages sent through the Postmark (http://postmarkapp.com/) application. Ultimately they decided to use Elasticsearch (http://www.elasticsearch.org/) for most of their storage and index/search needs. Consequently he developed some expertise which he hopes to pass on to others by way of his blog and several (https://www.pluralsight.com/authors/james-toto) courses (https://www.pluralsight.com/authors/james-toto) he has authored at at Pluralsight (http://www.pluralsight.com/).

If you’d like to get in touch with him the best ways include: Linked In (http://linkedin.com/in/jptoto),Twitter (http://twitter.com/jptoto),Github (http://github.com/jptoto), or Stack Overflow (http://stackoverflow.com/story/jptoto). He can also be reached via email at: jp at jptoto.jp.

https://secure.meetupstatic.com/photos/event/d/1/e/8/600_466193736.jpeg

We look forward to seeing everyone! Please RSVP by December 10th.

Agenda:

6:00p - 6:30p: Food & Networking

6:30p - 7:30p: Talk begins.