Verifying your Ansible Roles using Docker, Test Kitchen and Serverspec
•Download as PPTX, PDF•
1 like•774 views
In this presentation I demonstrated how simple it is to develop Ansible roles in a test driven way, using the faster feedback that docker enables and the easily readable Serverspec test framework, with Test Kitchen helping to bring all the tools together.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Verifying your Ansible Roles using Docker, Test Kitchen and Serverspec
Similar to Verifying your Ansible Roles using Docker, Test Kitchen and Serverspec (20)
Recently uploaded
Recently uploaded (20)
Verifying your Ansible Roles using Docker, Test Kitchen and Serverspec
- 1. Verifying your Ansible Roles Feat: Docker, Test Kitchen, Serverspec
- 3. Coming up… • Test Kitchen • Serverspec • Ansible • Docker • Demo Time!
- 4. Test Driven Development Write Failing Test Write CodeMake Test Pass Write tests one at a time Add code in small increments Commit often No refactoring until tests pass
- 5. Test Kitchen • Originally designed for Chef • Test Harness with simple workflow • Pluggable architecture!
- 6. Key Concepts • Drivers << • Provisioners • Platforms Where to run your code: Cloud infrastructure Azure, EC2, Rackspace Local environment Vagrant, Docker
- 7. Key Concepts • Drivers • Provisioners << • Platforms How to configure your environment: Ansible, Chef, Puppet, CFEngine
- 8. Key Concepts • Drivers • Provisioners • Platforms << Which OS to spin up: Can be Linux or Windows if using a VM
- 9. Test Kitchen Workflow Create Environments Config Management Run Tests VerifyConverge
- 10. Ansible 101 • SSH-based configuration management • Idempotent - Test & repair to achieve desired state • YML files with loops, conditionals and variables
- 11. Example Ansible role - template: src: foo.j2 dest: /tmp/foo.sh - user: name: “{{item}}” group: admin with_items: {{new_user}} tasks/main.yml defaults/main.yml templates/foo.j2 test_var: “Hello world” new_user: [foo,bar] #!/bin/bash echo {{ test_var}} Tasks Variables File Template
- 12. Serverspec RSpec for your infrastructure describe file('/etc/passwd') do it { should be_file } it { should exist } end describe package('httpd') do it { should be_installed } end describe user('foo') do it { should exist } it { should belong_to_group ‘bar’ } end Resource Matcher
- 13. Docker 101 • Image = Readonly template of a filesystem • Container = Isolated filesystem and processes based on an image • Image filesystem is made up of 1 or more cached layers • A container is not a VM! • Host kernel is shared with containers
- 14. Virtual Machine Docker Container
- 15. Why does this matter? • Spinning up a new container takes very little time • Faster feedback when testing • Containers can run inside VMs on hardware that doesn’t support virtualisation inside VMs • Images take seconds to update due to caching 'In our world, fast feedback is essential' - @martinfowler
- 16. Creating a new docker image Example Dockerfile FROM ubuntu:15.04 RUN apt-get update RUN apt-get install sudo openssh-server curl lsb-release -y From Docker registry
- 17. Why test at all? “You are already describing the desired state of the system in Ansible, why do it another time?”
- 18. Refactoring Uncoupling testing from Ansible People get it wrong!
- 19. Installed Software • Docker 1.8.2 (from package) • Ansible 1.9.3 (from package) • test-kitchen (rubygem) • kitchen-ansible (rubygem) • serverspec (rubygem)
- 20. Demo time!
- 21. Questions?
Editor's Notes
- Write tests first, one at a time. Add code in small increments. Commit often while tests still work.
- Pluggable arch: Very active github community creating plugins for commonly used config management tools, test frameworks and platforms
- 2 commands in test kitchen to orchestrate creating the environment and testing it
- Resource: