RubyGems - microwave - Versions diffs - 1.0.2 → 1.0.3 - Mend

microwave 1.0.2 → 1.0.3

Files changed (125) hide show

data/Rakefile +4 -4
data/bin/chef-solo +2 -0
data/spec/spec_helper.rb +2 -0
data/spec/unit/checksum/storage/filesystem_spec.rb +4 -4
data/spec/unit/config_spec.rb +7 -4
data/spec/unit/data_bag_spec.rb +11 -11
data/spec/unit/formatters/error_inspectors/compile_error_inspector_spec.rb +8 -8
data/spec/unit/formatters/error_inspectors/resource_failure_inspector_spec.rb +5 -5
metadata +10 -124
data/distro/README +0 -2
data/distro/arch/etc/conf.d/chef-client.conf +0 -5
data/distro/arch/etc/conf.d/chef-expander.conf +0 -8
data/distro/arch/etc/conf.d/chef-server-webui.conf +0 -10
data/distro/arch/etc/conf.d/chef-server.conf +0 -10
data/distro/arch/etc/conf.d/chef-solr.conf +0 -8
data/distro/arch/etc/rc.d/chef-client +0 -90
data/distro/arch/etc/rc.d/chef-expander +0 -78
data/distro/arch/etc/rc.d/chef-server +0 -78
data/distro/arch/etc/rc.d/chef-server-webui +0 -78
data/distro/arch/etc/rc.d/chef-solr +0 -78
data/distro/common/html/chef-client.8.html +0 -145
data/distro/common/html/chef-expander.8.html +0 -164
data/distro/common/html/chef-expanderctl.8.html +0 -146
data/distro/common/html/chef-server-webui.8.html +0 -185
data/distro/common/html/chef-server.8.html +0 -182
data/distro/common/html/chef-solo.8.html +0 -191
data/distro/common/html/chef-solr.8.html +0 -165
data/distro/common/html/knife-bootstrap.1.html +0 -241
data/distro/common/html/knife-client.1.html +0 -219
data/distro/common/html/knife-configure.1.html +0 -170
data/distro/common/html/knife-cookbook-site.1.html +0 -241
data/distro/common/html/knife-cookbook.1.html +0 -384
data/distro/common/html/knife-data-bag.1.html +0 -238
data/distro/common/html/knife-environment.1.html +0 -267
data/distro/common/html/knife-exec.1.html +0 -134
data/distro/common/html/knife-index.1.html +0 -125
data/distro/common/html/knife-node.1.html +0 -250
data/distro/common/html/knife-recipe.1.html +0 -92
data/distro/common/html/knife-role.1.html +0 -200
data/distro/common/html/knife-search.1.html +0 -288
data/distro/common/html/knife-ssh.1.html +0 -156
data/distro/common/html/knife-status.1.html +0 -128
data/distro/common/html/knife-tag.1.html +0 -137
data/distro/common/html/knife.1.html +0 -320
data/distro/common/html/shef.1.html +0 -283
data/distro/common/man/man1/knife-bootstrap.1 +0 -201
data/distro/common/man/man1/knife-client.1 +0 -99
data/distro/common/man/man1/knife-configure.1 +0 -88
data/distro/common/man/man1/knife-cookbook-site.1 +0 -145
data/distro/common/man/man1/knife-cookbook.1 +0 -345
data/distro/common/man/man1/knife-data-bag.1 +0 -136
data/distro/common/man/man1/knife-environment.1 +0 -178
data/distro/common/man/man1/knife-exec.1 +0 -46
data/distro/common/man/man1/knife-index.1 +0 -29
data/distro/common/man/man1/knife-node.1 +0 -134
data/distro/common/man/man1/knife-role.1 +0 -88
data/distro/common/man/man1/knife-search.1 +0 -280
data/distro/common/man/man1/knife-ssh.1 +0 -79
data/distro/common/man/man1/knife-status.1 +0 -29
data/distro/common/man/man1/knife-tag.1 +0 -43
data/distro/common/man/man1/knife.1 +0 -288
data/distro/common/man/man1/shef.1 +0 -256
data/distro/common/man/man8/chef-client.8 +0 -104
data/distro/common/man/man8/chef-expander.8 +0 -97
data/distro/common/man/man8/chef-expanderctl.8 +0 -62
data/distro/common/man/man8/chef-server-webui.8 +0 -155
data/distro/common/man/man8/chef-server.8 +0 -147
data/distro/common/man/man8/chef-solo.8 +0 -158
data/distro/common/man/man8/chef-solr.8 +0 -122
data/distro/common/markdown/README +0 -3
data/distro/common/markdown/man1/knife-bootstrap.mkd +0 -141
data/distro/common/markdown/man1/knife-client.mkd +0 -103
data/distro/common/markdown/man1/knife-configure.mkd +0 -70
data/distro/common/markdown/man1/knife-cookbook-site.mkd +0 -123
data/distro/common/markdown/man1/knife-cookbook.mkd +0 -263
data/distro/common/markdown/man1/knife-data-bag.mkd +0 -121
data/distro/common/markdown/man1/knife-environment.mkd +0 -151
data/distro/common/markdown/man1/knife-exec.mkd +0 -37
data/distro/common/markdown/man1/knife-index.mkd +0 -30
data/distro/common/markdown/man1/knife-node.mkd +0 -130
data/distro/common/markdown/man1/knife-role.mkd +0 -85
data/distro/common/markdown/man1/knife-search.mkd +0 -180
data/distro/common/markdown/man1/knife-ssh.mkd +0 -69
data/distro/common/markdown/man1/knife-status.mkd +0 -36
data/distro/common/markdown/man1/knife-tag.mkd +0 -39
data/distro/common/markdown/man1/knife.mkd +0 -218
data/distro/common/markdown/man1/shef.mkd +0 -189
data/distro/common/markdown/man8/chef-client.mkd +0 -74
data/distro/common/markdown/man8/chef-expander.mkd +0 -82
data/distro/common/markdown/man8/chef-expanderctl.mkd +0 -58
data/distro/common/markdown/man8/chef-server-webui.mkd +0 -121
data/distro/common/markdown/man8/chef-server.mkd +0 -121
data/distro/common/markdown/man8/chef-solo.mkd +0 -107
data/distro/common/markdown/man8/chef-solr.mkd +0 -89
data/distro/debian/etc/default/chef-client +0 -4
data/distro/debian/etc/default/chef-expander +0 -8
data/distro/debian/etc/default/chef-server +0 -9
data/distro/debian/etc/default/chef-server-webui +0 -9
data/distro/debian/etc/default/chef-solr +0 -8
data/distro/debian/etc/init.d/chef-client +0 -210
data/distro/debian/etc/init.d/chef-expander +0 -176
data/distro/debian/etc/init.d/chef-server +0 -122
data/distro/debian/etc/init.d/chef-server-webui +0 -123
data/distro/debian/etc/init.d/chef-solr +0 -176
data/distro/debian/etc/init/chef-client.conf +0 -17
data/distro/debian/etc/init/chef-expander.conf +0 -17
data/distro/debian/etc/init/chef-server-webui.conf +0 -17
data/distro/debian/etc/init/chef-server.conf +0 -17
data/distro/debian/etc/init/chef-solr.conf +0 -17
data/distro/redhat/etc/init.d/chef-client +0 -121
data/distro/redhat/etc/init.d/chef-expander +0 -104
data/distro/redhat/etc/init.d/chef-server +0 -112
data/distro/redhat/etc/init.d/chef-server-webui +0 -112
data/distro/redhat/etc/init.d/chef-solr +0 -104
data/distro/redhat/etc/logrotate.d/chef-client +0 -8
data/distro/redhat/etc/logrotate.d/chef-expander +0 -8
data/distro/redhat/etc/logrotate.d/chef-server +0 -8
data/distro/redhat/etc/logrotate.d/chef-server-webui +0 -8
data/distro/redhat/etc/logrotate.d/chef-solr +0 -8
data/distro/redhat/etc/sysconfig/chef-client +0 -15
data/distro/redhat/etc/sysconfig/chef-expander +0 -7
data/distro/redhat/etc/sysconfig/chef-server +0 -14
data/distro/redhat/etc/sysconfig/chef-server-webui +0 -14
data/distro/redhat/etc/sysconfig/chef-solr +0 -8
data/distro/windows/service_manager.rb +0 -164

data/distro/common/html/shef.1.html DELETED Viewed

@@ -1,283 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <meta http-equiv='content-type' value='text/html;charset=utf8'>
-  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
-  <title>shef(1) - Interactive Chef Console</title>
-  <style type='text/css' media='all'>
-  /* style: man */
-  body#manpage {margin:0}
-  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
-  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
-  .mp h2 {margin:10px 0 0 0}
-  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
-  .mp h3 {margin:0 0 0 4ex}
-  .mp dt {margin:0;clear:left}
-  .mp dt.flush {float:left;width:8ex}
-  .mp dd {margin:0 0 0 9ex}
-  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
-  .mp pre {margin-bottom:20px}
-  .mp pre+h2,.mp pre+h3 {margin-top:22px}
-  .mp h2+pre,.mp h3+pre {margin-top:5px}
-  .mp img {display:block;margin:auto}
-  .mp h1.man-title {display:none}
-  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
-  .mp h2 {font-size:16px;line-height:1.25}
-  .mp h1 {font-size:20px;line-height:2}
-  .mp {text-align:justify;background:#fff}
-  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
-  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
-  .mp u {text-decoration:underline}
-  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
-  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
-  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
-  .mp b.man-ref {font-weight:normal;color:#434241}
-  .mp pre {padding:0 4ex}
-  .mp pre code {font-weight:normal;color:#434241}
-  .mp h2+pre,h3+pre {padding-left:0}
-  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
-  ol.man-decor {width:100%}
-  ol.man-decor li.tl {text-align:left}
-  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
-  ol.man-decor li.tr {text-align:right;float:right}
-  </style>
-  <style type='text/css' media='all'>
-  /* style: toc */
-  .man-navigation {display:block !important;position:fixed;top:0;left:113ex;height:100%;width:100%;padding:48px 0 0 0;border-left:1px solid #dbdbdb;background:#eee}
-  .man-navigation a,.man-navigation a:hover,.man-navigation a:link,.man-navigation a:visited {display:block;margin:0;padding:5px 2px 5px 30px;color:#999;text-decoration:none}
-  .man-navigation a:hover {color:#111;text-decoration:underline}
-  </style>
-</head>
-<!--
-  The following styles are deprecated and will be removed at some point:
-  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
-  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
-  .man-navigation should be used instead.
--->
-<body id='manpage'>
-  <div class='mp' id='man'>
-  <div class='man-navigation' style='display:none'>
-    <a href="#NAME">NAME</a>
-    <a href="#SYNOPSIS">SYNOPSIS</a>
-    <a href="#DESCRIPTION">DESCRIPTION</a>
-    <a href="#SYNTAX">SYNTAX</a>
-    <a href="#PRIMARY-MODE">PRIMARY MODE</a>
-    <a href="#RECIPE-MODE">RECIPE MODE</a>
-    <a href="#EXAMPLES">EXAMPLES</a>
-    <a href="#BUGS">BUGS</a>
-    <a href="#SEE-ALSO">SEE ALSO</a>
-    <a href="#AUTHOR">AUTHOR</a>
-    <a href="#DOCUMENTATION">DOCUMENTATION</a>
-    <a href="#CHEF">CHEF</a>
-  </div>
-  <ol class='man-decor man-head man head'>
-    <li class='tl'>shef(1)</li>
-    <li class='tc'>Chef Manual</li>
-    <li class='tr'>shef(1)</li>
-  </ol>
-  <h2 id="NAME">NAME</h2>
-<p class="man-name">
-  <code>shef</code> - <span class="man-whatis">Interactive Chef Console</span>
-</p>
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-<p><strong>shef</strong> [<em>named configuration</em>] <em>(options)</em></p>
-<dl>
-<dt><code>-S</code>, <code>--server CHEF_SERVER_URL</code></dt><dd>The chef server URL</dd>
-<dt><code>-z</code>, <code>--client</code></dt><dd>chef-client mode</dd>
-<dt><code>-c</code>, <code>--config CONFIG</code></dt><dd>The configuration file to use</dd>
-<dt><code>-j</code>, <code>--json-attributes JSON_ATTRIBS</code></dt><dd>Load attributes from a JSON file or URL</dd>
-<dt><code>-l</code>, <code>--log-level LOG_LEVEL</code></dt><dd>Set the logging level</dd>
-<dt><code>-s</code>, <code>--solo</code></dt><dd>chef-solo shef session</dd>
-<dt><code>-a</code>, <code>--standalone</code></dt><dd>standalone shef session</dd>
-<dt><code>-v</code>, <code>--version</code></dt><dd>Show chef version</dd>
-<dt><code>-h</code>, <code>--help</code></dt><dd>Show command options</dd>
-</dl>
-<p>When no --config option is specified, shef attempts to load a default configuration file:</p>
-<ul>
-<li>If a <em>named configuration</em> is given, shef will load ~/.chef/<em>named
-configuration</em>/shef.rb</li>
-<li>If no <em>named configuration</em> is given shef will load ~/.chef/shef.rb if it exists</li>
-<li>Shef falls back to loading /etc/chef/client.rb or /etc/chef/solo.rb if -z or
--s options are given and no shef.rb can be found.</li>
-<li>The --config option takes precedence over implicit configuration
-paths.</li>
-</ul>
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-<p><code>shef</code> is an <span class="man-ref">irb<span class="s">(1)</span></span> (interactive ruby) session customized for Chef.
-<code>shef</code> serves two primary functions: it provides a means to
-interact with a Chef Server interactively using a convenient DSL; it
-allows you to define and run Chef recipes interactively.</p>
-<h2 id="SYNTAX">SYNTAX</h2>
-<p>Shef uses irb's subsession feature to provide multiple modes of
-interaction. In addition to the primary mode which is entered on start,
-<code>recipe</code> and <code>attributes</code> modes are available.</p>
-<h2 id="PRIMARY-MODE">PRIMARY MODE</h2>
-<p>The following commands are available in the primary
-session:</p>
-<dl>
-<dt class="flush"><code>help</code></dt><dd>Prints a list of available commands</dd>
-<dt class="flush"><code>version</code></dt><dd>Prints the Chef version</dd>
-<dt class="flush"><code>recipe</code></dt><dd>Switches to <code>recipe</code> mode</dd>
-<dt><code>attributes</code></dt><dd>Switches to <code>attributes</code> mode</dd>
-<dt><code>run_chef</code></dt><dd>Initiates a chef run</dd>
-<dt class="flush"><code>reset</code></dt><dd>reinitializes shef</dd>
-<dt><code>echo :on|:off</code></dt><dd>Turns irb's echo function on or off. Echo is <em>on</em> by default.</dd>
-<dt><code>tracing :on|:off</code></dt><dd>Turns irb's function tracing feature on or off. Tracing is extremely
-verbose and expected to be of interest primarily to developers.</dd>
-<dt class="flush"><code>node</code></dt><dd>Returns the <em>node</em> object for the current host. See <span class="man-ref">knife-node<span class="s">(1)</span></span>
-for more information about nodes.</dd>
-<dt class="flush"><code>ohai</code></dt><dd>Prints the attributes of <em>node</em></dd>
-</dl>
-<p>In addition to these commands, shef provides a DSL for accessing data on
-the Chef Server. When working with remote data in shef, you chain method
-calls in the form <em>object type</em>.<em>operation</em>, where <em>object type</em> is in
-plural form. The following object types are available:</p>
-<ul>
-<li><code>nodes</code></li>
-<li><code>roles</code></li>
-<li><code>data_bags</code></li>
-<li><code>clients</code></li>
-<li><code>cookbooks</code></li>
-</ul>
-<p>For each <em>object type</em> the following operations are available:</p>
-<dl>
-<dt><em>object type</em>.all(<em>&amp;block</em>)</dt><dd>Loads all items from the server. If the optional code <em>block</em> is
-given, each item will be passed to the block and the results
-returned, similar to ruby's <code>Enumerable#map</code> method.</dd>
-<dt><em>object type</em>.show(<em>object name</em>)</dt><dd><p>Aliased as <em>object type</em>.load</p>
-<p>Loads the singular item identified by <em>object name</em>.</p></dd>
-<dt><em>object type</em>.search(<em>query</em>, <em>&amp;block</em>)</dt><dd><p>Aliased as <em>object type</em>.find</p>
-<p>Runs a search against the server and returns the matching items. If
-the optional code <em>block</em> is given each item will be passed to the
-block and the results returned.</p>
-<p>The <em>query</em> may be a Solr/Lucene format query given as a String, or
-a Hash of conditions. If a Hash is given, the options will be ANDed
-together. To join conditions with OR, use negative queries, or any
-advanced search syntax, you must provide give the query in String
-form.</p></dd>
-<dt><em>object type</em>.transform(:all|<em>query</em>, <em>&amp;block</em>)</dt><dd><p>Aliased as <em>object type</em>.bulk_edit</p>
-<p>Bulk edit objects by processing them with the (required) code <em>block</em>.
-You can edit all objects of the given type by passing the Symbol
-<code>:all</code> as the argument, or only a subset by passing a <em>query</em> as the
-argument. The <em>query</em> is evaluated in the same way as with
-<strong>search</strong>.</p>
-<p>The return value of the code <em>block</em> is used to alter the behavior
-of <code>transform</code>. If the value returned from the block is <code>nil</code> or
-<code>false</code>, the object will not be saved. Otherwise, the object is
-saved after being passed to the block. This behavior can be
-exploited to create a dry run to test a data transformation.</p></dd>
-</dl>
-<h2 id="RECIPE-MODE">RECIPE MODE</h2>
-<p>Recipe mode implements Chef's recipe DSL. Exhaustively documenting this
-DSL is outside the scope of this document. See the following pages in
-the Chef documentation for more information:</p>
-<ul>
-<li><a data-bare-link="true" href="http://wiki.opscode.com/display/chef/Resources">http://wiki.opscode.com/display/chef/Resources</a></li>
-<li><a data-bare-link="true" href="http://wiki.opscode.com/display/chef/Recipes">http://wiki.opscode.com/display/chef/Recipes</a></li>
-</ul>
-<p>Once you have defined resources in the recipe, you can trigger a
-convergence run via <code>run_chef</code></p>
-<h2 id="EXAMPLES">EXAMPLES</h2>
-<ul>
-<li><p>A "Hello World" interactive recipe</p>
-<p>chef > recipe<br />
-chef:recipe > echo :off<br />
-chef:recipe > file "/tmp/hello_world"<br />
-chef:recipe > run_chef<br />
-[Sat, 09 Apr 2011 08:56:56 -0700] INFO: Processing file[/tmp/hello_world] action create ((irb#1) line 2)<br />
-[Sat, 09 Apr 2011 08:56:56 -0700] INFO: file[/tmp/hello_world] created file /tmp/hello_world<br />
-chef:recipe > pp ls '/tmp'<br />
-[".",<br />
-"..",<br />
-"hello_world"]</p></li>
-<li><p>Search for <em>nodes</em> by role, and print their IP addresses</p>
-<p>chef > nodes.find(:roles => 'monitoring-server') {|n| n[:ipaddress] }<br />
-=> ["10.254.199.5"]</p></li>
-<li><p>Remove the role <em>obsolete</em> from every node in the system</p>
-<p>chef > nodes.transform(:all) {|n| n.run_list.delete('role[obsolete]') }<br />
- => [node[chef098b2.opschef.com], node[ree-woot], node[graphite-dev], node[fluke.localdomain], node[ghost.local], node[kallistec]]</p></li>
-</ul>
-<h2 id="BUGS">BUGS</h2>
-<p>The name <code>shef</code> is clever in print but is confusing when spoken aloud.
-Pronouncing <code>shef</code> as <code>chef console</code> is an imperfect workaround.</p>
-<p><code>shef</code> often does not perfectly replicate the context in which
-<span class="man-ref">chef-client<span class="s">(8)</span></span> configures a host, which may lead to discrepancies in
-observed behavior.</p>
-<p><code>shef</code> has to duplicate much code from chef-client's internal libraries
-and may become out of sync with the behavior of those libraries.</p>
-<h2 id="SEE-ALSO">SEE ALSO</h2>
-<p>  <span class="man-ref">chef-client<span class="s">(8)</span></span> <span class="man-ref">knife<span class="s">(1)</span></span>
-  <a data-bare-link="true" href="http://wiki.opscode.com/display/chef/Shef">http://wiki.opscode.com/display/chef/Shef</a></p>
-<h2 id="AUTHOR">AUTHOR</h2>
-<p>   Chef was written by Adam Jacob <a data-bare-link="true" href="&#x6d;&#x61;&#x69;&#x6c;&#116;&#111;&#58;&#97;&#x64;&#97;&#x6d;&#64;&#111;&#112;&#x73;&#x63;&#x6f;&#100;&#101;&#46;&#x63;&#x6f;&#x6d;">&#97;&#x64;&#x61;&#109;&#x40;&#x6f;&#112;&#x73;&#99;&#x6f;&#100;&#101;&#x2e;&#99;&#111;&#x6d;</a> with many
-   contributions from the community. Shef was written by Daniel DeLeo.</p>
-<h2 id="DOCUMENTATION">DOCUMENTATION</h2>
-<p>   This manual page was written by Daniel DeLeo <a data-bare-link="true" href="&#x6d;&#97;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#100;&#x61;&#x6e;&#64;&#x6f;&#x70;&#x73;&#x63;&#x6f;&#x64;&#101;&#x2e;&#99;&#x6f;&#x6d;">&#x64;&#97;&#110;&#x40;&#111;&#112;&#x73;&#99;&#x6f;&#100;&#101;&#46;&#99;&#x6f;&#109;</a>.
-   Permission is granted to copy, distribute and / or modify this
-   document under the terms of the Apache 2.0 License.</p>
-<h2 id="CHEF">CHEF</h2>
-<p>   Shef is distributed with Chef. <a data-bare-link="true" href="http://wiki.opscode.com/display/chef/Home">http://wiki.opscode.com/display/chef/Home</a></p>
-  <ol class='man-decor man-foot man foot'>
-    <li class='tl'>Chef 10.16.0.rc.1</li>
-    <li class='tc'>October 2012</li>
-    <li class='tr'>shef(1)</li>
-  </ol>
-  </div>
-</body>
-</html>

data/distro/common/man/man1/knife-bootstrap.1 DELETED Viewed

@@ -1,201 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "KNIFE\-BOOTSTRAP" "1" "October 2012" "Chef 10.16.0.rc.1" "Chef Manual"
-.
-.SH "NAME"
-\fBknife\-bootstrap\fR \- Install Chef Client on a remote host
-.
-.SH "SYNOPSIS"
-\fBknife\fR \fBbootstrap\fR \fI(options)\fR
-.
-.TP
-\fB\-i\fR, \fB\-\-identity\-file IDENTITY_FILE\fR
-The SSH identity file used for authentication
-.
-.TP
-\fB\-N\fR, \fB\-\-node\-name NAME\fR
-The Chef node name for your new node
-.
-.TP
-\fB\-P\fR, \fB\-\-ssh\-password PASSWORD\fR
-The ssh password
-.
-.TP
-\fB\-x\fR, \fB\-\-ssh\-user USERNAME\fR
-The ssh username
-.
-.TP
-\fB\-p\fR, \fB\-\-ssh\-port PORT\fR
-The ssh port
-.
-.TP
-\fB\-\-bootstrap\-version VERSION\fR
-The version of Chef to install
-.
-.TP
-\fB\-\-bootstrap\-proxy PROXY_URL\fR
-\fBThe proxy server for the node being bootstrapped\fR
-.
-.TP
-\fB\-\-prerelease\fR
-Install pre\-release Chef gems
-.
-.TP
-\fB\-r\fR, \fB\-\-run\-list RUN_LIST\fR
-Comma separated list of roles/recipes to apply
-.
-.TP
-\fB\-\-template\-file TEMPLATE\fR
-Full path to location of template to use
-.
-.TP
-\fB\-\-sudo\fR
-Execute the bootstrap via sudo
-.
-.TP
-\fB\-d\fR, \fB\-\-distro DISTRO\fR
-Bootstrap a distro using a template
-.
-.TP
-\fB\-\-[no\-]host\-key\-verify\fR
-Enable host key verification, which is the default behavior\.
-.
-.TP
-\fB\-\-hint HINT_NAME[=HINT_FILE]\fR
-Provide the name of a hint (with option JSON file) to set for use by Ohai plugins\.
-.
-.SH "DESCRIPTION"
-Performs a Chef Bootstrap on the target node\. The goal of the bootstrap is to get Chef installed on the target system so it can run Chef Client with a Chef Server\. The main assumption is a baseline OS installation exists\. This sub\-command is used internally by some cloud computing plugins\.
-.
-.P
-The bootstrap sub\-command supports supplying a template to perform the bootstrap steps\. If the distro is not specified (via \fB\-d\fR or \fB\-\-distro\fR option), an Ubuntu 10\.04 host bootstrapped with RubyGems is assumed\. The \fBDISTRO\fR value corresponds to the base filename of the template, in other words \fBDISTRO\fR\.erb\. A template file can be specified with the \fB\-\-template\-file\fR option in which case the \fBDISTRO\fR is not used\. The sub\-command looks in the following locations for the template to use:
-.
-.IP "\(bu" 4
-\fBbootstrap\fR directory in the installed Chef Knife library\.
-.
-.IP "\(bu" 4
-\fBbootstrap\fR directory in the \fB$PWD/\.chef\fR\.
-.
-.IP "\(bu" 4
-\fBbootstrap\fR directory in the users \fB$HOME/\.chef\fR\.
-.
-.IP "" 0
-.
-.P
-The default bootstrap templates are scripts that get copied to the target node (FQDN)\. The following distros are supported:
-.
-.IP "\(bu" 4
-centos5\-gems
-.
-.IP "\(bu" 4
-fedora13\-gems
-.
-.IP "\(bu" 4
-ubuntu10\.04\-gems
-.
-.IP "\(bu" 4
-ubuntu10\.04\-apt
-.
-.IP "" 0
-.
-.P
-The gems installations will use RubyGems 1\.3\.6 and Chef installed as a gem\. The apt installation will use the Opscode APT repository\.
-.
-.P
-In addition to handling the software installation, these bootstrap templates do the following:
-.
-.IP "\(bu" 4
-Write the validation\.pem per the local knife configuration\.
-.
-.IP "\(bu" 4
-Write a default config file for Chef (\fB/etc/chef/client\.rb\fR) using values from the \fBknife\.rb\fR\.
-.
-.IP "\(bu" 4
-Create a JSON attributes file containing the specified run list and run Chef\.
-.
-.IP "" 0
-.
-.P
-In the case of the RubyGems, the \fBclient\.rb\fR will be written from scratch with a minimal set of values; see \fBEXAMPLES\fR\. In the case of APT Package installation, \fBclient\.rb\fR will have the \fBvalidation_client_name\fR appended if it is not set to \fBchef\-validator\fR (default config value), and the \fBnode_name\fR will be added if \fBchef_node_name\fR option is specified\.
-.
-.P
-When this is complete, the bootstrapped node will have:
-.
-.IP "\(bu" 4
-Latest Chef version installed from RubyGems or APT Packages from Opscode\. This may be a later version than the local system\.
-.
-.IP "\(bu" 4
-Be validated with the configured Chef Server\.
-.
-.IP "\(bu" 4
-Have run Chef with its default run list if one is specfied\.
-.
-.IP "" 0
-.
-.P
-Additional custom bootstrap templates can be created and stored in \fB\.chef/bootstrap/DISTRO\.erb\fR, replacing \fBDISTRO\fR with the value passed with the \fB\-d\fR or \fB\-\-distro\fR option\. See \fBEXAMPLES\fR for more information\.
-.
-.SH "EXAMPLES"
-Setting up a custom bootstrap is fairly straightforward\. Create a \fB\.chef/bootstrap\fR directory in your Chef Repository or in \fB$HOME/\.chef/bootstrap\fR\. Then create the ERB template file\.
-.
-.IP "" 4
-.
-.nf
-mkdir ~/\.chef/bootstrap
-vi ~/\.chef/bootstrap/debian5\.0\-apt\.erb
-.
-.fi
-.
-.IP "" 0
-.
-.P
-For example, to create a new bootstrap template that should be used when setting up a new Debian node\. Edit the template to run the commands, set up the validation certificate and the client configuration file, and finally to run chef\-client on completion\. The bootstrap template can be called with:
-.
-.IP "" 4
-.
-.nf
-knife bootstrap mynode\.example\.com \-\-template\-file ~/\.chef/bootstrap/debian5\.0\-apt\.erb
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Or,
-.
-.IP "" 4
-.
-.nf
-knife bootstrap mynode\.example\.com \-\-distro debian5\.0\-apt
-.
-.fi
-.
-.IP "" 0
-.
-.P
-The \fB\-\-distro\fR parameter will automatically look in the \fB~/\.chef/bootstrap\fR directory for a file named \fBdebian5\.0\-apt\.erb\fR\.
-.
-.P
-Templates provided by the Chef installation are located in \fBBASEDIR/lib/chef/knife/bootstrap/*\.erb\fR, where \fIBASEDIR\fR is the location where the package or Gem installed the Chef client libraries\.
-.
-.SH "BUGS"
-\fBknife bootstrap\fR is not capable of bootstrapping multiple hosts in parallel\.
-.
-.P
-The bootstrap script is passed as an argument to sh(1) on the remote system, so sensitive information contained in the script will be visible to other users via the process list using tools such as ps(1)\.
-.
-.SH "SEE ALSO"
-\fBknife\-ssh\fR(1)
-.
-.SH "AUTHOR"
-Chef was written by Adam Jacob \fIadam@opscode\.com\fR with many contributions from the community\.
-.
-.SH "DOCUMENTATION"
-This manual page was written by Joshua Timberman \fIjoshua@opscode\.com\fR\. Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2\.0 License\.
-.
-.SH "CHEF"
-Knife is distributed with Chef\. \fIhttp://wiki\.opscode\.com/display/chef/Home\fR