NOTE: There is a picture in the comments with better directions of where to park and where the main entrance is.


Ansible is an incredibly easy way to manage infrastructure and configuration. But what’s the best way to ensure the changes to your Ansible playbooks have the intended outcome and do not introduce unwanted changes? And how can you verify your your playbook changes do not negatively impact the compliance status of your infrastructure?

In this session, we will learn about InSpec and how it’s incredibly easy-to-read language allows for integration and compliance requirements to be expressed as code. We will look at how Test Kitchen and InSpec can be used to validate your Ansible playbooks and empower developers to test for compliance earlier in the development cycle. Additionally, we will also explore how to use and modify InSpec profiles created by others.

Nathen Harvey, VP of Community Development at Chef, helps the community whip up an awesome ecosystem built around the Chef platform. Nathen also spends much of his time helping people learn about the practices, processes, and technologies that support DevOps, continuous delivery, and high velocity organizations. Prior to joining Chef, Nathen spent a number of years managing operations and infrastructure for a diverse range of web applications. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps. He is also an occasional farmer who loves eggs and actively supports #hugops.


11:30a – 12:00p Eat and network
12:00p – 12:45p Eat while learning some awesomeness from Nathen