CloudOps CloudStack Budapest, 2014

#CCCEU14 | #CloudStackWorks


Test your cloud as code

Pierre-Luc Dion ([email protected])


Overview

• introduction

• Why?

• cloudstack_spec: how it work


About Me

• Cloud Architect @ CloudOps

• Work full time with Apache CloudStack– As user

– As contributor

• Apache CloudStack PMC member

• Ruby and Chef Enthusiast


About CloudOps

• CloudOps builds and operates CloudStack based clouds of all shapes and sizes

• Develops cloud infrastructure solutions and operational models

• 24x7x365 managed service for CloudStack based cloud infrastructures

• Customers are global

• Based in Montreal, Canada


Current state of the project

• Proof of concept

• Support– VPC

– Port Forwarding

– Create snapshot

– Create template from snapshot

– Various zone features validation.



Why ?


What I’m trying to solve

• We have multiple LAB CloudStack installations running multiple versions and configurations. Need to validate their usability.

• CloudStack Release Upgrade tests on real hardware.


Monitoring is not enough

• Monitoring can tell if there is enough Secondary storage. But cannot tell if it’s usable in CloudStack.

• Monitoring cannot tell if Featured templates are usable.



But what about Marvin?


I did not tried Marvin

1. Look like it provision CloudStack configs and tests, right?

2. Defining tests require coding (from user perspective)

3. Could hardly benefit from ServerSpec, specinfra or test-kitchen

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python



cloudstack_spec


The purposes

• Test existing CloudStack installation

• Validate functionality of a Cloud

• Advanced tests:– Port-forwarding rules into VPC

– Create Instance from Snapshot

– Create Template from Snapshot


About cloudstack_spec

• Ruby Rspec based

• Based on ServerSpec

• Test case easy to define

• Use: – cloudstack_ruby_client

– serverspec

– specinfra

• Code maturity: under heavy dev


It is not

• Deployment tool

• Replacement to Marvin

• Monitoring plugin/tool

• Reporting tool



In Action



Define tests


Zone

require 'spec_helper'

describe zone do

it { should exist }

it { should be_allocated }

its(:local_storage) { should be_set }

its(:security_group) { should_not be_set }

its(:network_type) { should match("Advanced") }

end


Zone


describe zone do

it { should exist }





end

Do I have a zone?


Zone


describe zone do

it { should exist }





end

The zone is enabled

(allocated)?


Zone


describe zone do

it { should exist }





end

rspec_its: eval method attributes


Zone


describe zone do

it { should exist }





end

Easy valid on false


Zone


describe zone do

it { should exist }





end

Rspec string validation


Output results



Does my zone have system VMs?


System vm tests

%w(consoleproxy secondarystoragevm).each do |svm|

describe system_vm(svm) do

it { should exist }

it { should be_running }

it { should be_reachable }

end

end


SVMs output



Create VM inside VPC and test the network


VPC test Scope

• Create VPC

• Create VPC network Tier

• Create Instance

• Enable Port-Forwarding for SSH


vpc_spec.rb

describe vpc('spec-vpc1') do

it { should be_created }

it { should exist }

it { should be_ready }


describe vpc_tier('tier11') do


it { should exist }

describe virtual_machine('vm-test1') do


it { should_not be_reachable }

it { should exist }


its(:open_pf_ssh) { should be_set }

context 'With port forwarding' do

it { should be_reachable.with( :port => 22, :proto => 'tcp' ) }

end

end

end

end


vpc_spec.rb



it { should exist }





it { should exist }




it { should exist }





end

end

end

end

be_createdCreate the object


vpc_spec.rb



it { should exist }





it { should exist }




it { should exist }





end

end

end

end

be_reachablePing test


vpc_spec.rb



it { should exist }





it { should exist }




it { should exist }





end

end

end

end

be_reachableTcp connection test

Using Public IP



Results of VPC tests…


test execution (1/4)



Working with Rspec


Custom Rspec matcher

# If the zone is allocated (Enabled)

RSpec::Matchers.define :be_allocated do |expected|

match do |actual|

actual.allocated? == true

end

failure_message do |actual|

"status: #{actual.allocated?}"

end

description do

"be allocated (Enabled)"

end

failure_message_when_negated do |actual|

"Status: #{actual}"

end

end


resources (Test cases)

• Test cases are:– Objects to test are Ruby Class:

CloudstackSpec::Resource::Snapshot

– Unit tests are Ruby Methods inside Class:

self.exist?



What’s next?


Future improvements

• Provide as Gem

• Auto config, same as Serverspec

• More tests

• Better error message

• Add compatibility with ServerSpec

• test-kitchen compatibility?


Help needed

• ServerSpec integration– Test from within an instance

• More test scenarios


Future usage

• Validate new CloudStack release

• Cloud heath check

• Post automation tests

• Continuous Integration Tests (CI)


Conclusion

• Test phase in the automated DevOps world

• Tests definition made easy.

• More tests case in progress.


More Information

• Pierre-Luc Dion– [email protected]

– www.cloudops.com

–@CloudOps_

• Github– https://github.com/pdion891/

cloudstack_spec



Thank you!

CloudOps CloudStack Budapest, 2014

Technology

Transcript of CloudOps CloudStack Budapest, 2014