vagrant-orchestrate 0.4.1 → 0.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: aa8ac72aee45a656c1a9e60a575c995075ddb053
-  data.tar.gz: a242a2fbad92acb639515f796ca8543989f07f05
+  metadata.gz: 9057f96a7ecd5de9313d115b4c9dc0e0e43b47bf
+  data.tar.gz: 9155032e7fc9a2366c9e60e4c22c4466399a7e85
 SHA512:
-  metadata.gz: f6f36cc9190db80c3f91676533aa0e0f3856e0547dc88b62fda842ad3a413d0a4ca1389104bf2aa764d9946753e1b1bb895a76ee0d20a36255ef30a94ec3ea29
-  data.tar.gz: 303e98568405ab411a3e405d35c0b7aee9c1144480385afbc48f726ee05f0343ea50b95fbebd7c262f296415b71e40d73a282012690d943ecaf2304b0bf28ceb
+  metadata.gz: dbe677786084f036f395bf0e5cb0790560674eaefdfd47ba355a6890e047fb8573d16295360c7d37b7a6c6f1167d9ecbc6c756f5bf405c638cedd430dd7df879
+  data.tar.gz: 677b58e92422f62a2d063fe54e1bbffc8a0d95eb3b057b92eb066b4e2f8b2a53a5c1bb22f2f87087a0dd84eccb5e48d63e887db3a3614d13b4152e39fc1b77df

data/.travis.yml

@@ -0,0 +1,10 @@
+language: ruby
+rvm:
+- 2.0.0
+deploy:
+  provider: rubygems
+  gem: vagrant-orchestrate
+  on:
+    tags: true
+  api_key:
+    secure: qKr5F4kkezl1Vp+wfPX/8IO/7O6lqVqut6/Op1baALCWTtrSLyJpBND1fWaKVf01NZiJTmNXhCTHAEzZjbGkiqBpSqMdR2g8ISxEgj8hScw46RLmYBzH6RdL503O1j7HHyJNf2cUPQjjzLNriPowYhp92aut4z0bMCxZer7bd8o=

data/README.md

@@ -1,5 +1,10 @@
+[![Build Status](https://travis-ci.org/Cimpress-MCP/vagrant-orchestrate.svg?branch=master)](https://travis-ci.org/Cimpress-MCP/vagrant-orchestrate)
+[![Gem Version](https://badge.fury.io/rb/vagrant-orchestrate.svg)](http://badge.fury.io/rb/vagrant-orchestrate)
+
 # Vagrant Orchestrate
 
+![](http://i.imgur.com/71yAw5v.gif)
+
 This is a Vagrant 1.6+ plugin that allows orchestrated deployments
 to already provisioned (non-elastic) servers on top of the excellent vagrant-managed-servers plugin.
 It features a powerful templating `init` command and is designed from the
@@ -262,8 +267,8 @@ The push command is currently limited by convention to vagrant machines that use
 
 #### Deployment Strategy
 
-Vagrant Orchestrate supports several deployment [strategies](docs/strategy.md) including parallel, canary and
-blue-green.
+Vagrant Orchestrate supports several deployment [strategies](docs/strategy.md) including parallel, canary, and
+half and half.
 
 You can push changes to all of your servers in parallel with
 

data/docs/strategy.md

@@ -1,7 +1,7 @@
 # Deployment Strategies
 
 Vagrant Orchestrate supports several deployment strategies including parallel and
-blue-green. Here we'll cover how to use the various strategies as well as describing
+half and half. Here we'll cover how to use the various strategies as well as describing
 situations when each might be useful.
 
 ## Strategies
@@ -36,9 +36,8 @@ provision [trigger](https://github.com/emyl/vagrant-triggers) to run a smoke tes
 
     config.orchestrate.strategy = :canary
 
-### Blue Green
-The [Blue Green](http://martinfowler.com/bliki/BlueGreenDeployment.html) deployment
-strategy deploys to half of the cluster in parallel, then the other half, with
+### Half and Half
+Deploys to half of the cluster in parallel, then the other half, with
 a pause in between. This won't manage any of your load balancing or networking
 configuration for you, but if your application has a healthcheck that your load
 balancer respects, it should be easy to turn it off at the start of your provisioning
@@ -47,19 +46,19 @@ then this will be the best blend of getting the deployment done quickly and main
 a running application. If the total number of target servers is odd then the smaller
 number will be deployed to first.
 
-    $ vagrant orchestrate push --strategy blue_green
+    $ vagrant orchestrate push --strategy half_half
 
-    config.orchestrate.strategy = :blue_green
+    config.orchestrate.strategy = :half_half
 
-### Canary Blue Green
+### Canary Half and Half
 Combines the two immediately above - deploying to a single
 server, pausing, then to half of the remaining cluster in parallel, pausing, and then the other half,
 also in parallel. This is good if you have a large number of servers and want to do a
 smoke test of a single server before committing to pushing to half of your farm.
 
-    $ vagrant orchestrate push --strategy canary_blue_green
+    $ vagrant orchestrate push --strategy canary_half_half
 
-		config.orchestrate.strategy = :canary_blue_green
+		config.orchestrate.strategy = :canary_half_half
 
 ## Specifying a strategy
 

data/lib/vagrant-orchestrate/command/push.rb

@@ -63,7 +63,7 @@ module VagrantPlugins
 
           # Handle a couple of them more tricky edges.
           strategy = :serial if machines.size == 1
-          strategy = :blue_green if strategy.to_sym == :canary_blue_green && machines.size == 2
+          strategy = :half_half if strategy.to_sym == :canary_half_half && machines.size == 2
 
           case strategy.to_sym
           when :serial
@@ -74,11 +74,11 @@ module VagrantPlugins
           when :canary
             # A single canary server and then the rest
             result = deploy(options, machines.take(1), machines.drop(1))
-          when :blue_green
+          when :half_half
             # Split into two (almost) equal groups
             groups = split(machines)
             result = deploy(options, groups.first, groups.last)
-          when :canary_blue_green
+          when :canary_half_half
             # A single canary and then two equal groups
             canary = machines.take(1)
             groups = split(machines.drop(1))

data/lib/vagrant-orchestrate/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module Orchestrate
-    VERSION = "0.4.1"
+    VERSION = "0.4.2"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-orchestrate
 version: !ruby/object:Gem::Version
-  version: 0.4.1
+  version: 0.4.2
 platform: ruby
 authors:
 - Christopher Baldauf
@@ -76,6 +76,7 @@ files:
 - .gitignore
 - .rspec
 - .rubocop.yml
+- .travis.yml
 - Gemfile
 - LICENSE
 - README.md