chef-provisioning 0.15

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 611cb52d02b2fcedc3d919e3c43ffec244d24508
+  data.tar.gz: 1a5effed9787a551bfb2fb1eb9bd48e7d305de37
+SHA512:
+  metadata.gz: 24df478126fe1673f447c71a3c2f17f20389faed39d0799e1d2770faa413b0a1510308d566c2c1c97216bb9d219a92abba6435f913e1d3732b79ea97108ab5d6
+  data.tar.gz: 2a90b86f5c2d502e3c557476ad62fd3b5a9d3833c86771d48bce4fb2abb71ceb447154dd2fff26683b05182f767405fdfa842e4aa0c744bfba673456ba96a996

data/CHANGELOG.md

@@ -0,0 +1,207 @@
+# Chef Metal Changelog
+## 0.15 (10/29/2014)
+
+- Rename from chef-metal to chef-provisioning
+
+## 0.14.2 (9/2/2014)
+
+- Disable auto batching
+- Fix for with_machine_options context hash
+- Pass timeout from execution_options to winrm set_timeout
+- Add better error message when driver does not specify driver_url
+- Add info that location.driver_url is required
+- Remove Chef 11.14 alpha note in readme
+- Gracefully handle Host Down and Network Unreachable
+
+## 0.14.1 (8/18/2014)
+
+- Fix "metal execute mario ls" to work again
+
+## 0.14 (8/18/2014)
+
+- FEATURE: Add the machine_image resource (@jkeiser, @johnewart):
+  ```ruby
+  machine_image 'base' do
+    machine_options :bootstrap_options => { :image_id => 'ami-1234798123431', :ssh_username => 'root' }
+    recipe 'secure_base'
+    recipe 'corp_users'
+  end
+  # Build an image based on 'base' that has apache
+  machine_image 'apache' do
+    # All bootstrap options, like ssh_username, are carried forward
+    from_image 'base'
+    recipe 'apache2'
+  end
+  # Build an image with my web app based on the apache base image
+  machine_image 'myapp' do
+    from_image 'apache'
+    recipe 'mywebapp'
+  end
+  # Build an image with mysql and my schema based on the corporate base image
+  machine_image 'mydb' do
+    from_image 'base'
+    recipe 'mysql'
+    recipe 'myschema'
+  end
+  # Build a DB machine from mydb.  Does not reinstall stuff! :)
+  machine 'db' do
+    from_image 'mydb'
+  end
+  # Build a web app machine from myapp.  Does not reinstall stuff! :)
+  machine 'myapp1' do
+    from_image 'myapp'
+  end
+  ```
+  - Creates a node with the name of the machine_image, which contains metadata
+    like the username of the image.  This makes things like AWS image registries
+    possible.
+- Fix the no_converge convergence strategy (@johnewart)
+- SSH port forwarding improvements:
+  - Detects *any* IP on the localhost and forwards it--not just 127.0.0.1
+  - Binds to localhost on the remote side instead of 127.0.0.1, allowing for IPv6 communication
+  - Tries multiple ports--if the origin port is already taken, tries "0" (ephemeral).
+- Fix SSH race condition causing port forwarding to happen twice (and fail miserably)
+- Add Chef::Provisioning.connect_to_machine('mario')
+
+## 0.13 (6/17/2014)
+
+- make winrm work again (@mwrock)
+- add bootstrap_proxy as a convergence_option for when target machines require a proxy (@MrMMorris)
+
+## 0.12.1 (6/18/2014)
+
+- fix machine_batch action :setup
+- fix issue with default machine_batch names being non-unique across recipes
+
+## 0.12 (6/18/2014)
+
+- Remove chef-provisioning-fog and chef-provisioning-vagrant as dependencies (install whatever things you want directly!)
+- Fix ssl_verify_mode to work correctly when other HTTPS calls are made (@mwrock)
+- Fix machine_file and machine_execute resources (@irvingpop)
+
+## 0.11.2 (6/4/2014)
+
+- Fix issue where machines with different drivers could get default options from the global current driver
+
+## 0.11.1 (6/4/2014)
+
+- fix local mode port forwarding on IPv6 hosts
+
+## 0.11 (6/4/2014)
+
+- New Driver interface (see docs/ and blogs/ directories for documentation)
+- New configuration (see docs/ and blogs/)
+- get rid of annoying SSL warning (note: this turns off SSL verification, which was the default anyway)
+- fix machine_batch error report to be less verbose
+- fail when machine is being moved from driver to driver
+- @marcusn disconnect from SSH when there is a problem
+- fix SSH gateway code to honor any options given (@marcusn)
+- Make machine_batch auto batching smarter (only batch things that have the same actions)
+- Allow auto batching to be turned off with `auto_batch_machines = false` in recipes or config
+- Allow this:
+  ```ruby
+  machine_batch do
+    machine 'a'
+    machine 'b'
+  end
+  ```
+- Allow this:
+  ```ruby
+  machine_batch do
+    machines 'a', 'b', 'c'
+    action :destroy
+  end
+- fix issue setting Hosted Chef ACLs on nodes
+- fix local mode forwarding in mixed IPv4/IPv6 environments
+
+## 0.10.2 (5/2/2014)
+
+- Fix crash with add_provisioner_options when provisioner_options is not yet set
+
+## 0.10.1 (5/2/2014)
+
+- Fix a crash when uploading files in a machine batch
+
+## 0.10 (5/1/2014)
+
+- Parallelism!
+  - All machines by default will be created in parallel just before the first "machine" definition. They will attempt to run all the way to converge.  If they fail, add "with_machine_batch 'mybatch', :setup"
+  - Use "with_machine_batch 'mybatch'" before any machines if you want tighter control. Actions include :delete, :acquire, :setup, and :converge.
+- Parallelizableness: chef-provisioning now stores data in the run_context instead of globally, so that it can be run multiple times in parallel. This capability is not yet being used.
+
+## 0.9.4 (4/23/2014)
+
+- Preserve provisioner_output in machine resource (don't destroy it!!)
+
+## 0.9.3 (4/13/2014)
+
+- SSH: Treat EHOSTUNREACH as "machine not yet available" (helps with AWS)
+
+## 0.9.2 (4/13/2014)
+
+- Timeout stability fixes (makes EC2 a little stabler for some AMIs)
+
+## 0.9.1 (4/11/2014)
+
+- Make write_file and upload_file create parent directory
+
+## 0.9 (4/9/2014)
+
+- Add `files` and `file` attributes to the `machine` resource
+- Fix `machine_execute` resource (@irvingpop)
+- Fix `machine :converge` action (thanks @double-z)
+- Make chef-client timeout longer by default (2 hours)
+- Make chef_client_timeout a configurable option for all convergence strategies and provisioner_options
+- Add `metal cp` command
+
+## 0.8.2 (4/9/2014)
+
+- Add timeout support to execute
+- Fix machine_file resource
+- Add ohai_hints DSL to machine resource (@xorl)
+
+## 0.8.1 (4/9/2014)
+
+- Bug: error! was not raising an error in the SSH and WinRM transports
+- Transports: stream output automatically when in debug
+- Support the :read_only execute hint (for Docker)
+- Add more metal command lines (converge, update, delete)
+- Add Chef::Provisioning.connect_to_machine(machine_name) method to get Machine object for a node name
+
+## 0.8 (4/8/2014)
+
+- New machine_execute resource! (irving@getchef.com)
+- Experimental "metal" command line: metal execute NODENAME COMMAND ARGS
+- Transport: Add ability to stream execute() for better nested chef-client debugging
+
+## 0.7 (4/5/2014)
+
+- Change transport interface: add ability to rewrite URL instead of forwarding ports
+
+## 0.6 (4/4/2014)
+
+- Vagrant and Fog provisioners moved to their own gems (chef-provisioning-vagrant and chef-provisioning-fog)
+- Support for Hosted and Enterprise Chef (https://github.com/dafyddcrosby)
+
+## 0.5 (4/3/2014)
+
+* Provisioner interface changes designed to allow provisioners to be used outside of Chef (doubt@getchef.com)
+  * All Provisioner and Machine methods now take "action_handler" instead of "driver."  It uses the ActionHandler interface described in action_handler.rb.  In short:
+    - driver.run_context -> action_handler.recipe_context
+    - driver.updated_by_last_action(true) -> action_handler.updated!
+    - driver.converge_by -> action_handler.perform_action
+    - driver.cookbook_name -> driver.debug_name
+  * Convergence strategy: delete_chef_objects() -> cleanup_convergence()
+* Ability to get back to a machine from a node (another Provisioner interface change) (doubt@getchef.com):
+  * Provisioners must create a file named `chef_provisioning/provisioner_init/<scheme>_init.rb`.  It will be required when a node is encountered with that scheme.  It should call Chef::Provisioning.add_registered_provisioner_class(<scheme>, <provisioner class name>).  For the provisioner_url `fog:AWS:21348723432`, the scheme is "fog" and the file is `chef_provisioningprovisioner_init/fog_init.rb`.  It should call `Chef::Provisioning.add_registered_provisioner_class('fog', Chef::Provisioning::Provisioner::FogProvisioner)`.
+  * Provisioner classes must implement the class method `inflate(node)`, which should create a Provisioner instance appropriate to the given `node` (generally by looking at `node['normal']['provisioner_output']`)
+* New `NoConverge` convergence strategy that creates a node but does not install Chef or converge.
+* Support for machine_file `group`, `owner` and `mode` attributes (@irvingpop)
+* SSH transport (ryan@segv.net): try to enable pty when possible (increases chance of successful connection).  Set options[:ssh_pty_enable] to `false` to turn this off.  Set `true` to force it (and fail if we can't get it)
+
+## 0.4 (3/29/2014)
+
+* EC2: Make it possible for multiple IAM users to converge chef-provisioning on the same account
+* Openstack: Openstack support via the Fog driver! (@cstewart87)
+* EC2: Add :use_private_ip_for_ssh option, and use private ip by default if public IP does not exist.  (@xorl, @dafyddcrosby)
+* RHEL/Centos: fix platform detection and installation

data/LICENSE

@@ -0,0 +1,201 @@
+                              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,260 @@
+[![Stories in Ready](https://badge.waffle.io/opscode/chef-provisioning.png?label=ready&title=Ready)](https://waffle.io/opscode/chef-provisioning)
+Chef Provisioning
+==========
+[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/opscode/chef-metal?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
+This library solves the problem of repeatably creating machines and infrastructures in Chef.  It has a plugin model that lets you write bootstrappers for your favorite infrastructures, including VirtualBox, EC2, LXC, bare metal, and many more!
+
+[This video](https://www.youtube.com/watch?v=Yb8QdL30WgM) explains the basics of chef-provisioning (though provisioners are now called drivers).  Slides (more up to date) are [here](http://slides.com/jkeiser/chef-provisioning).
+
+Date       | Blog
+-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------
+6/3/2014   | [machine_batch and parallelization](https://github.com/opscode/chef-provisioning/blob/master/docs/blogs/2012-05-28-machine_batch.html.markdown#chef-provisioning-parallelization)
+6/3/2014   | [Chef Provisioning, Configuration and Drivers](https://github.com/opscode/chef-provisioning/blob/master/docs/blogs/2012-05-22-new-driver-interface.html.markdown#chef-provisioning-configuration-and-drivers)
+3/4/2014   | [Chef Provisioning 0.2: Overview](http://www.getchef.com/blog/2014/03/04/chef-provisioning-0-2-release/) - this is a pretty good overview (though dated).
+12/20/2013 | [Chef Provisioning Alpha](http://www.getchef.com/blog/2013/12/20/chef-provisioning-alpha/)
+
+Documentation
+-------------
+* [Frequently Asked Questions](https://github.com/opscode/chef-provisioning/blob/master/docs/faq.md)
+* [Configuration](https://github.com/opscode/chef-provisioning/blob/master/docs/configuration.md#configuring-and-using-provisioning-drivers)
+* [Writing Drivers](https://github.com/opscode/chef-provisioning/blob/master/docs/building_drivers.md#writing-drivers)
+* [Embedding](https://github.com/opscode/chef-provisioning/blob/master/docs/embedding.md)
+* [Providers](https://github.com/opscode/chef-provisioning/blob/master/docs/providers)
+
+Try It Out
+----------
+
+You can try out Chef Provisioning in many different flavors.
+
+### Vagrant
+
+To give it a spin, install Vagrant and VirtualBox and try this from the `chef-provisioning/docs/examples` directory:
+
+```
+gem install chef-provisioning chef-provisioning-vagrant
+export CHEF_DRIVER=vagrant
+chef-client -z vagrant_linux.rb simple.rb
+```
+
+This will create two vagrant precise64 linux boxes, "mario" and "luigi1", in `~/machinetest`, bootstrapped to an empty runlist.  For Windows, you can replace `myapp::linux` with `myapp::windows`, but you'll need your own Windows vagrant box to do that (licensing!).
+
+### AWS
+
+If you have an AWS account, you can spin up a machine there like this:
+
+```
+gem install chef-provisioning chef-provisioning-fog
+export CHEF_DRIVER=fog:AWS
+chef-client -z simple.rb
+```
+
+This will create two linux boxes in the AWS account referenced by your default profile in `~/.aws/config` (or your environment variables).
+
+### DigitalOcean
+
+If you are on DigitalOcean and using the `tugboat` gem, you can do this:
+
+```
+gem install chef-provisioning chef-provisioning-fog
+export CHEF_DRIVER=fog:DigitalOcean
+chef-client -z simple.rb
+```
+
+If you aren't using the `tugboat` gem, you can put `driver` and `driver_options` into your `.chef/knife.rb` file.
+
+This will use your tugboat settings to create whatever sort of instance you normally create.
+
+### Cleaning up
+
+When you are done with the examples, run this to clean up:
+
+```
+chef-client -z destroy_all.rb
+```
+
+What Is Chef Provisioning?
+-------------------
+
+Chef Provisioning has two major abstractions: the machine resource, and drivers.
+
+### The `machine` resource
+
+You declare what your machines do (recipes, tags, etc.) with the `machine` resource, the fundamental unit of Chef Provisioning.  You will typically declare `machine` resources in a separate, OS/provisioning-independent file that declares the *topology* of your app--your machines and the recipes that will run on them.
+
+The machine resources from the example [myapp::small](https://github.com/opscode/chef-provisioning/blob/master/cookbooks/myapp/recipes/small.rb) are pretty straightforward.  Here's a copy/paste:
+
+```ruby
+machine 'mario' do
+  recipe 'postgresql'
+  recipe 'mydb'
+  tag 'mydb_master'
+end
+
+num_webservers = 1
+
+1.upto(num_webservers) do |i|
+  machine "luigi#{i}" do
+    recipe 'apache'
+    recipe 'mywebapp'
+  end
+end
+```
+
+You will notice the dynamic nature of the number of web servers.  It's all code, your imagination is the limit :)
+
+### Drivers
+
+Drivers handle the real work of getting those abstract definitions into real, physical form.  They handle the following tasks, idempotently (you can run the resource again and again and it will only create the machine once--though it may notice things are wrong and fix them!):
+
+* Acquiring machines from the cloud, creating containers or VMs, or grabbing bare metal
+* Connecting to those machines via ssh, winrm, or other transports
+* Bootstrapping chef onto the machines and converging the recipes you suggested
+
+The driver API is separated out so that new drivers can be made with minimal effort (without having to rewrite ssh, tunneling, bootstrapping, and OS support).  But to the user, they appear as a single thing, so that the machine acquisition can use its smarts to autodetect the other bits (transports, OS's, etc.).
+
+Drivers save their data in the Chef node itself, so that they will be accessible to everyone who is using the Chef server to manage the nodes.
+
+Drivers each have their own repository.  Current drivers:
+
+**Cloud:**
+- [FOG: EC2, DigitalOcean, OpenStack, etc.](https://github.com/opscode/chef-provisioning-fog)
+
+**Virtualization:**
+- [Vagrant: VirtualBox, VMWare Fusion, etc.](https://github.com/opscode/chef-provisioning-vagrant)
+- [VSphere](https://github.com/RallySoftware-cookbooks/chef-provisioning-vsphere) (not yet up to date with 0.11)
+
+**Containers:**
+- [LXC](https://github.com/opscode/chef-provisioning-lxc) (not yet up to date with 0.11)
+- [Docker](https://github.com/opscode/chef-provisioning-docker)
+
+**Bare Metal:**
+- [SSH (no PXE)](https://github.com/double-z/chef-provisioning-ssh) (not yet up to date with 0.11)
+
+### Anatomy of a Recipe
+
+chef-zero comes with a provisioner for Vagrant, an abstraction that covers VirtualBox, VMWare and other Virtual Machine drivers. In docs/examples, you can run this to try it:
+
+```ruby
+export CHEF_DRIVER=vagrant
+chef-client -z vagrant_linux.rb simple.rb
+```
+
+This is a chef-client run, which runs multiple **recipes.** Chef Provisioning is nothing but resources you put in recipes.
+
+The driver is specified on the command line.  Drivers are URLs.  You could use `vagrant:~/vms` or `fog:AWS:default:us-east-1' as driver URLs.  More information [here.](https://github.com/opscode/chef-provisioning/blob/master/docs/configuration.md#setting-the-driver-with-a-driver-url)
+
+The `vagrant_linux.rb` recipe handles the physical specification of the machines and Vagrant box:
+
+```ruby
+require 'chef/provisioning_vagrant'
+
+vagrant_box 'precise64' do
+  url 'http://files.vagrantup.com/precise64.box'
+end
+
+with_machine_options :vagrant_options => {
+  'vm.box' => 'precise64'
+}
+```
+
+`require 'chef/provisioning_vagrant'` is how we bring in the `vagrant_box` resource.
+
+`vagrant_box` makes sure a particular vagrant box exists, and lets you specify `machine_options` for things like port forwarding, OS definitions, and any other vagrant-isms.
+
+Typically, you declare these in separate files from your machine resources.  Chef Provisioning picks up the drivers and machine_options you have declared, and uses them to instantiate the machines you request.  The actual machine definitions, in this case, are in `simple.rb`, and are generic--you could use them against Azure or EC2 as well:
+
+```ruby
+machine 'mario' do
+  tag 'itsame'
+end
+```
+
+Other directives, like `recipe 'apache'`, help you set run lists and other information about the machine.
+
+### Fog (EC2, Openstack and friends)
+
+chef-provisioning also comes with a [Fog](http://fog.io/) provisioner that handles provisioning to Openstack, Rackspace, Amazon's EC2 and other cloud drivers.  Before you begin, you will need to put your AWS credentials in ~/.aws/config in the format [mentioned in Option 1 here](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#d0e726).  There are other ways to specify your credentials, but this is the standard one for the Amazon CLI.
+
+Once your credentials are in, basic usage looks like this:
+
+```
+export CHEF_DRIVER=fog:AWS
+chef-client -z simple.rb
+```
+
+Other valid URLs include `fog:AWS:myprofilename` and `fog:AWS:profilename:us-west-2`.
+
+Most Chef Provisioning drivers try hard to provide reasonable defaults so you can get started easily.  Once you have specified your credentials, AMIs and other things are chosen for you.
+
+You will usually want to create or input a custom key pair for bootstrap. To customize, specify keys and AMI and other options, you can make recipes like this:
+
+```ruby
+require 'chef/provisioning_fog'
+
+fog_key_pair 'my_bootstrap_key'
+
+with_machine_options :bootstrap_options => {
+  :key_name => 'my_bootstrap_key',
+  :image_id => 'ami-59a4a230',
+  :flavor_id => 't1.micro'
+}
+```
+
+`fog_key_pair` creates a new key pair (if the files do not already exist) and uploads it to AWS (it will toss an error if the key pair already exists and does not match). By default, `fog_key_pair` will look for matching key files in .chef/keys, ~/.chef/keys and ~/.ssh.  If it does not find one, it will place the key in `.chef/keys`.  You can override this path in fog_key_pair, but if you do, you will want to modify `private_key_paths` in your configuration to match.
+
+`with_machine_options` specifies machine_options that will be applied to any `machine` resources chef-client encounters.
+
+You will notice that we are still using `simple.rb` here.  Machine definitions are generally driver-independent.  This is an important feature that allows you to spin up your clusters in different places to create staging, test or miniature dev environments.
+
+### Pointing Boxes at Chef Servers
+
+By default, Chef Provisioning will put your boxes on the same Chef server you started chef-client with (in the case of -z, that's a local chef-zero server). Sometimes you want to put your boxes on different servers.  There are a couple of ways to do that:
+
+```ruby
+with_chef_local_server :chef_repo_path => '~/repo'
+```
+
+`with_chef_local_server` is a generic directive that creates a chef-zero server pointed at the given repository.  nodes, clients, data bags, and all data will be stored here on your provisioner machine if you do this.
+
+You can use `with_chef_server` instead if you want to point at OSS, Hosted or Enterprise Chef, and if you don't specify a Chef server at all, it will use the one you are running chef-client against. Keep in mind when using `with_chef_server` and running `chef-client -z` on your workstation that you will also need to set the client name and signing key for the chef server. If you've already got knife.rb set up, then something like this will correctly create a client for the chef server on instance using your knife.rb configuration:
+
+```ruby
+with_chef_server "https://chef-server.example.org",
+  :client_name => Chef::Config[:node_name],
+  :signing_key_filename => Chef::Config[:client_key]
+```
+
+**Note for Hosted/Enterprise Chef Servers**
+
+Currently, you will need to add the 'clients' group to the 'admin' group in order for machine provisioning to work:
+
+```
+knife edit /groups/admin.json -e <editor>
+```
+Then add:
+```
+{
+  "users": [
+    "pivotal" # This is an internal superuser for Hosted/Enterprise Chef
+  ],
+  "groups": [
+    "clients" # This is what you need to add
+  ]
+}
+```
+
+This can also be done through the Chef Server web UI (Administration tab > Groups > select admins Group > Add 'clients'
+
+
+Kitchen
+-------
+
+Chef Provisioning also works with Test Kitchen, allowing you to test entire clusters, not just machines!  The repository for the kitchen-metal gem is https://github.com/doubt72/kitchen-metal.
+
+Bugs and The Plan
+-----------------
+
+Please submit bugs, gripes and feature requests at [https://github.com/opscode/chef-provisioning/issues](https://twitter.com/jkeiser2), contact jkeiser on Twitter at @jkeiser2, email at [jkeiser@getchef.com](mailto:jkeiser@getchef.com)
+
+To contribute, just make a PR in the appropriate repo--also, make sure you've [signed the Chef Contributor License Agreement](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L) (quick couple of minutes online), since this is going into core Chef eventually. It takes some time to process, so if you've just done it, let me know in the PR :)  If you already signed this for a Chef contribution, you don't need to do so again--if you're not sure, you can check for your name [here](https://wiki.opscode.com/display/chef/Approved+Contributors)!