Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Automated Infrastructure Testing
Search
Ranjib Dey
September 08, 2012
0
200
Automated Infrastructure Testing
Testing strategies for chef managed infrastructure
Ranjib Dey
September 08, 2012
Tweet
Share
More Decks by Ranjib Dey
See All by Ranjib Dey
Consul @ PagerDuty
ranjibd
1
160
Extending CI/CD in Operations Using Chef & LXC
ranjibd
1
310
Adopting Test Driven Development in Operations
ranjibd
4
1.4k
Chef-LXC - Building and deploying custom containers
ranjibd
2
1.6k
How to mock a mocking bird - testing dynamic infrastructure
ranjibd
4
1.1k
A short introduction to LXC
ranjibd
1
350
Attaining Resiliency - Culture , Tools and Practices
ranjibd
2
1.1k
Enabling continuous delivery for your webapp
ranjibd
2
170
Featured
See All Featured
jQuery: Nuts, Bolts and Bling
dougneiner
59
7.1k
How GitHub (no longer) Works
holman
304
140k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
226
51k
Building Better People: How to give real-time feedback that sticks.
wjessup
355
18k
4 Signs Your Business is Dying
shpigford
175
21k
Automating Front-end Workflow
addyosmani
1356
200k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
14
1.5k
Embracing the Ebb and Flow
colly
80
4.1k
Building Your Own Lightsaber
phodgson
99
5.7k
Building Applications with DynamoDB
mza
88
5.6k
Building Adaptive Systems
keathley
31
1.9k
Statistics for Hackers
jakevdp
789
220k
Transcript
Automated Infrastructure Testing Ranjib Dey System Administrator, ThoughtWorks
Part 1 What we are building?
What you already know?
To Code (develop functionalities) To Test (ensure if its working
fine)
To Code (develop functionalities) To Test (ensure if its working
fine) Automate
Enter DevOps/CD
To Code (develop functionalities) To Test (ensure if its working
fine) To Deploy (ensure if it can be released)
To Code (develop functionalities) To Test (ensure if its working
fine) To Deploy (ensure if it can be released) Automate
To Code (develop functionalities) To Test (ensure if its working
fine) To Deploy (ensure if it can be released) Automate Automate
To Code To Test To Deploy Automate Automate CI
To Code To Test To Deploy Automate Automate CI CD
Part 2 How it is different?
Tested code Deployed code Automate
Tested code Deployed code Automate Infrastructure
Tested code Deployed code Automate Infrastructure Operations
Tested code Deployed code Automate Infrastructure Operations Data
Tested code Deployed code Automate Infrastructure Operations Data Compliance
Tested code Deployed code Automate Infrastructure Operations Data Compliance End
users
Tested code Deployed code Automate Infrastructure Operations Data Compliance End
users Integrations
On infrastructure
To Code To Test To Deploy Automate Automate
To Code To Test To Deploy Automate Automate Build infrastructure
To Code To Test To Deploy Automate Automate Build infrastructure
Production Infrastructure
Part 3 On testing
Tested code Deployed code Automate
Tested code Deployed code Automate Infrastructure as Code
Tested code Deployed code Automate Infrastructure as Code Code
None
Tested code Deployed code Automate Infrastructure as Code Code Test
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing
None
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing Functional Testing
Scenario: Nginx is running as a daemon When I run
"ps aux | grep nginx" Then I should see “nginx:master" in the output
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing Functional Testing
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing Functional Testing Integration Testing
describe_recipe 'nginx:configuration' do it 'installs version 1.0.15' do node[:nginx][:version].should ==
'1.0.15' file("/etc/nginx/nginx.conf").must_have(:mode, "644") package("nginx").must_be_installed service("nginx").must_be_running end end
Tested code Deployed code Automate Infrastructure as Code Code Test
Unit Testing Functional Testing Integration Testing Monitoring
• Monitoring
Tested code Deployed code Automate Infrastructure as Code Monitoring Tests
Mocks
Tested code Deployed code Automate Infrastructure as Code Monitoring Tests
Mocks Analytics
Part 4 Cloud cometh
Cloud
None
I see more code
I see more code I need more tests
Cloud AWS
Cloud AWS Rackspace GCE HP Joyent
Oh yeah We love cross browser testing?
Part 5 Lessons learned
Health of infrastructure
Health of infrastructure Battle tested code
Health of infrastructure Battle tested code Thorough Monitoring
• Remember to build feedback system . – Test harness
should publish metrics in the same system where ops and project metrics are kept. – Have analytics or trending system on top of the metrics.
Collaborate more with Ops.
Some advice • Remember MIME types? • World wont be
fully automatic ever. Always automate the most time consuming task first. • No easy way out. The function domain requires you to understand man pages, rfps etc. • Choose a text editor rather than an Window manager based IDE.
References • Infra-automation: http://www.opscode.com/chef/ • Monitoring: http://www.nagios.org/ • Lint tool:
http://acrmp.github.com/foodcritic/ • Unit testing: https://github.com/acrmp/chefspec • Functional testing: http://www.cucumber-chef.org/ • Integration testing: https://github.com/calavera/minitest-chef-handler
@RanjibDey http://ranjib.posterous.com http://www.dzone.com/users/ranjibd
[email protected]