stack-kicker 0.0.1 → 0.0.2

data/.rvmrc

@@ -0,0 +1,48 @@
+#!/usr/bin/env bash
+
+# This is an RVM Project .rvmrc file, used to automatically load the ruby
+# development environment upon cd'ing into the directory
+
+# First we specify our desired <ruby>[@<gemset>], the @gemset name is optional,
+# Only full ruby name is supported here, for short names use:
+#     echo "rvm use 1.9.3" > .rvmrc
+environment_id="ruby-1.9.3-p286@stack-kicker"
+
+# Uncomment the following lines if you want to verify rvm version per project
+# rvmrc_rvm_version="1.16.17 (stable)" # 1.10.1 seams as a safe start
+# eval "$(echo ${rvm_version}.${rvmrc_rvm_version} | awk -F. '{print "[[ "$1*65536+$2*256+$3" -ge "$4*65536+$5*256+$6" ]]"}' )" || {
+#   echo "This .rvmrc file requires at least RVM ${rvmrc_rvm_version}, aborting loading."
+#   return 1
+# }
+
+# First we attempt to load the desired environment directly from the environment
+# file. This is very fast and efficient compared to running through the entire
+# CLI and selector. If you want feedback on which environment was used then
+# insert the word 'use' after --create as this triggers verbose mode.
+if [[ -d "${rvm_path:-$HOME/.rvm}/environments"
+  && -s "${rvm_path:-$HOME/.rvm}/environments/$environment_id" ]]
+then
+  \. "${rvm_path:-$HOME/.rvm}/environments/$environment_id"
+  [[ -s "${rvm_path:-$HOME/.rvm}/hooks/after_use" ]] &&
+    \. "${rvm_path:-$HOME/.rvm}/hooks/after_use" || true
+else
+  # If the environment file has not yet been created, use the RVM CLI to select.
+  rvm --create  "$environment_id" || {
+    echo "Failed to create RVM environment '${environment_id}'."
+    return 1
+  }
+fi
+
+# If you use bundler, this might be useful to you:
+# if [[ -s Gemfile ]] && {
+#   ! builtin command -v bundle >/dev/null ||
+#   builtin command -v bundle | GREP_OPTIONS= \grep $rvm_path/bin/bundle >/dev/null
+# }
+# then
+#   printf "%b" "The rubygem 'bundler' is not installed. Installing it now.\n"
+#   gem install bundler
+# fi
+# if [[ -s Gemfile ]] && builtin command -v bundle >/dev/null
+# then
+#   bundle install | GREP_OPTIONS= \grep -vE '^Using|Your bundle is complete'
+# fi

data/Gemfile

@@ -1,4 +1,4 @@
 source 'https://rubygems.org'
 
-# Specify your gem's dependencies in kicker.gemspec
+# Specify your gem's dependencies in stack-kicker.gemspec
 gemspec

data/LICENSE.txt

@@ -1,22 +1,202 @@
-Copyright (c) 2013 Simon McCartney
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -1,25 +1,142 @@
-# Kicker
+# stack-kicker
 
-TODO: Write a gem description
+stack-kicker is a simple 'application stack' deployment tool, it's purpose in life 
+is to spin up a set of instances in a repeatable, controlled fashion, and optionally 
+run post-install scripts after each instance has been started.
 
-## Installation
+stack-kicker has hooks to allow default & custom cloud-init templates to be built & passed to
+your compute provider (we currently use ruby-openstack, so are limited to OpenStack providers, 
+however, a sister project, aws-kicker, uses fog.io, the interaction with the compute provider is
+minimal, so it's on the roadmap to merge aws-kicker & stack-kicker, and use either an internal
+abstraction layer or just fog.io for all compute provisioning requests)
+
+## Stackfile
+Normally, stack configurations are stored in a Stackfile, which is a ruby hash of configuration options.
+Typically, the Stackfile contains the following sets of information
+
+1. Credentials for your compute provider
+2. Defaults for your Stack (compute flavor, image id, region/az, ssh-keys, instance name template)
+1. roles
+
+## Concepts
+stack-kicker sequentially iterates over defined roles, creating the required number of nodes (nodes are the compute instances).  If an instance already exists with the proposed name, it's skipped, assuming that this node has already been built.
+
+Hostnames are generated from a customizable template, which is effectively:
+
+	config[:name_template] = '%s-%s-%s%04d'
+	config['global_service_name'] = 'myapp'
+	site = <derived from region/az, via config[:site_template]>
+	hostname = sprintf(config[:name_template], config['global_service_name'], site, role, position)
+
+So hostnames will be myapp-az1-chef0001, myapp-az1-web0001, myapp-az1-web0002 etc. 
 
-Add this line to your application's Gemfile:
+post-install scripts are executed from the same host as stack-kicker is being used, using the same credentials as the current user.  They are can be used to retrieve information from a freshly built node (like certificates from a chef server), so block progress until the chef-client run has completed (we use this to block percona/galera & rabbitmq cluster builds so that the first node is up & running correctly before we try and add another node to the cluster)
 
-    gem 'kicker'
+## Example workflows/models
+stack-kicker was built with the following workflows in mind:
 
-And then execute:
+### private chef-server
+This was the original requirement, a multi-role application stack build that started
+with building a chef-server, uploading roles, environments, cookbooks & databags to it,
+and then building the rest of the application-stack instances, using the freshly built chef-server
+to drop the application on to the instances.  In this setup we used vanilla images (Ubuntu 12.04 LTS, 
+but you could use any image, either vanilla or pre-populated with your software).
 
-    $ bundle
+Here's an example Stackfile for this:
+	
+	module StackConfig
+		Stacks = {
+	    'web-w-chef-server' => {
+	      # (we can access environment variable via ENV['foo'] instead of hard coding u/p here)
+	      'REGION'      => ENV['OS_REGION_NAME'],
+	      'USERNAME'    => ENV['OS_USERNAME'],
+	      'PASSWORD'    => ENV['OS_PASSWORD'],
+	      'AUTH_URL'    => ENV['OS_AUTH_URL'],
+	      'TENANT_NAME' => ENV['OS_TENANT_NAME'],
+	
+	       # generic instance info
+	       'flavor_id'  => 103,
+	       'image_id'   => 75845,
+	       :key_pair => 'ssh-keypair-name',
+	       :key_public => '/path/to/id_rsa.pub',
+	       :global_service_name => 'perconaconf',
+	       
+	       # role details
+	       :roles => {
+	         # override the default cloud-init script & default bootstrap (which is a chef-client bootstrap)
+	         :chef => {
+	            # we are the chef server, so skip the chef-client steps
+	           :chef_server => true,	:skip_chef_prereg => true,
+	           # override the default cloud-config with a chef-server template
+	           :cloud_config_yaml => 'chef-cloud-config.yaml',
+	           # skip the default chef-client bootstrap
+	           :bootstrap => '',                                 
+	           # wait for the chef server to come up & download pem files & generate client account
+	           :post_install_script => 'bootstrap/chef-post-install.sh',
+	            # our post install script dumps out .pem files in the CWD   
+	           :post_install_cwd => '.chef',                    
+	           # The post-install script needs to know the public IP of the just built instance so that this station can access it
+	           :post_install_args => '%PUBLIC_IP%'               
+	         },
+	         # much simpler role, just build 3 of these, chef-client will do the rest on boot
+	         :web => {  :count => 3 }
+	       }
+	    }
+	    }
+	end
+           
 
-Or install it yourself as:
+### simple roles
+There is no requirement that stack-kicker do anything other than spin up your instances, your requirements 
+may be such that you just need a number of instances started with certain images, region & flavor requirements.
 
-    $ gem install kicker
+### masterless puppet
+aws-kicker (a sister project) had an original requirement of starting a simple 2-tier web application in multiple 
+locations/environments (prod, stage, dev etc), to do this we configured the instances by bootrapping puppet, 
+git clonig /etc/puppet and running "puppet apply", a simple pattern used in many places, this was all achievd with a
+carefully crafted cloud-init template (incidentally, this also allowed for simple prototyping using vagrant to
+provide local instances using the exact same '/etc/puppet' git repo.
+
+### Other workflows
+These are only the workflows I've used, there is no reason a puppet master couldn't be built & used, or 
+hosted/external puppet & chef servers. (pull requests accepted etc, including salt, ansible, cfengine etc..)
+
+## Installation
+
+    $ gem install stack-kicker
+    
+## Requirements
+In addition to the the ruby dependencies which gem will install for you, access to python-novaclient is currently required to attach floating-ips to instances.
 
 ## Usage
 
-TODO: Write usage instructions here
+	Usage: stack-kicker [options] task
+	
+	Options:
+	    -h, --help                       Show command line help
+	        --stackfile Stackfile        Specify an alternative Stackfile
+	                                     (default: Stackfile)
+	        --stack mystack              Specify the stack in Stackfile that you want to work with
+	        --ssh-user USER              User to be used for SSH access
+	        --version                    Show help/version info
+	        --log-level LEVEL            Set the logging level
+	                                     (debug|info|warn|error|fatal)
+	                                     (Default: info)
+	
+	Arguments:
+
+    task
+        task to be performed validate|configure-knife|show-stacks|show-stack|show-running|build|replace|delete|secgroup-sync|ssh
+
+## TODO
 
+1. Clean up provider logic
+2. Remove dependency on python-novaclient for floating-ip attach
+3. Remove dependency on a full chef gem install
+4. Better docs & examples
+5. Support for AWS EC2 (from aws-kicker)
+5. Support for DNS Updates on instance creation (from aws-kicker)
+6. 
 ## Contributing
 
 1. Fork it

data/README.rdoc

@@ -1,9 +1,13 @@
-= kicker - DESCRIBE YOUR GEM
+= stack-kicker - DESCRIBE YOUR GEM
 
 Author::  YOUR NAME (YOUR EMAIL)
 Copyright:: Copyright (c) 2013 YOUR NAME
 
 
+License:: apache, see LICENSE.txt
+
+
+
 DESCRIBE YOUR GEM HERE
 
 == Links

data/bin/stack-kicker

@@ -0,0 +1,84 @@
+#!/usr/bin/env ruby
+# Copyright 2012 Hewlett-Packard Development Company, L.P.
+# All Rights Reserved.
+#
+# Author: Simon McCartney <simon.mccartney@hp.com>
+#
+#    Licensed under the Apache License, Version 2.0 (the "License"); you may
+#    not use this file except in compliance with the License. You may obtain
+#    a copy of the License at
+#
+#         http://www.apache.org/licenses/LICENSE-2.0
+#
+#    Unless required by applicable law or agreed to in writing, software
+#    distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+#    WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+#    License for the specific language governing permissions and limitations
+#    under the License.
+#
+
+require 'bundler'
+require 'optparse'
+require 'methadone'
+require 'stack-kicker'
+require 'stack'
+
+class App
+  include Methadone::Main
+  include Methadone::CLILogging
+
+  main do |task|
+    debug { "#{options}" }
+    # pass the logger.level into the Stack module
+    Stack.log_level(logger.level)
+
+    if (task != 'show-stacks')
+      config = Stack.select_stack(options[:stackfile], options['stack'])
+    end
+
+    case task
+    when 'validate'
+      Stack.validate(config)
+    when 'configure-knife'
+      Stack.generate_knife_rb(config)
+    when 'show-stacks'
+      Stack.show_stacks(options[:stackfile])
+    when 'show-stack'
+      Stack.show_stack(config)
+    when 'show-running'
+      Stack.show_running(config)
+    when 'build'
+      Stack.deploy_all(config)
+    when 'delete'
+      Stack.delete_all(config)
+    else
+      error "Sorry, #{task} hasn't been implemented yet"
+    end
+  end
+
+  # supplemental methods here
+
+  # Declare command-line interface here
+
+  description "create application stacks in the cloud from fundamental building blocks"
+  #
+  # Accept flags via:
+  # on("--flag VAL","Some flag")
+  # options[flag] will contain VAL
+  #
+  # Specify switches via:
+  # on("--[no-]switch","Some switch")
+  #
+
+  options[:stackfile] = 'Stackfile'
+  on("--stackfile Stackfile", "Specify an alternative Stackfile")
+  on("--stack mystack", "Specify the stack in Stackfile that you want to work with")
+  on("--ssh-user USER", "User to be used for SSH access")
+
+  arg :task, "task to be performed validate|configure-knife|show-stacks|show-stack|show-running|build|replace|delete|secgroup-sync|ssh"
+  version Stack::Kicker::VERSION
+
+  use_log_level_option
+
+  go!
+end

data/doc/examples/Stackfile

@@ -0,0 +1,41 @@
+module StackConfig
+    Stacks = {
+    'web-w-chef-server' => {
+      # (we can access environment variable via ENV['foo'] instead of hard coding u/p here)
+      'REGION'      => ENV['OS_REGION_NAME'],
+      'USERNAME'    => ENV['OS_USERNAME'],
+      'PASSWORD'    => ENV['OS_PASSWORD'],
+      'AUTH_URL'    => ENV['OS_AUTH_URL'],
+      'TENANT_NAME' => ENV['OS_TENANT_NAME'],
+
+       # generic instance info
+       'flavor_id'  => 103,
+       'image_id'   => 75845,
+       :key_pair => 'ssh-keypair-name',
+       :key_public => '/path/to/id_rsa.pub',
+       :global_service_name => 'perconaconf',
+       
+       # role details
+       :roles => {
+         # override the default cloud-init script & default bootstrap (which is a chef-client bootstrap)
+         :chef => {
+            # we are the chef server, so skip the chef-client steps
+           :chef_server => true,        :skip_chef_prereg => true,
+           # override the default cloud-config with a chef-server template
+           :cloud_config_yaml => 'chef-cloud-config.yaml',
+           # skip the default chef-client bootstrap
+           :bootstrap => '',                                 
+           # wait for the chef server to come up & download pem files & generate client account
+           :post_install_script => 'bootstrap/chef-post-install.sh',
+            # our post install script dumps out .pem files in the CWD   
+           :post_install_cwd => '.chef',                    
+           # The post-install script needs to know the public IP of the just built instance so that this station can access it
+           :post_install_args => '%PUBLIC_IP%'               
+         },
+         # much simpler role, just build 3 of these, chef-client will do the rest on boot
+         :web => {  :count => 3 }
+       }
+    }
+    }
+end
+

data/features/stack-kicker.feature

@@ -0,0 +1,27 @@
+Feature: Build application stacks in the cloud using Chef
+
+    Scenario: App just runs
+        When I get help for "stack-kicker"
+        Then the exit status should be 0
+        And the banner should be present
+        And the banner should document that this app takes options
+        And the following options should be documented:
+          |--version|
+        And the banner should document that this app's arguments are: 
+          |task|which is required|
+
+    Scenario: show-stacks shows the stacks defined in the current Stackfile
+        Given a 2 stack Stackfile
+        When I successfully run "stack-kicker show-stacks"
+        Then both stacks are listed by show-stack
+
+    Scenario: show-stack shows the stacks defined in the current Stackfile
+        Given a 2 stack Stackfile
+        When I successfully run "stack-kicker show-stack"
+        Then the nodes in both stacks are listed by show-stack
+
+    Scenario: show-stack shows the stack defined in the current Stackfile
+        Given a single stack Stackfile
+        When I successfully run "stack-kicker show-stack"
+        Then the nodes in both stacks are listed by show-stack
+

data/lib/stack-kicker/version.rb

@@ -0,0 +1,5 @@
+module Stack
+  module Kicker
+    VERSION = "0.0.2"
+  end
+end

data/lib/stack-kicker.rb

@@ -0,0 +1,7 @@
+require "stack-kicker/version"
+
+module Stack
+  module Kicker
+    # Your code goes here...
+  end
+end