virtualmonkey 0.0.1

data/features/old_cuke_features/Steps-TODO

@@ -0,0 +1,31 @@
+FEs
+3233 a2enmod deflate needs to be added in the apache install script for Ubuntu FE's
+3248 Apache modules are not installed properly for Ubuntu images
+2700 haproxy plugin for collectd is not working
+3378 Apache doesn't properly serve static content, due to a bad Rewrite Condition
+3379 Add "LB get HA proxy config" to all Front End ST
+1401 entering "yes" for the OPT_PHP_ENABLE script breaks the install'
+3302 Ubuntu Apache access_log doesn't get rotated
+
+HAProxy
+3300 HAProxy Add scripts user sed -i.orig which causes duplicate plugins in processes.conf
+3225 Collectd plugin does not work with HAProxy 1.3
+3223 LB HA proxy install v5: Script bug with Ubuntu RightImages
+2700 haproxy plugin for collectd is not working
+3279 Better race condition code for haproxy connect/disconnect backend
+3312 Front End HAProxy templates do not rotate /var/log/httpd/haproxy.log
+3332 HAProxy templates should not have a default value for HEALTH_CHECK_URI
+3413 haproxy 1.3 won't start with no servers registered
+
+MySQL
+3381 MySQL logs not configured in logrotate.
+3399 MySQL 5.1 EBS v2 support for new size
+3175 Initialize slave from slave snapshot
+3303 MySQL shared default configuration files do not properly enable logging
+3324 MySQL keeps bin logs forever eventually consuming entire disk
+3391 MySQL binlogs are not properly rotated on CentOS
+3136 MySql Ubuntu - Logging not configured in my.cnf
+3012 verify low TTL for mysql/EBS server
+652 MySQL, collectd needs to be restart after promote to master
+
+

data/features/old_cuke_features/app_state.feature

@@ -0,0 +1,25 @@
+@app_state
+
+Feature: Unified App Server Test
+  Tests the RightScale app servers
+
+Scenario: App server test
+
+  Given A deployment
+  When I launch the frontends
+  And I hack the frontend rc crap
+  Then the frontends become operational  
+
+  When I launch the appservers
+  And I hack the appservers rc crap
+  Then the appservers become operational  
+
+  When I reboot the frontends
+  Then the frontends become non-operational
+  Then the frontends become operational  
+
+  When I reboot the appservers
+  Then the appservers become non-operational  
+  Then the appservers become operational  
+
+

data/features/old_cuke_features/app_test.feature

@@ -0,0 +1,24 @@
+@app_test
+
+Feature: Unified App Server Test
+  Tests the RightScale app servers
+
+Scenario: App server test
+
+  Given A deployment
+
+  When I query "/index.html" on all servers
+  Then I should see "html serving succeeded." in all the responses
+
+  When I query "/appserver/" on all servers
+  Then I should see "configuration=succeeded" in all the responses 
+
+  When I query "/dbread/" on all servers
+  Then I should see "I am in the db" in all the responses
+
+  When I query "/serverid/" on all servers
+  Then I should see "hostname=" in all the responses
+
+  When I query "/dbread/" on all servers
+  Then I should see "I am in the db" in all the responses
+

data/features/old_cuke_features/base.feature

@@ -0,0 +1,16 @@
+@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 launch all servers
+  Then I should wait for the state of "all" servers to be "operational"
+  Then I should check that monitoring is enabled
+  Then I should reboot the servers
+  Then I should wait for the state of "all" servers to be "operational"
+  Then I should check that monitoring is enabled
+

data/features/old_cuke_features/chef_quickstart.feature

@@ -0,0 +1,11 @@
+@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 I should check that monitoring is enabled

data/features/old_cuke_features/db_toolbox.feature

@@ -0,0 +1,38 @@
+@mysql_5.x
+Feature: mysql toolbox
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Run all toolbox scripts
+#
+# PHASE 1) Launch a few DB servers.  Make one the master.
+#
+    Given A MySQL Toolbox deployment
+    Then I should set a variation MySQL DNS
+    Then I should set a variation lineage
+    Then I should set a variation stripe count of "3"
+    Then I should set a variation volume size "3"
+
+    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 I should create master from scratch
+
+#
+# PHASE 2) Run checks for the basic scripts
+#
+# We need a non-mysql server that doesn't have continuous backups enabled
+#   Then I should test the backup script operations
+
+#
+# PHASE 3) restore the snapshot on another server
+#
+   Then I should backup the volume
+#   Then I should test the restore operations
+
+#
+# PHASE 4) Do the grow EBS tests
+#
+    Then I should test the restore grow operations
+#
+#
+#    Then I should stop the servers

data/features/old_cuke_features/ebs_toolbox.feature

@@ -0,0 +1,39 @@
+@ebs
+Feature: EBS toolbox tests
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Run all EBS toolbox operational scripts
+#
+# PHASE 1) Launch a toolbox server and create an EBS stripe with "interesting" data on it.
+#  How many servers do we need?  Launch them all and figure it out later.
+#
+    Given A EBS Toolbox deployment
+    Then I should set a variation lineage
+    Then I should set a variation stripe count of "3"
+    Then I should set a variation volume size "3"
+    Then I should set a variation mount point "/mnt/ebs"
+    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 I should create a new EBS stripe
+
+#
+# PHASE 2) Run checks for the basic scripts
+#
+   Then I should test the backup script operations
+
+#
+# PHASE 3) restore the snapshot on another server
+#
+   Then I should backup the volume
+   Then I should test the restore operations
+
+#
+# PHASE 4) Do the grow EBS tests
+#
+    Then I should test the restore grow operations
+#
+#
+    Then I should test reboot operations on the deployment
+#
+    Then I should stop the servers

data/features/old_cuke_features/elb_create_delete.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/elb_generic.feature

@@ -0,0 +1,27 @@
+@elb_test
+
+Feature: PHP App Server Elastic Load Balancing test
+  Tests the Elastic Load Balancing RightScripts using an 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 stop the servers
+    Then no instances should be registered with ELB
+       
+    When I delete EC2 Elastic Load Balancer
+    
+    

data/features/old_cuke_features/fe_app_checks.feature

@@ -0,0 +1,21 @@
+@lb_test
+
+Feature: PHP Server Test
+  Tests the PHP servers (checks only).  Assumes all servers are already operational or can be launched to operational and have the correct config.
+
+Scenario: PHP server test (checks only)
+
+  Given A frontend with application servers deployment
+
+  When I launch the "Front End" servers
+  Then I should wait for the state of "Front End" servers to be "operational"
+
+  When I launch the "App Server" servers
+  Then I should wait for the state of "App Server" servers to be "operational"
+
+# Optional:
+#  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

data/features/old_cuke_features/just-start.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/lamp.feature

@@ -0,0 +1,15 @@
+@lamp_test
+
+Feature: LAMP Server Template Test
+  Tests the deployment
+
+Scenario: LAMP Server Template Test
+
+  Given A LAMP 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 I should run LAMP checks
+  Then I should run mysql checks
+#  Then I should run mysqlslap stress test
+  Then I should check that ulimit was set correctly

data/features/old_cuke_features/lb-apache-haproxy.feature

@@ -0,0 +1,27 @@
+@lb_test
+
+Feature: LB Server Test
+  Tests the LB servers
+
+Scenario: LB server test
+
+  Given An Apache with HAproxy deployment
+  Then I should stop the servers
+  Then I should set a variation for connecting to shared database host
+
+  When I launch the "Load Balancer" servers
+  Then I should wait for the state of "Load Balancer" 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 "operational"
+
+  Then I should run unified application checks
+  Then I should run frontend checks
+  Then I should run log rotation checks
+
+# TODO?
+  #When I restart apache
+  #Then apache status should be good
+
+  Then I should test reboot operations on the deployment

data/features/old_cuke_features/mysql_5.x_v2_v4_from_scratch.feature

@@ -0,0 +1,33 @@
+@mysql_5.x
+Feature: mysql 5.x v2 or v4 promote operations test
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Setup 2 server deployment and run basic cluster failover operations
+#
+# PHASE 1) Bootstrap and test promote
+#
+    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 "1"
+    Then I should set a variation MySQL DNS
+    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 test promotion operations on the deployment
+    Then I should run mysql checks
+#    Then I should run mysqlslap stress test
+    Then I should check that ulimit was set correctly
+    Then I should check that monitoring is enabled
+
+#
+# PHASE 2) Reboot
+#
+
+    Then I should test reboot operations on the deployment
+
+#
+# PHASE 3) Additional Tests
+#
+
+    Then I should run a restore using OPT_DB_RESTORE_TIMESTAMP_OVERRIDE

data/features/old_cuke_features/mysql_5.x_v2_v4_from_scratch_awsdns.feature

@@ -0,0 +1,33 @@
+@mysql_5.x
+Feature: mysql 5.x v2 or v4 promote operations test
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Setup 2 server deployment and run basic cluster failover operations
+#
+# PHASE 1) Bootstrap and test promote
+#
+    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 "1"
+    Then I should set a variation AWSDNS provider
+    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 test promotion operations on the deployment
+    Then I should run mysql checks
+#    Then I should run mysqlslap stress test
+    Then I should check that ulimit was set correctly
+    Then I should check that monitoring is enabled
+
+#
+# PHASE 2) Reboot
+#
+
+    Then I should test reboot operations on the deployment
+
+#
+# PHASE 3) Additional Tests
+#
+
+    Then I should run a restore using OPT_DB_RESTORE_TIMESTAMP_OVERRIDE

data/features/old_cuke_features/mysql_5.x_v2_v4_from_scratch_dyndns.feature

@@ -0,0 +1,33 @@
+@mysql_5.x
+Feature: mysql 5.x v2 or v4 promote operations test
+  Tests the RightScale premium ServerTemplate
+
+  Scenario: Setup 2 server deployment and run basic cluster failover operations
+#
+# PHASE 1) Bootstrap and test promote
+#
+    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 "1"
+    Then I should set a variation DNS provider
+    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 test promotion operations on the deployment
+    Then I should run mysql checks
+#    Then I should run mysqlslap stress test
+    Then I should check that ulimit was set correctly
+    Then I should check that monitoring is enabled
+
+#
+# PHASE 2) Reboot
+#
+
+    Then I should test reboot operations on the deployment
+
+#
+# PHASE 3) Additional Tests
+#
+
+    Then I should run a restore using OPT_DB_RESTORE_TIMESTAMP_OVERRIDE