Test Kitchen Sessions
Arthur Maltson, Distinguished Engineer, Capital OneWatch Session » Session Description »
Test Driven Development is a popular concept in Software Development, leading to higher quality code that’s easier to maintain. Automated testing is normally a foreign concept in the Operations/DevOps world, but as you ssh into your servers to make that quick fix or run your updated script (fingers crossed), you might be wondering if there’s a better way. A way that gives you the confidence in your script and lets you test those scripts in isolation. There is a better way! Test Driven Infrastructure (TDI) is now possible. I know, it sounds crazy.
At this session you’ll learn the how, and more importantly the why, of TDI. You’ll see how Chef can be tested with Test Kitchen and Chef InSpec. You’ll also learn how to improve your feedback cycle with Docker, and using the Docker approach on a CI server. There’s even a live demo!
Finally, the Ops world collides with the Dev world in true DevOps testing bliss.
Lance Albertson, Director, OSU Open Source LabWatch Session » Session Description »
Multi-node testing with Kitchen has long been a requested feature, however it’s outside of the scope of Kitchen. Multi-node testing is useful for testing complex services such as replicated database servers, Ceph clusters and OpenStack to name a few.
Some examples of how this is useful:
- Test to ensure your replicated database servers can fail over properly
- Test an upgrade between versions of Ceph or Openstack where doing this in an “All-in-One” might have differences with multiple nodes interacting
- Ensure all components can communicate properly with firewalls
At the OSUOSL, we developed a method for doing this using a combination of Kitchen, Terraform, InSpec and OpenStack (however any public cloud supported by Terraform will also work).
This session will cover the following topics:
- Why this is important and the problem we’re trying to solve
- Discuss what tools we used
- How you can replicate this for your environment
- Recorded demo using a real-world example
Annie Hedgpeth, Senior Cloud Automation Engineer, 10th MagnitudeWatch Session » Session Description »
For those that have longed for a simpler test-driven approach to Terraform development, come and see how I’ve made my team’s lives easier by using Test Kitchen for Terraform and how I can validate my deployments with InSpec. This will be a beginner’s guide, but all skillsets are welcome to contribute to the conversation!
We’ll discuss the different use cases for Terraform testing, such as:
- Test Driven Development (TDD)
- Integration Testing and CI/CD
- Compliance, shifting security left
- Production provisioning validation
As we know, good testing doesn’t just solve CI/CD problems; it solves culture problems. I will seek to convince you of why you need to invest in a good Terraform testing strategy early and how you might have bought into a myth that makes you think you have velocity when you don’t (are you running in wet cement).
And if you’re late to the game and have existing infrastructure with no tests, that’s okay, too. Let’s talk about how you can reduce stress by adding in some testing now. It’s not too late.
It takes an IT village to do DevOps, so let’s talk about moving security and sanity left with InSpec and Terraform. So many use cases, and so little time. You’ll leave this talk ready to implement at least one of them.