clc-fork-chef-metal 0.11.beta.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c229a92cb5e105e2be9320f683c3d1acbddd051f
+  data.tar.gz: aeed9e2cf4740182b8091ff446a9cb0bbbc56ea3
+SHA512:
+  metadata.gz: a11e30995c1f7e74914cf875fef68ca58a86b3953473bd77fd0e7efb56defb1d40cbec52d5a79ac12dba4673bc44fb153cd7b4ed122b85c36e7851c8364fb33e
+  data.tar.gz: 36496bc2ac754cad82abfa77e7386a107fa2ff7ad982c6ac14beecf54f53f132280ebcce9e0ff982cb432855549264b448f7a308c1e9bb8bbc211d588d8b0c4c

data/CHANGELOG.md

@@ -0,0 +1,106 @@
+# Chef Metal Changelog
+
+## 0.11.beta.5 (5/28/2014)
+
+- fix issue setting Hosted Chef ACLs on nodes
+- fix single-machine converge crash
+
+## 0.11.beta.2 (5/27/2014)
+
+- Bring in cheffish-0.5.beta.2
+
+## 0.11.beta (5/23/2014)
+
+- New Driver interface (see docs/ and blogs/ directories for documentation)
+
+## 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-metal 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 ChefMetal.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-metal-vagrant and chef-metal-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_metal/provisioner_init/<scheme>_init.rb`.  It will be required when a node is encountered with that scheme.  It should call ChefMetal.add_registered_provisioner_class(<scheme>, <provisioner class name>).  For the provisioner_url `fog:AWS:21348723432`, the scheme is "fog" and the file is `chef_metalprovisioner_init/fog_init.rb`.  It should call `ChefMetal.add_registered_provisioner_class('fog', ChefMetal::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-metal 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,201 @@
+Chef Metal
+==========
+
+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!
+
+Currently, chef-metal supports vagrant, Unixes/ssh, and Windows/winrm with real chef-servers or with automagical chef-zero tunneling.  Fog and Docker support (to cover EC2 and LXC) are next up.  Further out, we'd like to extend support to image factories (using the machine resource to produce images) and PXE support.
+
+Try It Out
+----------
+
+To give it a spin, get chef 11.8 or greater try this:
+
+    git clone https://github.com/opscode/cheffish.git
+    cd cheffish
+    rake install
+    cd ..
+
+    git clone https://github.com/opscode/chef-metal.git
+    cd chef-metal
+    rake install
+    
+    cd chef-metal
+    chef-client -z -o myapp::vagrant,myapp::linux,myapp::small
+
+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!).
+
+What Is Chef Metal?
+-------------------
+
+Chef Metal has two major abstractions: the machine resource, and provisioners.
+
+### The `machine` resource
+
+You declare what your machines do (recipes, tags, etc.) with the `machine` resource, the fundamental unit of Chef Metal.  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-metal/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 :)
+
+Kitchen
+-------
+
+Chef Metal 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.
+
+Provisioners
+------------
+
+Provisioners 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 provisioner API is separated out so that new provisioners 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.).
+
+Provisioners 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.
+
+Provisioners each have their own repository.  Current provisioners:
+
+**Cloud:**
+- [FOG: EC2, DigitalOcean, OpenStack, etc.](https://github.com/opscode/chef-metal-fog)
+
+**Virtualization:**
+- [Vagrant: VirtualBox, VMWare Fusion, etc.](https://github.com/opscode/chef-metal-vagrant)
+
+**Containers:**
+- [LXC](https://github.com/opscode/chef-metal-lxc)
+- [Docker](https://github.com/opscode/chef-metal-docker)
+
+**Bare Metal:**
+- [SSH (no PXE)](https://github.com/double-z/chef-metal-ssh)
+
+### Vagrant
+
+chef-zero comes with a provisioner for Vagrant, an abstraction that covers VirtualBox, VMWare and other Virtual Machine drivers. To run it, you can check out the sample recipes with:
+
+```
+chef-client -z -o myapp::vagrant,myapp::linux,myapp::small
+```
+
+The provisioner specification is in myapp::vagrant and myapp::linux [sample recipes](https://github.com/opscode/chef-metal/tree/master/cookbooks/myapp/recipes), copy/pasted here for your convenience:
+
+```ruby
+vagrant_cluster "#{ENV['HOME']}/machinetest"
+
+directory "#{ENV['HOME']}/machinetest/repo"
+with_chef_local_server :chef_repo_path => "#{ENV['HOME']}/machinetest/repo"
+
+vagrant_box 'precise64' do
+  url 'http://files.vagrantup.com/precise32.box' 
+end
+```
+
+`vagrant_cluster` declares a directory where all the vagrant definitions will be stored, and uses `with_provisioner` internally to tell Chef Metal that this is the provisioner we want to use for machines.
+
+`vagrant_box` makes sure a particular vagrant box exists, and lets you specify `provisioner_options` for things like port forwarding, OS definitions, and any other vagrant-isms.  A more complicated vagrant box, with provisioner options, can be found in [myapp::windows](https://github.com/opscode/chef-metal/blob/master/cookbooks/myapp/recipes/windows.rb).
+
+`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
+require 'chef/config'
+
+with_chef_server "https://chef-server.example.org", {
+  :client_name => Chef::Config[:node_name],
+  :signing_key_filename => Chef::Config[:client_key]
+}
+```
+
+Typically, you declare these in separate files from your machine resources.  Chef Metal picks up the provisioners you have declared, and uses them to instantiate the machines you request.  The actual machine definitions, in this case, are in `myapp::small`, and are generic--you could use them against EC2 as well:
+
+```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
+```
+
+### Fog (EC2 and friends)
+
+chef-metal also comes with a [Fog](http://fog.io/) provisioner that handles provisioning to Amazon's EC2 and other cloud drivers.  (Only EC2 has been tested so far.)  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).
+
+Once your credentials are in, basic usage looks like this:
+
+```
+chef-client -z -o myapp::ec2,myapp::small
+```
+
+The provisioner definition in `myapp::ec2` looks like this:
+
+```ruby
+ec2testdir = File.expand_path('~/ec2test')
+
+directory ec2testdir
+
+with_fog_ec2_provisioner # :driver => 'AWS'
+
+with_provisioner_options :image_id => 'ami-5ee70037'
+
+fog_key_pair 'me' do
+  private_key_path "#{ec2testdir}/me"
+  public_key_path "#{ec2testdir}/me.pub"
+end
+```
+
+`with_fog_ec2_provisioner` tells chef-metal to use the Fog provisioner against EC2.  If you specify your credentials in `~/.aws/config`, you don't *have* to specify anything else; it will use the Fog defaults.  You may pass a hash of parameters to `with_fog_ec2_provisioner` that is described [here](https://github.com/opscode/chef-metal/blob/master/lib/chef_metal/provisioner/fog_provisioner.rb#L21-L32).
+
+`fog_key_pair` creates a new key pair (if the files do not already exist) and automatically tells the Provisioner to use it to bootstrap subsequent machines.  The private/public key pair will be automatically authorized to log on to the instance on first boot.
+
+To pass options like ami, you can say something like this:
+
+```ruby
+with_provisioner_options :image_id => 'ami-5ee70037'
+```
+
+If you need to pass bootstrapping options on a per-machine basis, you can do that as well by doing something like the following:
+
+```ruby
+machine "Ubuntu_64bit" do
+  action :create
+  provisioner_options 'bootstrap_options' => {
+    'image_id' => 'ami-59a4a230',
+    'flavor_id' => 't1.micro'
+  }
+end
+```
+
+You will notice that we are still using `myapp::small` here.  Machine definitions are generally provisioner-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.
+
+Bugs and The Plan
+-----------------
+
+It's early days.  *Please* submit bugs at https://github.com/opscode/chef-metal/issues, contact jkeiser on Twitter at @jkeiser2, email at jkeiser@opscode.com
+
+If you are interested in the Plan for Chef Metal, you can peruse our [Trello board](https://trello.com/b/GcSzW0GM/chef-metal)!  Please add suggestions there, vote or comment on issues that are important to you, and feel free to contribute by picking up a card.  Chat with me (jkeiser@opscode.com) if you would like some context on how to go about implementing a card, or just go hog wild and submit a PR :)