chef-skel 0.1.0 → 0.1.1

data/CHANGELOG.md

@@ -0,0 +1,12 @@
+v0.1.1 (Jun 26 2013)
+--------------------
+
+* Generate knife.rb as part of `rake test:prepare` so it doesn't have to be part
+  of the cookbook.
+* Add files README.md, TESTING.md, CHANGELOG.md, and LICENSE.
+* Remove Gemfile.lock.
+
+v0.1.0 (Jun 24 2013)
+--------------------
+
+* First tagged version.

data/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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

@@ -0,0 +1,61 @@
+chef-skel
+=========
+
+chef-skel provides a skeleton for a testable Chef cookbook.
+
+The goal of chef-skel is to extract all testing facilities of the [skeleton
+cookbook] into a gem. See file `TESTING.md` to learn more.
+
+
+Installation
+------------
+
+You can install chef-skel via RubyGems:
+
+    $ gem install chef-skel
+
+Alternatively, you can install the gem from source:
+
+    $ git clone git://github.com/mlafeldt/chef-skel.git
+    $ cd chef-skel/
+    $ bundle install
+    $ bundle exec rake install
+
+
+Usage
+-----
+
+For now, take a look at the [skeleton cookbook] to learn how chef-skel is used.
+
+
+License and Author
+------------------
+
+Author:: Mathias Lafeldt (<mathias.lafeldt@gmail.com>)
+
+Copyright:: 2012-2013, Mathias Lafeldt
+
+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.
+
+
+Contributing
+------------
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+
+[skeleton cookbook]: https://github.com/mlafeldt/skeleton-cookbook

data/TESTING.md

@@ -0,0 +1,150 @@
+Testing
+-------
+
+This cookbook comes with everything you need to develop infrastructure code with
+Chef and feel confident about it. The provided testing facilities allow you to
+iterate quickly on cookbook changes.
+
+After installing Vagrant and the required Ruby gems, most of the testing can be
+done through convenient Rake tasks.
+
+### Bundler
+
+Apart from Vagrant, which is described later on, all tools you need for cookbook
+development and testing are installed as Ruby gems using [Bundler]. This gives
+you a lot of control over the software stack ensuring that the testing
+environment matches your production environment.
+
+First, make sure you have Bundler (which is itself a gem):
+
+    $ gem install bundler
+
+Then let Bundler install the required gems (as defined in `Gemfile`):
+
+    $ bundle install
+
+Now you can use `bundle exec` to execute a command from the gemset, for example:
+
+    $ bundle exec rake
+
+(You should keep `Gemfile.lock` checked in.)
+
+### Rake
+
+The cookbook provides a couple of helpful [Rake] tasks (specified in
+`Rakefile`):
+
+    $ rake -T
+    rake clean                      # Remove any temporary products.
+    rake clobber                    # Remove any generated file.
+    rake env                        # Display information about the environment
+    rake test:all                   # Run test:syntax, test:lint, test:unit, and test:integration
+    rake test:integration           # Run serverspec integration tests with Vagrant
+    rake test:integration_teardown  # Tear down VM used for integration tests
+    rake test:lint                  # Run Foodcritic lint checks
+    rake test:syntax                # Run Knife syntax checks
+    rake test:travis                # Run test:syntax, test:lint, and test:unit
+    rake test:unit                  # Run ChefSpec examples
+    rake vagrant:destroy            # Destroy the VM
+    rake vagrant:halt               # Shutdown the VM
+    rake vagrant:provision          # Provision the VM using Chef
+    rake vagrant:ssh                # SSH into the VM
+
+As mentioned above, use `bundle exec` to start a Rake task:
+
+    $ bundle exec rake test
+
+The `test` task is an alias for `test:all` and also happens to be the default
+when no task is given. All test-related tasks are described in more detail
+below.
+
+### Knife
+
+The Rake task `test:syntax` will use `knife cookbook test` to run syntax checks
+on the cookbook, validating both Ruby files and templates.
+
+### Foodcritic
+
+The Rake task `test:lint` will use [Foodcritic] to run lint checks on the
+cookbook. Foodcritic is configured to fail if there are _any_ warnings that
+might stop the cookbook from working.
+
+### ChefSpec
+
+The Rake task `test:spec` will run all [ChefSpec] examples in the `spec`
+directory. Built on top of RSpec, ChefSpec allows you to write unit tests for
+Chef cookbooks. It runs your cookbook - without actually converging a node - and
+lets you make assertions about the resources that were created. This makes it
+the ideal tool to get fast feedback on cookbook changes.
+
+### serverspec
+
+The Rake task `test:integration` will run [serverspec] integration tests
+against a VM managed by Vagrant. The files `spec/integration/**/*_spec.rb` are
+the test files that are run at the end of the provisioning process by ssh'ing
+into the VM. For each VM you want to test, there must be a folder with specs in
+`spec/integration/` (the default node specs are in `spec/integration/default`).
+
+In case the VM is powered off, `rake test:integration` will boot it up first.
+When you no longer need the VM for integration testing, `rake
+test:integration_teardown` will shut it down. If you rather want to provision
+from scratch, set `INTEGRATION_TEARDOWN` accordingly. For example:
+
+    $ export INTEGRATION_TEARDOWN='vagrant:destroy'
+    $ rake test:integration_teardown
+    $ rake test:integration
+
+### Berkshelf
+
+[Berkshelf] is used to set up the cookbook and its dependencies prior to testing
+with Rake and Vagrant.
+
+The dependencies are defined in `Berksfile`, which in turn resolves the
+dependencies in `metadata.rb`. It is good practice to specify the cookbook
+sources in `Berksfile`, while keeping the cookbook versions in `metadata.rb`
+(the authoritative source of information for Chef).
+
+During testing, dependencies are installed to the `vendor/cookbooks` directory
+inside this cookbook.
+
+### Vagrant
+
+With [Vagrant], you can spin up a virtual machine and run your cookbook inside
+it via Chef Solo or Chef Client. The test setup requires to install **Vagrant
+1.2.x** from the [Vagrant downloads page].
+
+You will also need the [vagrant-berkshelf] plugin, which will make your cookbook
+and its dependencies automatically available to Vagrant when creating or
+provisioning a VM:
+
+    $ vagrant plugin install vagrant-berkshelf
+
+When everything is in place, this command will boot and provision the VM as
+specified in the `Vagrantfile`:
+
+    $ vagrant up
+
+In case the VM is already up, you can run the provisioners again with:
+
+    $ vagrant provision
+
+### Travis CI
+
+The cookbook includes a configuration for [Travis CI] that will run `rake
+test:travis` each time changes are pushed to GitHub. Simply enable Travis for
+your GitHub repository to get free continuous integration.
+
+Implementing CI with other systems should be as simple as running the commands
+in `.travis.yml`.
+
+
+[Berkshelf]: http://berkshelf.com
+[Bundler]: http://gembundler.com
+[ChefSpec]: https://github.com/acrmp/chefspec
+[Foodcritic]: http://acrmp.github.com/foodcritic/
+[Rake]: http://rake.rubyforge.org
+[Travis CI]: https://travis-ci.org
+[Vagrant downloads page]: http://downloads.vagrantup.com/
+[Vagrant]: http://vagrantup.com
+[serverspec]: http://serverspec.org/
+[vagrant-berkshelf]: https://github.com/RiotGames/vagrant-berkshelf

data/chef-skel.gemspec

@@ -4,10 +4,10 @@ require File.expand_path('../lib/chef_skel/version', __FILE__)
 Gem::Specification.new do |s|
   s.authors       = ['Mathias Lafeldt']
   s.email         = ['mathias.lafeldt@gmail.com']
-  s.description   = %q{Chef skeleton}
+  s.description   = %q{Skeleton for a testable Chef cookbook}
   s.summary       = s.description
-  s.homepage      = 'http://mlafeldt.github.com/chef-skel'
-  s.license       = 'MIT'
+  s.homepage      = 'https://github.com/mlafeldt/chef-skel'
+  s.license       = 'Apache 2.0'
 
   s.files         = `git ls-files`.split($\)
   s.executables   = s.files.grep(%r{^bin/}).map{ |f| File.basename(f) }

data/lib/chef_skel/rake_tasks.rb

@@ -38,6 +38,7 @@ end
 
 COOKBOOK_NAME = ENV.fetch('COOKBOOK_NAME', cookbook_name)
 COOKBOOK_PATH = ENV.fetch('COOKBOOK_PATH', 'vendor/cookbooks')
+KNIFE_CONFIG  = File.join(COOKBOOK_PATH, '.knife.rb')
 
 CLOBBER.include COOKBOOK_PATH, 'Berksfile.lock', '.kitchen', '.vagrant'
 
@@ -61,9 +62,20 @@ task :env do
 end
 
 namespace :test do
-  task :prepare do
-    ENV['COOKBOOK_PATH'] = COOKBOOK_PATH
+  task :prepare_cookbooks do
     sh 'berks', 'install', '--path', COOKBOOK_PATH
+  end
+
+  task :prepare_knife_config do
+    File.open(KNIFE_CONFIG, 'w') do |f|
+      f.puts "cache_type 'BasicFile'"
+      f.puts "cache_options :path => '#{File.join(ENV['HOME'], '.chef', 'checksums')}'"
+    end
+  end
+
+  task :prepare => [:prepare_cookbooks, :prepare_knife_config] do
+    # Export path to cookbooks
+    ENV['COOKBOOK_PATH'] = COOKBOOK_PATH
     # Run cleanup at exit unless an exception was raised.
     at_exit { Rake::Task['test:cleanup'].invoke if $!.nil? }
   end
@@ -74,7 +86,7 @@ namespace :test do
 
   desc 'Run Knife syntax checks'
   task :syntax => :prepare do
-    sh 'knife', 'cookbook', 'test', COOKBOOK_NAME, '--config', '.knife.rb',
+    sh 'knife', 'cookbook', 'test', COOKBOOK_NAME, '--config', KNIFE_CONFIG,
        '--cookbook-path', COOKBOOK_PATH
   end
 

data/lib/chef_skel/version.rb

@@ -1,3 +1,3 @@
 module ChefSkel
-  VERSION = '0.1.0'
+  VERSION = '0.1.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: chef-skel
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-06-24 00:00:00.000000000 Z
+date: 2013-06-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: berkshelf
@@ -107,7 +107,7 @@ dependencies:
     - - '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: Chef skeleton
+description: Skeleton for a testable Chef cookbook
 email:
 - mathias.lafeldt@gmail.com
 executables: []
@@ -115,17 +115,20 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
+- CHANGELOG.md
 - Gemfile
-- Gemfile.lock
+- LICENSE
+- README.md
 - Rakefile
+- TESTING.md
 - chef-skel.gemspec
 - lib/chef_skel/integration_spec_helper.rb
 - lib/chef_skel/rake_tasks.rb
 - lib/chef_skel/unit_spec_helper.rb
 - lib/chef_skel/version.rb
-homepage: http://mlafeldt.github.com/chef-skel
+homepage: https://github.com/mlafeldt/chef-skel
 licenses:
-- MIT
+- Apache 2.0
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -138,7 +141,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -3464971780163873864
+      hash: 2202343543367566813
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -147,11 +150,11 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -3464971780163873864
+      hash: 2202343543367566813
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.25
 signing_key: 
 specification_version: 3
-summary: Chef skeleton
+summary: Skeleton for a testable Chef cookbook
 test_files: []

data/Gemfile.lock

@@ -1,215 +0,0 @@
-PATH
-  remote: .
-  specs:
-    chef-skel (0.1.0)
-      berkshelf
-      chef
-      chefspec
-      foodcritic
-      rake
-      serverspec
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    activesupport (3.2.13)
-      i18n (= 0.6.1)
-      multi_json (~> 1.0)
-    addressable (2.3.4)
-    akami (1.2.0)
-      gyoku (>= 0.4.0)
-      nokogiri (>= 1.4.0)
-    berkshelf (2.0.5)
-      activesupport (>= 3.2.0)
-      addressable (~> 2.3.4)
-      buff-shell_out (~> 0.1)
-      celluloid (>= 0.14.0)
-      chozo (>= 0.6.1)
-      faraday (>= 0.8.5)
-      hashie (>= 2.0.2)
-      minitar (~> 0.5.4)
-      rbzip2 (~> 0.2.0)
-      retryable (~> 1.3.3)
-      ridley (~> 1.2.1)
-      solve (>= 0.5.0)
-      thor (~> 0.18.0)
-    buff-extensions (0.5.0)
-    buff-ruby_engine (0.1.0)
-    buff-shell_out (0.1.0)
-      buff-ruby_engine (~> 0.1.0)
-    builder (3.2.2)
-    celluloid (0.14.1)
-      timers (>= 1.0.0)
-    celluloid-io (0.14.1)
-      celluloid (>= 0.14.1)
-      nio4r (>= 0.4.5)
-    chef (11.4.4)
-      erubis
-      highline (>= 1.6.9)
-      json (>= 1.4.4, <= 1.7.7)
-      mixlib-authentication (>= 1.3.0)
-      mixlib-cli (~> 1.3.0)
-      mixlib-config (>= 1.1.2)
-      mixlib-log (>= 1.3.0)
-      mixlib-shellout
-      net-ssh (~> 2.6)
-      net-ssh-multi (~> 1.1.0)
-      ohai (>= 0.6.0)
-      rest-client (>= 1.0.4, < 1.7.0)
-      yajl-ruby (~> 1.1)
-    chefspec (1.3.1)
-      chef (>= 10.0)
-      erubis
-      fauxhai (>= 0.1.1, < 2.0)
-      minitest-chef-handler (>= 0.6.0)
-      rspec (~> 2.0)
-    chozo (0.6.1)
-      activesupport (>= 3.2.0)
-      hashie (>= 2.0.2)
-      multi_json (>= 1.3.0)
-    ci_reporter (1.8.4)
-      builder (>= 2.1.2)
-    diff-lcs (1.2.4)
-    erubis (2.7.0)
-    faraday (0.8.7)
-      multipart-post (~> 1.1)
-    fauxhai (1.1.1)
-      httparty
-      net-ssh
-      ohai
-    ffi (1.9.0)
-    foodcritic (2.1.0)
-      erubis
-      gherkin (~> 2.11.7)
-      nokogiri (~> 1.5.4)
-      rak (~> 1.4)
-      treetop (~> 1.4.10)
-      yajl-ruby (~> 1.1.0)
-    gherkin (2.11.8)
-      multi_json (~> 1.3)
-    gssapi (1.0.3)
-      ffi (>= 1.0.1)
-    gyoku (1.0.0)
-      builder (>= 2.1.2)
-    hashie (2.0.5)
-    highline (1.6.19)
-    httparty (0.11.0)
-      multi_json (~> 1.0)
-      multi_xml (>= 0.5.2)
-    httpclient (2.2.0.2)
-    httpi (0.9.7)
-      rack
-    i18n (0.6.1)
-    ipaddress (0.8.0)
-    json (1.7.7)
-    little-plugger (1.1.3)
-    logging (1.6.2)
-      little-plugger (>= 1.1.3)
-    mime-types (1.23)
-    minitar (0.5.4)
-    minitest (4.7.5)
-    minitest-chef-handler (1.0.1)
-      chef
-      ci_reporter
-      minitest (~> 4.7.3)
-    mixlib-authentication (1.3.0)
-      mixlib-log
-    mixlib-cli (1.3.0)
-    mixlib-config (1.1.2)
-    mixlib-log (1.6.0)
-    mixlib-shellout (1.1.0)
-    multi_json (1.7.7)
-    multi_xml (0.5.4)
-    multipart-post (1.2.0)
-    net-http-persistent (2.8)
-    net-ssh (2.6.7)
-    net-ssh-gateway (1.2.0)
-      net-ssh (>= 2.6.5)
-    net-ssh-multi (1.1)
-      net-ssh (>= 2.1.4)
-      net-ssh-gateway (>= 0.99.0)
-    nio4r (0.4.6)
-    nokogiri (1.5.10)
-    nori (1.1.5)
-    ohai (6.16.0)
-      ipaddress
-      mixlib-cli
-      mixlib-config
-      mixlib-log
-      mixlib-shellout
-      systemu
-      yajl-ruby
-    polyglot (0.3.3)
-    rack (1.5.2)
-    rak (1.4)
-    rake (10.1.0)
-    rbzip2 (0.2.0)
-    rest-client (1.6.7)
-      mime-types (>= 1.16)
-    retryable (1.3.3)
-    ridley (1.2.3)
-      addressable
-      buff-extensions (~> 0.3)
-      buff-shell_out (~> 0.1)
-      celluloid (~> 0.14.0)
-      celluloid-io (~> 0.14.0)
-      erubis
-      faraday (>= 0.8.4)
-      hashie (>= 2.0.2)
-      json (>= 1.7.7)
-      mixlib-authentication (>= 1.3.0)
-      net-http-persistent (>= 2.8)
-      net-ssh
-      retryable
-      solve (>= 0.4.4)
-      varia_model (~> 0.1)
-      winrm (~> 1.1.0)
-    rspec (2.13.0)
-      rspec-core (~> 2.13.0)
-      rspec-expectations (~> 2.13.0)
-      rspec-mocks (~> 2.13.0)
-    rspec-core (2.13.1)
-    rspec-expectations (2.13.0)
-      diff-lcs (>= 1.1.3, < 2.0)
-    rspec-mocks (2.13.1)
-    rubyntlm (0.1.1)
-    savon (0.9.5)
-      akami (~> 1.0)
-      builder (>= 2.1.2)
-      gyoku (>= 0.4.0)
-      httpi (~> 0.9)
-      nokogiri (>= 1.4.0)
-      nori (~> 1.0)
-      wasabi (~> 1.0)
-    serverspec (0.6.7)
-      highline
-      net-ssh
-      rspec (~> 2.13.0)
-    solve (0.5.0)
-    systemu (2.5.2)
-    thor (0.18.1)
-    timers (1.1.0)
-    treetop (1.4.14)
-      polyglot
-      polyglot (>= 0.3.1)
-    uuidtools (2.1.4)
-    varia_model (0.1.0)
-      buff-extensions (~> 0.1)
-      hashie (>= 2.0.2)
-    wasabi (1.0.0)
-      nokogiri (>= 1.4.0)
-    winrm (1.1.2)
-      gssapi (~> 1.0.0)
-      httpclient (~> 2.2.0.2)
-      logging (~> 1.6.1)
-      nokogiri (~> 1.5.0)
-      rubyntlm (~> 0.1.1)
-      savon (= 0.9.5)
-      uuidtools (~> 2.1.2)
-    yajl-ruby (1.1.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  chef-skel!