Update facter/ohai parts to talk about ansible facts in most recent release

This commit is contained in:
Michael DeHaan
2012-04-25 22:46:00 -04:00
parent eba1340542
commit d6368ab4fa
5 changed files with 28 additions and 23 deletions

View File

@@ -240,8 +240,8 @@ other systems that depend on that system.</p>
does not create its own programming language. What constructs Ansible does have should be enough to cover 80% or so of the cases of most Puppet users, and it should scale equally well (not having a server is
almost like cheating).</p>
<p>Ansible does support gathering variables from &#8216;facter&#8217;, if installed, and Ansible templates
in jinja2 in a way just like Puppet does with erb. Ansible in version 0.3 will has it&#8217;s own facts,
however, so it will not need to rely on facter, but can use it if available.</p>
in jinja2 in a way just like Puppet does with erb. Ansible also has it&#8217;s own facts though,
so usage of facter is not required to get variables about the system.</p>
</div>
<div class="section" id="vs-chef">
<h3>vs Chef?<a class="headerlink" href="#vs-chef" title="Permalink to this headline"></a></h3>
@@ -261,9 +261,8 @@ Chef and Puppet are around 60k+ lines of code, while Ansible is a much simpler
program. I believe this strongly leads to more reliable software and a richer
open source community &#8211; the code is kept simple so it is easy for anyone to
submit a patch or module.</p>
<p>Ansible does support gathering variables from &#8216;ohai&#8217;, if installed. As of release
0.3, Ansible will also have it&#8217;s own facts system so you will not need to use ohai
or facter (or have a dependency on Ruby).</p>
<p>Ansible does support gathering variables from &#8216;ohai&#8217;, if installed. Ansible also
has it&#8217;s own facts so you do not need to use ohai unless you want to.</p>
</div>
<div class="section" id="vs-capistrano-fabric">
<h3>vs Capistrano/Fabric?<a class="headerlink" href="#vs-capistrano-fabric" title="Permalink to this headline"></a></h3>