@@ -286,7 +286,7 @@ for heterogeneous distributions. While lots of software packages
claim to make this easy on you, the configuration files are often
quite different, to the point where it would be easier to treat them
as different playbooks. This is why, for example, Ansible has a
separate <aclass="reference internal"href="modules.html#yum"><em>yum</em></a> and <aclass="reference internal"href="modules.html#apt"><em>apt</em></a> module. Yum and apt have different
separate ‘yum’ and ‘apt’ module. Yum and apt have different
capabilities, and we don’t want to code for the least common
denominator.</p>
<p>Use variables for user tunable settings versus having constants in the
<p>Ok, so those are basics. If you didn’t read about patterns and groups yet, go back and read <aclass="reference internal"href="patterns.html"><em>Inventory & Patterns</em></a>.</p>
<p>The <ttclass="docutils literal"><spanclass="pre">-f</span><spanclass="pre">10</span></tt> in the above specifies the usage of 10 simultaneous
processes. Normally commands also take a <ttclass="docutils literal"><spanclass="pre">-m</span></tt> for module name, but
the default module name is <aclass="reference internal"href="modules.html#command"><em>command</em></a>, so we didn’t need to
the default module name is ‘command’, so we didn’t need to
specify that all of the time. We’ll use <ttclass="docutils literal"><spanclass="pre">-m</span></tt> in later examples to
run some other <aclass="reference internal"href="modules.html"><em>Ansible Modules</em></a>.</p>
<divclass="admonition note">
...
...
@@ -299,7 +299,7 @@ same options can be passed directly to the <tt class="docutils literal"><span cl
<divclass="section"id="managing-packages">
<h2><aclass="toc-backref"href="#contents">Managing Packages</a><aclass="headerlink"href="#managing-packages"title="Permalink to this headline">¶</a></h2>
<p>There are modules available for yum and apt. Here are some examples
with <aclass="reference internal"href="modules.html#yum"><em>yum</em></a>.</p>
with yum.</p>
<p>Ensure a package is installed, but don’t update it:</p>
<divclass="highlight-bash"><divclass="highlight"><pre><spanclass="nv">$ </span>ansible webservers -m yum -a <spanclass="s2">"pkg=acme state=installed"</span>
</pre></div>
...
...
@@ -322,7 +322,7 @@ for other package managers. Stop by the mailing list for info/details.</p>
</div>
<divclass="section"id="users-and-groups">
<h2><aclass="toc-backref"href="#contents">Users and Groups</a><aclass="headerlink"href="#users-and-groups"title="Permalink to this headline">¶</a></h2>
<p>The <aclass="reference internal"href="modules.html#user"><em>user</em></a> module allows easy creation and manipulation of
<p>The ‘user’ module allows easy creation and manipulation of
existing user accounts, as well as removal of user accounts that may
exist:</p>
<divclass="highlight-bash"><divclass="highlight"><pre><spanclass="nv">$ </span>ansible all -m user -a <spanclass="s2">"name=foo password=<crypted password here>"</span>
@@ -321,7 +321,7 @@ who which to use more advanced templating. This is optional and the $varname fo
files.</p>
<p>If there are discovered variables about the system, called ‘facts’, these variables bubble up back into the
playbook, and can be used on each system just like explicitly set variables. Ansible provides several
of these, prefixed with ‘ansible’, and are documented under <aclass="reference internal"href="modules.html#setup"><em>setup</em></a> in the module documentation. Additionally,
of these, prefixed with ‘ansible’, and are documented under ‘setup’ in the module documentation. Additionally,
facts can be gathered by ohai and facter if they are installed. Facter variables are prefixed with <ttclass="docutils literal"><spanclass="pre">facter_</span></tt> and Ohai
variables are prefixed with <ttclass="docutils literal"><spanclass="pre">ohai_</span></tt>.</p>