RubyGems - cucumber-chef - Versions diffs - 1.0.3 → 2.0.0.pre - Mend

cucumber-chef 1.0.3 → 2.0.0.pre

Files changed (108) hide show

data/.gitignore +8 -35
data/.rspec +1 -0
data/.rvmrc.template +2 -0
data/.travis.yml +22 -0
data/Gemfile +2 -15
data/LICENSE +202 -201
data/NOTICE +9 -0
data/README.md +696 -92
data/Rakefile +39 -25
data/TODO.md +28 -0
data/bin/cc-knife +32 -0
data/bin/cucumber-chef +409 -79
data/chef_repo/cookbooks/cucumber-chef/LICENSE +202 -0
data/chef_repo/cookbooks/cucumber-chef/README.md +69 -0
data/chef_repo/cookbooks/cucumber-chef/attributes/default.rb +27 -0
data/chef_repo/cookbooks/cucumber-chef/metadata.rb +13 -0
data/chef_repo/cookbooks/cucumber-chef/recipes/default.rb +23 -0
data/chef_repo/cookbooks/cucumber-chef/recipes/lxc.rb +315 -0
data/chef_repo/cookbooks/cucumber-chef/recipes/test_lab.rb +146 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/db-168-192.erb +15 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/db-test-lab.erb +15 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/dhcpd-conf.erb +44 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/gemrc.erb +10 -0
data/{cookbooks/cucumber-chef/files/default/cucumber-net → chef_repo/cookbooks/cucumber-chef/templates/default/lxc-initializer-config.erb} +1 -1
data/chef_repo/cookbooks/cucumber-chef/templates/default/lxc-install-chef.erb +3 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/motd.erb +10 -0
data/chef_repo/cookbooks/cucumber-chef/templates/default/named-conf-local.erb +25 -0
data/{cookbooks/cucumber-chef/files/default/permissive-ssh-config → chef_repo/cookbooks/cucumber-chef/templates/default/ssh-config.erb} +3 -1
data/chef_repo/roles/test_lab.rb +24 -0
data/cucumber-chef.gemspec +50 -123
data/examples/README.md +7 -0
data/examples/users_add.feature +51 -0
data/examples/users_auto_remove.feature +50 -0
data/features/support/env.rb +3 -2
data/lib/cucumber/chef/bootstrap.rb +94 -0
data/lib/cucumber/chef/command.rb +78 -0
data/lib/cucumber/chef/config.rb +143 -93
data/lib/cucumber/chef/helpers/chef_client.rb +87 -0
data/lib/cucumber/chef/helpers/chef_server.rb +90 -0
data/lib/cucumber/chef/helpers/command.rb +57 -0
data/lib/cucumber/chef/helpers/container.rb +154 -0
data/lib/cucumber/chef/helpers/minitest.rb +35 -0
data/lib/cucumber/chef/helpers/server.rb +81 -0
data/lib/cucumber/chef/helpers/test_lab.rb +46 -0
data/lib/cucumber/chef/helpers/utility.rb +73 -0
data/lib/cucumber/chef/helpers.rb +56 -0
data/lib/cucumber/chef/logger.rb +90 -0
data/lib/cucumber/chef/provisioner.rb +275 -69
data/lib/cucumber/chef/ssh.rb +190 -0
data/lib/cucumber/chef/steps/chef_steps.rb +32 -0
data/lib/cucumber/chef/steps/minitest_steps.rb +29 -0
data/lib/cucumber/chef/steps/provision_steps.rb +60 -0
data/lib/cucumber/chef/steps/ssh_steps.rb +95 -0
data/lib/cucumber/chef/steps.rb +27 -0
data/lib/cucumber/chef/tcp_socket.rb +83 -0
data/lib/cucumber/chef/template.rb +57 -0
data/lib/cucumber/chef/templates/bootstrap/ubuntu-precise-test-lab.erb +99 -0
data/lib/cucumber/chef/templates/cucumber/env.rb +56 -0
data/lib/cucumber/chef/templates/cucumber/example_feature.erb +49 -0
data/lib/cucumber/chef/templates/cucumber/example_steps.erb +11 -0
data/lib/cucumber/chef/templates/cucumber/readme-data_bags.erb +1 -0
data/lib/cucumber/chef/templates/cucumber/readme-keys.erb +1 -0
data/lib/cucumber/chef/templates/cucumber/readme-roles.erb +1 -0
data/lib/cucumber/chef/templates/cucumber/readme.erb +18 -0
data/lib/cucumber/chef/templates/cucumber-chef/config-rb.erb +33 -0
data/lib/cucumber/chef/templates/cucumber-chef/cucumber-yml.erb +2 -0
data/lib/cucumber/chef/templates/cucumber-chef/knife-rb.erb +18 -0
data/lib/cucumber/chef/test_lab.rb +308 -52
data/lib/cucumber/chef/test_runner.rb +86 -15
data/lib/cucumber/chef/utility.rb +128 -0
data/lib/cucumber/chef/version.rb +30 -1
data/lib/cucumber/chef.rb +53 -20
data/lib/cucumber-chef.rb +24 -1
data/spec/cucumber/chef/config_spec.rb +144 -78
data/spec/cucumber/chef/provisioner_spec.rb +60 -16
data/spec/cucumber/chef/test_lab_spec.rb +62 -19
data/spec/spec_helper.rb +30 -26
data/todo.org +17 -0
metadata +267 -163
data/.document +0 -5
data/VERSION +0 -1
data/cookbooks/cucumber-chef/README.rdoc +0 -8
data/cookbooks/cucumber-chef/files/default/add-git-identity +0 -2
data/cookbooks/cucumber-chef/files/default/controller-first-boot +0 -1
data/cookbooks/cucumber-chef/files/default/cucumber-private-key +0 -27
data/cookbooks/cucumber-chef/files/default/cucumber-run_list +0 -1
data/cookbooks/cucumber-chef/files/default/git-private-key +0 -27
data/cookbooks/cucumber-chef/files/default/install-chef +0 -1
data/cookbooks/cucumber-chef/files/default/lxc-controller-network-config +0 -5
data/cookbooks/cucumber-chef/files/default/lxc-lucid-chef +0 -378
data/cookbooks/cucumber-chef/metadata.rb +0 -6
data/cookbooks/cucumber-chef/recipes/controller.rb +0 -51
data/cookbooks/cucumber-chef/recipes/lxc.rb +0 -35
data/cookbooks/cucumber-chef/recipes/test_lab.rb +0 -23
data/cookbooks/cucumber-chef/recipes/testrunner.rb +0 -46
data/cookbooks/cucumber-chef/roles/controller.rb +0 -7
data/cookbooks/cucumber-chef/roles/test_lab_test.rb +0 -9
data/cookbooks/cucumber-chef/templates/default/controller-client.erb +0 -5
data/cookbooks/cucumber-chef/templates/default/lxc-lucid-chef +0 -385
data/lib/cucumber/chef/handy.rb +0 -90
data/lib/cucumber/chef/templates/controller.erb +0 -35
data/lib/cucumber/chef/templates/env.rb +0 -16
data/lib/cucumber/chef/templates/example_feature.erb +0 -11
data/lib/cucumber/chef/templates/example_step.erb +0 -19
data/lib/cucumber/chef/templates/readme.erb +0 -14
data/lib/cucumber/chef/templates/ubuntu10.04-gems.erb +0 -43
data/lib/cucumber/ec2_server_create.rb +0 -99
data/website/website.html +0 -385

data/lib/cucumber/ec2_server_create.rb DELETED Viewed

@@ -1,99 +0,0 @@
-require 'fog'
-require 'socket'
-require 'chef/knife'
-require 'chef/knife/bootstrap'
-require 'chef/json_compat'
-class Chef
-  class Knife
-    class Ec2ServerCreate < Knife
-      attr_accessor :initial_sleep_delay
-      def tcp_test_ssh(hostname)
-        tcp_socket = TCPSocket.new(hostname, 22)
-        readable = IO.select([tcp_socket], nil, nil, 5)
-        if readable
-          Chef::Log.debug("sshd accepting connections on #{hostname}, banner is #{tcp_socket.gets}")
-          yield
-          true
-        else
-          false
-        end
-      rescue Errno::ETIMEDOUT
-        false
-      rescue Errno::ECONNREFUSED
-        sleep 2
-        false
-      ensure
-        tcp_socket && tcp_socket.close
-      end
-      def run
-        require 'fog'
-        require 'highline'
-        require 'net/ssh/multi'
-        require 'readline'
-        $stdout.sync = true
-        connection = Fog::Compute.new(
-                                      :provider => 'AWS',
-                                      :aws_access_key_id => Chef::Config[:knife][:aws_access_key_id],
-                                      :aws_secret_access_key => Chef::Config[:knife][:aws_secret_access_key],
-                                      :region => #REGION
-                                      )
-        # WHAT IS THIS FOR?
-        ami = connection.images.get(locate_config_value(:image))
-        server_def = {
-        :image_id => locate_config_value(:image),
-        :groups => config[:security_groups],
-        :flavor_id => locate_config_value(:flavor),
-        :key_name => Chef::Config[:knife][:aws_ssh_key_id],
-        :availability_zone => Chef::Config[:knife][:availability_zone]
-      }
-      server = connection.servers.create(server_def)
-      puts "Instance ID: #{server.id}"
-      print "\n#{h.color("Waiting for server", :magenta)}"
-      # wait for it to be ready to do stuff
-      server.wait_for { print "."; ready? }
-      puts("\n")
-      puts "Public IP Address #{server.public_ip_address}"
-      print "\n#{h.color("Waiting for sshd", :magenta)}"
-      print(".") until tcp_test_ssh(server.dns_name) { sleep @initial_sleep_delay ||= 10; puts("done") }
-      bootstrap_for_node(server).run
-    end
-    def bootstrap_for_node(server)
-      bootstrap = Chef::Knife::Bootstrap.new
-      bootstrap.name_args = [server.dns_name]
-      bootstrap.config[:run_list] = config[:run_list]
-      bootstrap.config[:ssh_user] = config[:ssh_user]
-      bootstrap.config[:identity_file] = config[:identity_file]
-      bootstrap.config[:chef_node_name] = config[:chef_node_name] || server.id
-      bootstrap.config[:prerelease] = config[:prerelease]
-      bootstrap.config[:distro] = locate_config_value(:distro)
-      bootstrap.config[:use_sudo] = true
-      bootstrap.config[:template_file] = locate_config_value(:template_file)
-      bootstrap.config[:environment] = config[:environment]
-      bootstrap
-    end
-    def locate_config_value(key)
-      key = key.to_sym
-      Chef::Config[:knife][key] || config[key]
-    end
-  end
-end
-end

data/website/website.html DELETED Viewed

@@ -1,385 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
-"http://www.w3.org/TR/html4/strict.dtd">
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Cucumber-chef</title>
-<!-- Typekit service section -->
-<script type="text/javascript"
-src="http://use.typekit.com/jmb0kkz.js"></script>
-<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
-<!-- End of typekit service section -->
-<!-- Framework CSS --> <link rel="stylesheet" href="style/style.css"
-type="text/css" media="screen, projection"> </head>
-<body> <div class="container">
-<div id="nav">
-  <ul>
-    <li class="selected">Main</li>
-    <li>Docs</li>
-  </ul>
-</div>
-<div id="header">
-  <img src="images/cucumber-chef-logo.png" width="380" height="46"
-  alt="Cucumber Chef Logo"/>
-  <h3>A library of tools to enable test driven development</h3>
-</div>
-<div class="page">
-<div id="panel">
-  <a href="https://github.com/Atalanta/cucumber-chef"><img
-  src="images/large-button.png" width="252" height="52" class="imgpad"
-  alt="Git Hub" /></a>
-  <a href="http://oreilly.com/catalog/0636920020042"><img
-  src="images/book-cover.png" width="252" height="330" alt="Book
-  Cover"/></a>
-  <p class="book-description">Test-Driven Infrastructure with
-  Chef<br/>by Stephen Nelson-Smith<br/>Published by O’Reilly</p>
-  <a href="http://oreilly.com/catalog/0636920020042"><img
-  src="images/buy-button.png" width="62" height="27" alt="Buy
-  Button"/></a>
-</div>
-<h2>Overview</h2>
-<p><strong>Cucumber-chef</strong>is a library of tools to enable the
-emerging discipline of infrastructure as code to practice test driven
-development.  It provides a testing platform within which cucumber
-tests can be run which provision lightweight virtual machines,
-configure them by applying the appriporaite Chef roles to them, and
-then run acceptance and integration tests against the environment.</p>
-<p>It begins with a very simple premise. with a very simple
-premise.  If we are framing our infratructure as code - if we're
-writing cookbooks, recipes and other pieces of automation in a high
-level programming language, such as Ruby, then it makes sense to
-follow the current wisdom across the software development world to
-maximise the quality, maintainability and reusability of our code,
-providing maximum chance that we'll deliver value with it.  One
-area which has been shown to have a very positive effect is the
-practive of 'test-driven' development.  In this paradigm, the
-developer begins by writing a test that captures the intended
-behaviour of the code  they are going to write.  This test will
-start out by failing.  The developer then writes code to make the
-test pass, and iterates thereafter.</p>
-<strong>Cucumber-Chef</strong> provides a framework to make it easier
-to do test-driven development for infrastructure. It does this by
-providing a test infrastructure, in the cloud, which provides a very
-fast, lightweight and cheap way to fire up virtual machines for
-testing.  We call this the "test lab".</p>
-<p>As you might have guessed from the name, we're going to write high
-level acceptance tests using Cucumber.  Cucumber-Chef provides step
-definitions and helper methods to make it easy to provision and manage
-machines with Chef, and then build end-to-end tests.</p>
-<ul> <li><strong>Test Lab:</strong> An environment made up (at
-  present) of an EC2 instance, configured to be an LXC host. This
-  machine does nothing other than provide space in which Linux
-  containers can be created and destroyed.</li>
-  <li><strong>Controller:</strong> One special Linux container which
-  acts as the central point from which tests are run. This machine is
-  where the tests run, and has connectivity and credentials to connect
-  to the machines that are created as part of a test run.</li>
-  <li><strong>Container:</strong> A container is a lightweight virtual
-  machine - it is entirely self-contained, with its own process tree,
-  resource constraints, filesystem and network stack. It shares a
-  kernel with the Test Lab host server.</li> </ul>
-  <h3>Getting Started</h3>
-  <p>Getting started with <strong>Cucumber-Chef</strong> is a simple,
-  three step process:</p>
-  <ul>
-    <li>1) Install Cucumber-Chef</li>
-    <li>2) Integrate with Hosted Chef and Amazon EC2</li>
-    <li>3) Run cucumber-chef setup</li>
-  </ul>
-  <h3>Installing Cucumber-Chef</h3>
-  <p>Installing Cucumber-Chef is simple.  It's distributed as a
-  RubyGem, so you can simply run:</p>
-<div class="inset-box">
-  <pre><code>$ gem install cucumber-chef
-    </code></pre>
-</div>
-<p>Once installed, you can run cucumber-chef on the command line to
-get an overview of the tasks it can carry out.</p>
-<div class="inset-box">
-  <pre><code>$ cucumber-chef
-Tasks:
-  cucumber-chef connect                 # Connect to a container in your test lab
-  cucumber-chef destroy                 # Destroy running test labs
-  cucumber-chef displayconfig           # Display the current config from knife.rb
-  cucumber-chef help [TASK]             # Describe available tasks or one specific task
-  cucumber-chef info                    # Display information about the current test lab
-  cucumber-chef project &lt;project name&gt;  # Create a project template for testing an infrastructure
-  cucumber-chef setup                   # Set up a cucumber-chef test lab in Amazon EC2
-  cucumber-chef test                    # Run a cucumber-chef test suite from a workstation.
-  cucumber-chef upload &lt;project name&gt;   # Upload a cucumber-chef test
-</code></pre>
-</div>
-<h3>Integrate with Hosted Chef and Amazon EC2</h3>
-<p>In it's current incarnation, Cucumber-Chef makes two important
-assumptions.  Firstly, it assumes you're using Opscode Hosted Chef
-rather than your own Chef server.  Secondly, it assume that you are
-comfortable with using Amazon's EC2 service for providing the 'bare
-metal' on which we set up the test lab.  </p>
-<p><strong>Cucumber-chef</strong> is tightly integrated with Chef - it
-uses your knife.rb for credentials, and any cucumber-chef-specific
-configuration goes in knife.rb under the cucumber-chef namespace.</p>
-<p>On installation, the first thing you should do is run:</p>
-<div class="inset-box">
-  <pre>
-    $ cucumber-chef displayconfig
-   </pre>
-</div>
-<p>This will look for your knife.rb, and extract the relevant
-sections, check them, and display them on the screen. If any entries
-are missing, it will alert you.</p>
-<p>The recommended best practice for Chef is to keep your knife.rb
-inside your organisation's Chef repository, inside the .chef
-directory, and use environment variables to specify username,
-organisation name and cloud provider credentials.  Cucumber-chef
-supports and encourages this approach.  It will search for a
-directory called .chef in your current directory, and then carry on
-going up the directory tree until it finds one.  In practice this
-means that if you stay within the chef-repo directory for the
-organisation on which you're working, cucumber-chef will use the
-knife.rb; if your elsewhere in the filesystem rooted in your home
-directory, and have .chef in your home directory, cucumber-chef
-will use that.  Otherwise you'll need to either change into a
-directory where a .chef can be found, or copy, creatre or link
-accordingly.  In most cases we anticipate that you'll be inside the
-chef-repo of your organisation, and the documentation is written
-from this perspective.</p>
-<p>If you haven't already, refactor your knife.rb to look like this:</p>
-<div class="inset-box">
-  <pre><code>current_dir = File.dirname(__FILE__)
-user = ENV['OPSCODE_USER'] || ENV['USER']
-log_level :info
-log_location STDOUT
-node_name user
-client_key "#{ENV['HOME']}/.chef/#{user}.pem"
-validation_client_name "#{ENV['ORGNAME']}-validator"
-validation_key "#{ENV['HOME']}/.chef/#{ENV['ORGNAME']}-validator.pem"
-chef_server_url "https://api.opscode.com/organizations/#{ENV['ORGNAME']}"
-cache_type 'BasicFile'
-cache_options( :path =&gt; "#{ENV['HOME']}/.chef/checksums" )
-cookbook_path ["#{current_dir}/../cookbooks"]
-</code></pre>
-</div>
-<p>Now set your Hosted Chef username and organization name using
-environment variables:</p>
-<div class="inset-box">
-  <pre><code>$ export OPSCODE_USER=platform_user_name
-$ export ORGNAME=platform_organisation
-</code></pre>
-</div>
-<p>Now put your validator and client keys in $HOME/.chef.  Verify that
-everything still works:</p>
-<div class="inset-box">
-  <pre><code>$ knife client list
-</code></pre>
-</div>
-<p>If you get results back, we're in business.</p>
-<p>Now add the EC2 configuration:</p>
-<div class="inset-box">
-  <pre><code>knife[:aws_access_key_id] = ENV['AWS_ACCESS_KEY_ID']
-knife[:aws_secret_access_key] = ENV['AWS_SECRET_ACCESS_KEY']
-knife[:aws_ssh_key_id] = ENV['AWS_SSH_KEY_ID']
-knife[:identity_file] = "/path/to/aws_ssh_key.pem"
-knife[:availability_zone] = "eu-west-1a"
-knife[:region] = "eu-west-1"
-knife[:aws_image_id] = "ami-339ca947"
-</code></pre>
-</div>
-<p>Note that right now Cucumber-Chef only supports Ubuntu-based  test
-labs.</p>
-<p>And set your environment variables:</p>
-<div class="inset-box">
-  <pre><code>$ export AWS_ACCESS_KEY_ID=SEKRITKEY
-$ export AWS_SECRET_ACCESS_KEY=REELYSEKRITKEY
-$ export AWS_SSH_KEY_ID
-</code></pre>
-</div>
-<p>And then ensure your AWS ssh key is in place.</p>
-<p>Now check your config again, with cucumber-chef display config.  If
-you get no complaints, you're ready to set up a test lab.</p>
-<h3>Run cucumber-chef setup</h3>
-<div class="inset-box">
-  <pre><code>$ cucumber-chef setup
-</code></pre>
-</div>
-<p>This command will set up a complete test lab environment, As long
-as you've provided valid AWS and Opscode credentials, it will do this
-automatically.  The process takes about 15 minutes, after which you'll
-have a fully funtioning platform available for you to use.  Let's just
-quickly review what that means.  You will have an EC2 machine, fully
-managed by Chef, and providing the following:</p>
-<ul>
-  <li>The ability to provision LXC containers</li>
-  <li>The ability to run tests against LXC containers</li>
-  <li>A dedicated container for certain kinds of testing scenarios</li>
-</ul>
-<p>The next stage is to set up a project.  A project is simply a
-directory structure for containing your cucumber features and steps,
-already set up with an appropriate environment to make use of the
-step definitions provided with cucumber-chef.  We think it makes
-most sense to have this in your organisation's chef repo.
-Cucumber-chef provides a task which will create a the directory for
-you, and populate it with a README and an example feature and
-step.</p>
-<div class="inset-box">
-  <pre><code>$ cd /path/to/chef-repo
-$ cucumber-chef project example
-</code></pre>
-</div>
-<p>This will create a directory, cucumber-chef, and a subdirectory, example.</p>
-<div class="inset-box">
-  <pre><code>└── example
-    ├── README
-    └── features
-        ├── example.feature
-        ├── step_definitions
-        │   └── example_step.rb
-        └── support
-            └── env.rb
-</code></pre>
-</div>
-<h2>Writing tests</h2>
-<p>Once you've got your test lab set up, and you've generated a
-project, it's time to crack on with writing a test.  The basic idea is
-this:</p>
-<p>
-<ul>
-  <li>1) An infrastructure requirement is established</li>
-  <li>2) Write a cucumber feature that expresses the required
-  behaviour of the infrastructure requirement</li>
-  <li>3) Write steps that will build this infrastructure environment
-  on the test lab, using the step definitions provided - these include
-  the ability to create a container, apply roles to it, and destroy it
-  again.</li>
-  <li>4) Write cookbooks and recipes and supporting code to make
-  the test pass</li>
-</ul></p>
-<h2>Running tests</h2>
-<p>You can write the tests and Chef code wherever you like.  We're
-assuming you prefer working on your local machine, and checking into
-version control.  But we don't really care.  When it's time to run
-tests, cucumber-chef provides a task which handles this:</p>
-<div class="inset-box">
-  <pre><code>$ cucumber-chef test myproject
-</code></pre>
-</div>
-<p>At the moment cucumber-chef doesn't pass though clever filtering
-and tagging options that cucumber supports - you run all the tests.
-We're going to improve that soon, again, patches and pull requests
-very welcome.</p>
-<p>Running the test task will upload your current project to the test
-lab, and run the tests, reporting the results back to the screen.
-Cucumber-chef also provides an upload task, so you can push the
-current project to the test lab, and then connect to test lab yourself
-to run tests in a more granular way.  To do this, you need to know the
-IP of the test lab.  You can find this out by running:</p>
-<div class="inset-box">
-  <pre><code>$ cucumber-chef info
-</code></pre>
-</div>
-<p>At present, Cucumber-Chef only allows one test lab per AWS account
-and Opscode Hosted Chef account.</p>
-</div>
-</div>
-</body>
-</html>