virtualmonkey 0.0.1

data/features/old_cuke_features/mysql_chef_premium.feature

@@ -0,0 +1,27 @@
+Feature: mysql_db premium resources and master/slave cluster operations
+  Tests the RightScale premium ServerTemplate Mysql Chef (alpha)
+
+  Scenario: Basic cluster failover operations
+    Given A deployment. 
+    And "2" operational servers
+    Then I should run a mysql query "drop database mynewtest" on server "1"
+    Then I should run a mysql query "drop database mynewtest" on server "2"
+    When I run a recipe named "db_mysql::do_restore_and_become_master" on server "1". 
+    Then it should converge successfully
+
+    Then I should sleep 10 seconds
+
+    When I run a recipe named "db_mysql::do_init_slave" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_backup" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_disable_backup" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_enable_backup" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_promote_to_master" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_disable_backup" on server "2"
+    Then it should converge successfully
+    When I run a recipe named "db_mysql::do_enable_backup" on server "2"
+    Then it should converge successfully

data/features/old_cuke_features/mysql_chef_premium_from_scratch.feature

@@ -0,0 +1,37 @@
+Feature: mysql_db premium resources and master/slave cluster operations
+  Tests the RightScale premium ServerTemplate Mysql Chef (alpha). Starting from a fresh database (no prior backup required)
+
+  Scenario: Basic cluster failover operations and backup from scratch
+    Given A deployment
+    Then I should set a variation lineage
+    Then I should set a variation bucket
+    And "2" operational servers
+    Then I should run a mysql query "create database mynewtest" on server "1"
+
+    When I run a recipe named "db_mysql::setup_admin_privileges" on server "1"
+    Then it should converge successfully
+    Then the audit entry should NOT contain "Found buggy mysql"
+    
+    When I run a recipe named "db_mysql::setup_replication_privileges" on server "1"
+    Then it should converge successfully
+    
+    When I run a recipe named "db_mysql::do_tag_as_master" on server "1"
+    Then it should converge successfully
+
+    When I run a recipe named "db_mysql::do_backup" on server "1"
+    Then it should converge successfully
+
+    Then I should sleep 10 seconds
+    
+    When I run a recipe named "db_mysql::do_init_slave" on server "2"
+    Then it should converge successfully
+
+    When I run a recipe named "db_mysql::do_promote_to_master" on server "2"
+    Then it should converge successfully
+
+    When I run a recipe named "db_mysql::do_enable_backup" on server "2"
+    Then it should converge successfully
+
+    When I run a recipe named "db_mysql::do_disable_backup" on server "2"
+    Then it should converge successfully
+    

data/features/old_cuke_features/mysql_v1_upgrade_v2.feature

@@ -0,0 +1,42 @@
+@mysql_5.x
+Feature: mysql 5.x v1 to v2 upgrade tests
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Follow the steps in the v1 to v2 upgrade guide. Then run the mysql checks.
+# http://support.rightscale.com/03-Tutorials/02-AWS/02-Website_Edition/2.1_MySQL_Setup/MySQL_Setup_Migration%3a__EBS_to_EBS_Stripe
+#
+# PHASE 1) Launch a v1 master from a known hardcoded snapshot.
+#  TODO - add the steps to create the v1 master from scratch.  The upgrade is the major
+#         concern so lets get that done first.
+#  Prerequisite: A Deployment with a running MySQL EBS Master-DB server 
+#  (launched using a revision of the "MySQL EBS v1" ServerTemplate)
+# Old school hand crafted deployment: https://my.rightscale.com/deployments/49925.  Make sure
+# The one server is still up and running as master DB.
+#
+    Given A MySQL deployment
+    Then I should stop the servers
+    Then I should set a variation lineage
+    Then I should set a variation stripe count of "3"
+# This is done when the deployment is setup - the master never changes the scripts use the inputs as set
+#    Then I should set the master DNS to a hardcoded value
+#    Then I should set the v1 ebs prefix to a hardcoded value
+
+#
+# PHASE 2) Launch a new v2 server and migrate from v1
+#
+    Then I should launch all servers
+    Then I should wait for the state of "all" servers to be "operational"
+# Run "DB EBS create migrate script from EBS non-stripe master"
+    Then I should create the migration script
+# ssh to box and run "/tmp/init_slave.sh"
+    Then I should migrate a new slave
+#    Then I should test that new slave is working
+
+#
+# PHASE 3) Initialize additional slave from v2 snapshots
+#
+    Then I should init a new v2 slave
+    Then I should test the new v2 slave
+#    Then I should run mysqlslap stress test
+    Then I should check that ulimit was set correctly
+

data/features/old_cuke_features/php.feature

@@ -0,0 +1,27 @@
+@lb_test
+
+Feature: PHP Server Templates
+  Tests the PHP servers
+
+Scenario: PHP server test
+
+  Given A frontend with application servers deployment
+  Then I should stop the servers
+  Then I should set a variation for connecting to shared database host
+
+  When I launch the "Front End" servers
+  Then I should wait for the state of "Front End" servers to be "booting"
+  Then I should wait for the state of "Front End" servers to be "operational"
+  Then I should set a variation LB_HOSTNAME
+  When I launch the "App Server" servers
+  Then I should wait for the state of "App Server" servers to be "booting"
+  Then I should wait for the state of "App Server" servers to be "operational"
+  Then I should cross connect the frontends
+
+  Then I should run unified application checks
+  Then I should run frontend checks
+  Then I should run log rotation checks
+
+  Then I should test reboot operations on the deployment
+
+  Then I should check that monitoring is enabled

data/features/old_cuke_features/php_aio_trial_chef_alpha.feature

@@ -0,0 +1,11 @@
+@php_aio_trial_chef_test
+
+Feature: PHP AIO Trial (Chef Alpha) Server Template Test
+  Tests the deployment
+
+Scenario: PHP AIO Trial Server Template test
+
+  Given A PHP AIO Trial Chef deployment
+  Then I should stop the servers
+  Then I should launch all servers
+  Then I should wait for the state of "all" servers to be "operational"

data/features/old_cuke_features/php_chef.feature

@@ -0,0 +1,21 @@
+@lb_test
+
+Feature: PHP Chef Server Template
+  Tests the deployment
+
+Scenario: PHP Chef Server Templates, PHP FrontEnd and PHP App
+
+  Given A PHP Chef deployment
+  Then I should stop the servers
+  Then I should set a variation for connecting to shared database host
+
+  Then I should launch the deployment
+
+  Then I should cross connect the frontends
+
+  Then I should run unified application checks
+  Then I should run frontend checks
+  Then I should run log rotation checks
+
+  Then I should test reboot operations on the deployment
+  Then I should check that monitoring is enabled

data/features/old_cuke_features/php_elb.feature

@@ -0,0 +1,41 @@
+@elb_test
+
+Feature: PHP App Server Elastic Load Balancing test
+  Tests the Elastic Load Balancing RightScripts using PHP App Server 
+
+Scenario: Connect/Disconnect PHP App Server to ELB
+
+  Given An ELB Test deployment
+  
+   When I create EC2 Elastic Load Balancer
+  
+   Then I should stop the servers
+   Then I should set a variation for connecting to shared database host 
+   Then I should set a variation ELB_NAME
+   When I launch the "App Server" servers
+   Then I should wait for the state of "App Server" servers to be "booting"
+   Then I should wait for the state of "App Server" servers to be "operational"
+ 
+   Then I should run EC2 Elastic Load Balancer unified_app checks
+   Then all instances should be registered with ELB
+#   Then I should run log rotation checks
+#   Then I should check that monitoring is enabled
+  
+#   Then I should reboot the servers
+
+#   Then I should run EC2 Elastic Load Balancer unified_app checks
+#   Then all instances should be registered with ELB
+#   Then I should run log rotation checks
+#   Then I should check that monitoring is enabled
+ 
+    Then I should stop the servers
+    Then no instances should be registered with ELB
+       
+    When I delete EC2 Elastic Load Balancer
+#    When I launch the "App Server" servers
+#    When I should wait for the state of "App Server" servers to be "booting"
+    
+#    Then I should wait for the state of "App Server" servers to be "stranded"
+#    Then I should stop the servers
+    
+    

data/features/old_cuke_features/rails.feature

@@ -0,0 +1,26 @@
+@lb_test
+
+Feature: Rails Server Test
+  Tests the Rails servers
+
+Scenario: Rails server test
+
+  Given A frontend with application servers deployment
+  Then I should stop the servers
+  Then I should set a variation for connecting to shared database host
+  When I launch the "Front End" servers
+  Then I should wait for the state of "Front End" servers to be "booting"
+  Then I should wait for the state of "Front End" servers to be "operational"
+  Then I should set a variation LB_HOSTNAME
+  When I launch the "App Server" servers
+  Then I should wait for the state of "App Server" servers to be "booting"
+  Then I should wait for the state of "App Server" servers to be "operational"
+  Then I should cross connect the frontends
+
+  Then I should run unified application checks
+  Then I should run frontend checks
+  Then I should run log rotation checks
+
+  Then I should test reboot operations on the deployment
+
+  Then I should check that monitoring is enabled

data/features/old_cuke_features/rails_aio_developer_chef.feature

@@ -0,0 +1,17 @@
+@rails_aio_developer_chef
+
+Feature: Rails AIO Developer (Chef Alpha) Server Template Test
+  Rails AIO Developer (Chef Alpha) Server Template Test AND
+  Rails AIO Demo (Chef Alpha) Server Template Test
+
+Scenario: Rails AIO (Chef Alpha) Server Template Test
+
+  Given A Rails AIO Developer Chef deployment
+  #Then I should stop the servers
+  Then I should launch all servers
+  Then I should wait for the state of "all" servers to be "booting"
+  Then I should wait for the state of "all" servers to be "operational"
+  Then I should run AIO rails demo application checks
+  Then I should run log rotation checks
+
+  #Then I should test reboot operations on the deployment

data/features/old_cuke_features/reboot.feature

@@ -0,0 +1,23 @@
+@reboot_test
+
+Feature: Reboot Server Test
+  Tests the Reboot servers
+
+Scenario: Reboot server test
+
+  Given A deployment
+
+  When I launch the "frontend" servers
+  Then the "frontend" servers become operational
+
+  When I launch the "app" servers
+  Then the "frontend" servers become operational
+
+  Given I am testing the "frontend"
+  When I reboot the servers
+  And the "frontend" servers become operational
+
+  Given I am testing the "app"
+  When I reboot the servers
+  And the "app" servers become operational
+

data/features/old_cuke_features/rightlink.feature

@@ -0,0 +1,19 @@
+@rightlink
+Feature: RightLink Feature Tests
+
+  Make sure rightlink supports the expected functionality 
+
+  Scenario: The RightLink Test template should go operational
+    Given A simple deployment
+    Then I should stop the servers
+    Then I should launch all servers
+    Then I should wait for the state of "all" servers to be "operational"
+
+    Then all servers should successfully run a recipe named "rightlink_test::state_test_check_value".
+    
+    When I run a recipe named "rightlink_test::resource_remote_recipe_test_start" on server "1". 
+    Then it should converge successfully.   
+    Then I should sleep 10 seconds.
+    Then I should see "resource_remote_recipe_ping" in the log on server "2".  
+    
+    Then I should check that monitoring is enabled

data/features/old_cuke_features/rsgrid.feature

@@ -0,0 +1,19 @@
+@grid
+
+Feature: Grid Server Test
+  Tests the Reboot servers
+
+Scenario: Grid server test
+
+  Given A deployment with "16" servers
+
+  When I launch all servers
+  Then the "all" servers become operational
+
+  Given I am testing the "all"
+  When I reboot the servers
+  And the "all" servers become operational
+
+# Just reboot the controllers - the workers will terminate if rebooted
+#
+# Run the Grid macro - then update the rsgrid.json with the input for the new deployment

data/features/old_cuke_features/simple.feature

@@ -0,0 +1,8 @@
+@lb_test
+
+Feature: PHP Server Test
+  Tests the PHP servers
+
+Scenario: PHP server test
+
+  Given A simple deployment

data/features/old_cuke_features/simple_fail.feature

@@ -0,0 +1,9 @@
+@lb_test
+
+Feature: PHP Server Test
+  Tests the PHP servers
+
+Scenario: PHP server test
+
+  Given A simple deployment
+  Then I will fail

data/features/old_cuke_features/start-stop.feature

@@ -0,0 +1,13 @@
+@base
+
+Feature: Base Server Test
+  Tests the base server functions
+
+Scenario: base server test
+
+  Given A simple deployment
+#  Then I should stop the servers
+#  Then I should relaunch all servers
+  Then I should launch all servers
+  Then I should wait for the state of "all" servers to be "operational"
+  Then I should perform start stop operations.

data/features/old_cuke_features/step_definitions/app.rb

@@ -0,0 +1,21 @@
+require File.expand_path(File.join(File.dirname(__FILE__) , '..','..','spec','spec_helper'))
+
+Then /I should run unified application checks/ do
+  @runner.run_unified_application_checks
+end
+
+Then /I should run LAMP checks/ do
+  @runner.run_lamp_checks
+end
+
+Then /I should run AIO rails demo application checks/ do
+  @runner.run_rails_demo_application_checks
+end
+
+Then /^I should set a variation for connecting to shared database host/ do
+  @runner.set_master_db_dnsname
+end
+
+Then /^I should launch the deployment/ do
+  @runner.startup_sequence
+end

data/features/old_cuke_features/step_definitions/deployment_steps.rb

@@ -0,0 +1,112 @@
+require File.expand_path(File.join(File.dirname(__FILE__) , '..','..','spec','spec_helper'))
+
+Given /^A simple deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::SimpleRunner.new(ENV['DEPLOYMENT'])
+end
+
+Given /^A LAMP deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::LampRunner.new(ENV['DEPLOYMENT'])
+end
+
+Given /^An ELB Test deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::ELBRunner.new(ENV['DEPLOYMENT'])
+  @runner.lookup_scripts
+end
+
+Given /^A PHP Chef deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::PhpChefRunner.new(ENV['DEPLOYMENT'])
+end
+
+Given /A Rails AIO Developer Chef deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::RailsAioDeveloperChefRunner.new(ENV['DEPLOYMENT'])
+end
+
+Given /^A PHP AIO Trial Chef deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+  @runner = VirtualMonkey::PhpAioTrialChefRunner.new(ENV['DEPLOYMENT'])
+end
+
+Given /^A MySQL Toolbox deployment$/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+
+  @runner = VirtualMonkey::MysqlToolboxRunner.new(ENV['DEPLOYMENT'])
+  @runner.lookup_scripts
+end
+
+Given /A MySQL deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+
+  @runner = VirtualMonkey::MysqlRunner.new(ENV['DEPLOYMENT'])
+  @runner.lookup_scripts
+end
+
+Given /A frontend with application servers deployment/ do
+  raise "FATAL:  Please set the environment variable $DEPLOYMENT" unless ENV['DEPLOYMENT']
+
+# EXPERIMENTAL
+# sleep here to delay the run of the cucumber initial calls to the api. (be nice)
+#  num = rand(120)
+#  puts "delaying start of test by #{num} seconds"
+#  sleep num
+#  Don't think this really helped, but, if we start really really pounding the site we may want to add
+#  it back in
+  @runner = VirtualMonkey::FeAppRunner.new(ENV['DEPLOYMENT'])
+  @runner.lookup_scripts
+end
+
+Then /I will fail/ do
+  raise "Test failure simulation!"
+end
+
+Then /I should test reboot operations on the deployment/ do
+  @runner.run_reboot_operations
+end
+
+When /^I launch the "([^\"]*)" servers$/ do |server_set|
+  @runner.launch_set(server_set)
+end
+
+Then /^I should relaunch all servers$/ do
+  @runner.relaunch_all
+end
+
+Then /I should wait for the state of \"(.*)\" servers to be \"(.*)\"/ do |set,state|
+  if set == "all"
+    @runner.wait_for_all(state)
+  else
+    @runner.wait_for_set(set, state)
+  end
+end
+
+Then /^I should stop_ebs all servers$/ do
+  @runner.stop_ebs_all
+end
+
+Then /^I should start_ebs all servers$/ do
+  @runner.start_ebs_all
+end
+
+Then /I should reboot the servers$/ do
+  @runner.reboot_all
+end
+
+Then /I should stop the servers$/ do
+  @runner.stop_all
+end
+
+Then /I should launch all servers$/ do
+  @runner.launch_all
+end
+
+Then /I should check that monitoring is enabled$/ do
+  @runner.check_monitoring
+end
+
+Then /^I should perform start stop operations\.$/ do
+  @runner.perform_start_stop_operations
+end