Docs rebuild
This commit is contained in:
parent
139a1324e9
commit
16c4802476
13 changed files with 24 additions and 17 deletions
|
@ -273,7 +273,7 @@ languages:
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
2
api.html
2
api.html
|
@ -357,7 +357,7 @@ a conf.d file appropriately or something similar. Who knows.</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -372,7 +372,7 @@ a simplified syntax for this.</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
2
faq.html
2
faq.html
|
@ -379,7 +379,7 @@ tasks – whether for a QA sytem, build system, or anything you can think of
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -188,7 +188,7 @@ s.parentNode.insertBefore(ga, s);
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -341,7 +341,7 @@ explore, but you already have a fully working infrastructure!</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -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
|
||||
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>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>
|
||||
</div>
|
||||
<div class="section" id="deployment-and-configuration-unified">
|
||||
<h1>Deployment and Configuration, Unified<a class="headerlink" href="#deployment-and-configuration-unified" title="Permalink to this headline">¶</a></h1>
|
||||
|
@ -427,7 +430,7 @@ Puppet Labs, and is now with <a class="reference external" href="http://rpath.co
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -428,7 +428,7 @@ Stop by the mailing list to inquire about requirements.</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
14
modules.html
14
modules.html
|
@ -362,19 +362,19 @@ All parameters available to the file module are also available when running the
|
|||
</ul>
|
||||
<p><em>seuser</em>:</p>
|
||||
<ul class="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>
|
||||
<p><em>serole</em>:</p>
|
||||
<ul class="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>
|
||||
<p><em>setype</em>:</p>
|
||||
<ul class="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>
|
||||
<p><em>selevel</em>:</p>
|
||||
<ul class="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>
|
||||
<p><em>context</em>:</p>
|
||||
<ul class="simple">
|
||||
|
@ -610,6 +610,10 @@ be a relative or absolute path.</li>
|
|||
<ul class="simple">
|
||||
<li>Optionally sets the description of the user</li>
|
||||
</ul>
|
||||
<p><em>uid</em>:</p>
|
||||
<ul class="simple">
|
||||
<li>optional uid to set for the user</li>
|
||||
</ul>
|
||||
<p><em>group</em>:</p>
|
||||
<ul class="simple">
|
||||
<li>Optionally sets the user’s primary group, takes a group name.</li>
|
||||
|
@ -750,7 +754,7 @@ yum pkg=httpd state=installed</pre>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -321,7 +321,7 @@ groups. This behavior may be refined in future releases.</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -710,7 +710,7 @@ Let’s run a playbook using a parallelism level of 10:</p>
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
|
@ -205,7 +205,7 @@ s.parentNode.insertBefore(ga, s);
|
|||
</p>
|
||||
<p>
|
||||
© Copyright 2012 Michael DeHaan.<br/>
|
||||
Last updated on Apr 28, 2012.<br/>
|
||||
Last updated on May 02, 2012.<br/>
|
||||
</p>
|
||||
</div>
|
||||
</footer>
|
||||
|
|
File diff suppressed because one or more lines are too long
Loading…
Reference in a new issue