Testing servers like software
4 likes993 views
The document discusses the use of Serverspec for acceptance testing in server management, providing examples of how to verify server configurations and services. It also compares acceptance testing with monitoring, noting that while the two serve different purposes, Serverspec can be used for both. Additionally, it highlights integration with tools like Test Kitchen and Beaker for testing environments and configurations.
![context 'custom parameters' do
it 'should work with no errors' do
pp = <<-EOS
class { 'swap_file':
swapfile => '/tmp/swapfile',
swapfilesize => '5 MB',
}
EOS
it 'should contain the given swapfile' do
shell('/sbin/swapon -s | grep /tmp/swapfile', :acceptable_exit_codes => [0])
shell('/sbin/swapon -s | grep 5116', :acceptable_exit_codes => [0])
end
end
end
end](https://image.slidesharecdn.com/testingserverslikesoftware-140815104629-phpapp02/85/Testing-servers-like-software-34-320.jpg)
Testing servers like software
- 2. ME DEVELOPER TURNED ops guy WORKING AT KAINOS, CONTRACTING ON GOVERNMENT PROJECTS
- 3. PREVIOUSLY ON THE IER PROJECT NOW LIVE! HTTPS://WWW.GOV.UK/ REGISTER-TO-VOTE
- 4. NOW ON THE DEFRA CAPD PROJECT
- 5. FOREWARNING ▸ Ruby and Puppet Biased ▸ They're the tools I use the most! ▸ But most tools mentioned are system and tool agnostic
- 6. SO YOU'VE MADE A CONFIGURATION CODE CHANGE...
- 9. SO YOU PUSH TO PRODUCTION!
- 13. "Serverspec tests your servers'actual state through SSH access"
- 14. CHECK YOUR SERVER ▸ Is $package installed? ▸ Does file contain $foo? ▸ Does the firewall have the correct rules? ▸ Is service running? ▸ etc...
- 15. RESOURCE TYPES cgroup, command, cron, default_gateway, file, group, host, iis_app_pool, iis_website, interface, ipfilter, ipnat, iptables, kernel_module, linux_kernel_parameter, lxc, mail_alias, package, php_config, port, ppa, process, routing_table, selinux, service, user, windows_feature, windows_registry_key, yumrepo, zfsfs
- 17. return_stdout describe command('cat /etc/resolv.conf') do it { should return_stdout /8.8.8.8/ } end content describe file('/etc/httpd/conf/httpd.conf') do its(:content) { should match /ServerName www.example.jp/ } end
- 19. BE_RESOLVABLE describe host('serverspec.org') do it { should be_resolvable } end describe host('serverspec.org') do it { should be_resolvable.by('hosts') } end describe host('serverspec.org') do it { should be_resolvable.by('dns') } end
- 20. BE_REACHABLE describe host('target.example.jp') do # ping it { should be_reachable } # tcp port 22 it { should be_reachable.with( :port => 22 ) } # set protocol explicitly it { should be_reachable.with( :port => 22, :proto => 'tcp' ) } # udp port 53 it { should be_reachable.with( :port => 53, :proto => 'udp' ) } # timeout setting (default is 5 seconds) it { should be_reachable.with( :port => 22, :proto => 'tcp', :timeout => 1 ) } end
- 21. FULL SPECS FOR A WEB SERVER require 'spec_helper' describe package('apache2') do it { should be_installed } end describe service('apache2') do it { should be_enabled } it { should be_running } end describe port(80) do it { should be_listening } end
- 24. OUR WORKFLOW:CHANGE IN PUPPET MADE => TESTED IN VAGRANT INSTANCE CODE REVIEWED, PASSES CI AND MERGED PUSHED TO INTEGRATION ENVIRONMENT SERVERSPEC TESTS RUN ON INTEGRATION ENVIRONMENT ANY ISSUES: FIX OR IF BIG ENOUGH, REVERT CONTINUES DOWN THE PIPELINE TO PRODUCTION
- 25. SERVERSPEC: PRETTY NEAT BUT THERE'S ALSO LANGUAGE SPECIFIC TOOLS!
- 26. TEST KITCHEN
- 27. ▸ Uses serverspec as it's core ▸ It's basically helper wrappers to install chef ▸ And run the cookbooks given ▸ Used for cookbook acceptance testing
- 30. BEAKER
- 31. ▸ Again: serverspec as it's core ▸ But specs customised with Puppet references ▸ Specific rspec grammer around running manifests etc.
- 33. require 'spec_helper_acceptance' describe 'swap_file class', :unless => UNSUPPORTED_PLATFORMS.include?(fact('osfamily')) do context 'swap_file' do context 'ensure => present' do it 'should work with no errors' do pp = <<-EOS class { 'swap_file': } EOS # Run it twice and test for idempotency expect(apply_manifest(pp).exit_code).to_not eq(1) expect(apply_manifest(pp).exit_code).to eq(0) end
- 34. context 'custom parameters' do it 'should work with no errors' do pp = <<-EOS class { 'swap_file': swapfile => '/tmp/swapfile', swapfilesize => '5 MB', } EOS it 'should contain the given swapfile' do shell('/sbin/swapon -s | grep /tmp/swapfile', :acceptable_exit_codes => [0]) shell('/sbin/swapon -s | grep 5116', :acceptable_exit_codes => [0]) end end end end
- 35. I KNOW WHAT YOU MIGHT BE THINKING...
- 36. Wait, whats the difference between this and monitoring?
- 37. MONITORING KEEP THE LIGHTS ON ▸ "Fix me now!" issues ▸ Dynamic changes - Things crashing, hard drives are full
- 38. ACCEPTANCE "MY CHANGES DIDN'T BREAK ANYTHING" ▸ Smoke tests ▸ Human readable ▸ One-off for edge-cases ▸ Auditing
- 39. HOWEVER
- 40. USING SERVERSPEC AS MONITORING IS POSSIBLE! AND HAS SOME PRETTY SWEET BENEFITS HTTP://WWW.SLIDESHARE.NET/M_RICHARDSON/SERVERSPEC-AND-SENSU-TESTING-AND-MONITORING- COLLIDE
- 41. Q&A
- 42. LINKShttp://serverspec.org/ http://vincent.bernat.im/en/blog/2014-serverspec-test- infrastructure.html https://github.com/serverspec/serverspec http://www.debian-administration.org/article/703/ A_brief_introduction_to_server-testing_with_serverspec "ChefConf 2014: Gosuke Miyashita, "Serverspec: The Simplest Server Testing Tool Ever" - http://www.youtube.com/watch? v=6GvlHImeloo*