@@ -201,6 +201,9 @@ more plays, each executed against a different batch of nodes. Think about
...
@@ -201,6 +201,9 @@ more plays, each executed against a different batch of nodes. Think about
webservers, database servers, and backend servers in a multi-node web environment. A play can address each set of machines in a cycle, ensuring the configurations of the machines were correct and also updating them to the specified
webservers, database servers, and backend servers in a multi-node web environment. A play can address each set of machines in a cycle, ensuring the configurations of the machines were correct and also updating them to the specified
version of software if required.</p>
version of software if required.</p>
<p>Multi-machine software deployment is poorly solved by most systems management tools – often due to architectural nature of being pull oriented and having complex ordering systems, they cover configuration but fail at deployment when updating tiers of machines in well defined steps. This results in using two (or more) logically distinct tools and having complex overlap between them.</p>
<p>Multi-machine software deployment is poorly solved by most systems management tools – often due to architectural nature of being pull oriented and having complex ordering systems, they cover configuration but fail at deployment when updating tiers of machines in well defined steps. This results in using two (or more) logically distinct tools and having complex overlap between them.</p>
<p>If you actually do need pull oriented mode, though, Ansible 0.4 and later can run playbooks in pull mode as well.
This is useful in extreme scaling scenarios or when automatic system remediation is desired. Since Ansible remains
server and daemonless, scaling potential is unlimited, and no resources are wasted on running management daemons.</p>
@@ -362,19 +362,19 @@ All parameters available to the file module are also available when running the
...
@@ -362,19 +362,19 @@ All parameters available to the file module are also available when running the
</ul>
</ul>
<p><em>seuser</em>:</p>
<p><em>seuser</em>:</p>
<ulclass="simple">
<ulclass="simple">
<li>‘user’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present.</li>
<li>‘user’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present. If you specify ‘_default’, it will use the ‘user’ portion of default context from the policy if available.</li>
</ul>
</ul>
<p><em>serole</em>:</p>
<p><em>serole</em>:</p>
<ulclass="simple">
<ulclass="simple">
<li>‘role’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present.</li>
<li>‘role’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present. If you specify ‘_default’, it will use the ‘role’ portion of default context from the policy if available.</li>
</ul>
</ul>
<p><em>setype</em>:</p>
<p><em>setype</em>:</p>
<ulclass="simple">
<ulclass="simple">
<li>‘type’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present.</li>
<li>‘type’ part of SELinux file context. Will default to what is provided by system policy, if available. Only used on systems with SELinux present. If you specify ‘_default’, it will use the ‘type’ portion of default context from the policy if available.</li>
</ul>
</ul>
<p><em>selevel</em>:</p>
<p><em>selevel</em>:</p>
<ulclass="simple">
<ulclass="simple">
<li>‘level’ part of SELinux file context. This is the MLS and MCS attribute of the file context. It defaults to ‘s0’. Only used only used on hosts with SELinux present.</li>
<li>‘level’ part of SELinux file context. This is the MLS and MCS attribute of the file context, also sometimes known as the ‘range’. It defaults to ‘s0’. Only used only used on hosts with SELinux present. If you specify ‘_default’, it will use the ‘level’ portion of default context from the policy if available.</li>
</ul>
</ul>
<p><em>context</em>:</p>
<p><em>context</em>:</p>
<ulclass="simple">
<ulclass="simple">
...
@@ -610,6 +610,10 @@ be a relative or absolute path.</li>
...
@@ -610,6 +610,10 @@ be a relative or absolute path.</li>
<ulclass="simple">
<ulclass="simple">
<li>Optionally sets the description of the user</li>
<li>Optionally sets the description of the user</li>
</ul>
</ul>
<p><em>uid</em>:</p>
<ulclass="simple">
<li>optional uid to set for the user</li>
</ul>
<p><em>group</em>:</p>
<p><em>group</em>:</p>
<ulclass="simple">
<ulclass="simple">
<li>Optionally sets the user’s primary group, takes a group name.</li>
<li>Optionally sets the user’s primary group, takes a group name.</li>
