Fix some example command line options, add some more links to home page.

This commit is contained in:
Michael DeHaan 2012-03-11 21:46:05 -04:00
parent 817cac7954
commit e726b9796d
7 changed files with 17 additions and 17 deletions

View file

@ -209,7 +209,7 @@ is commonly referred to as &#8216;idempotent&#8217;.</p>
<p>Ansible can SCP lots of files to multiple machines in parallel, and <p>Ansible can SCP lots of files to multiple machines in parallel, and
optionally use them as template sources.</p> optionally use them as template sources.</p>
<p>To just transfer a file directly to many different servers:</p> <p>To just transfer a file directly to many different servers:</p>
<div class="highlight-python"><pre>ansible atlanta copy -a "/etc/hosts /tmp/hosts"</pre> <div class="highlight-python"><pre>ansible atlanta -m copy -a "/etc/hosts /tmp/hosts"</pre>
</div> </div>
<p>To use templating, first run the setup module to put the template <p>To use templating, first run the setup module to put the template
variables you would like to use on the remote host. Then use the variables you would like to use on the remote host. Then use the
@ -274,7 +274,7 @@ to poll, it looks like this:</p>
<div class="highlight-python"><pre>ansible all -B 3600 -a "/usr/bin/long_running_operation --do-stuff"</pre> <div class="highlight-python"><pre>ansible all -B 3600 -a "/usr/bin/long_running_operation --do-stuff"</pre>
</div> </div>
<p>If you do decide you want to check on the job status later, you can:</p> <p>If you do decide you want to check on the job status later, you can:</p>
<div class="highlight-python"><pre>ansible all -n job_status -a jid=123456789</pre> <div class="highlight-python"><pre>ansible all -m async_status -a "jid=123456789"</pre>
</div> </div>
<p>Polling is built-in and looks like this:</p> <p>Polling is built-in and looks like this:</p>
<div class="highlight-python"><pre>ansible all -B 3600 -P 60 -a "/usr/bin/long_running_operation --do-stuff"</pre> <div class="highlight-python"><pre>ansible all -B 3600 -P 60 -a "/usr/bin/long_running_operation --do-stuff"</pre>

View file

@ -183,12 +183,12 @@ much learning curve. Ansible is dead simple and painless to extend.
For comparison, Puppet and Chef have about 60k lines of code. For comparison, Puppet and Chef have about 60k lines of code.
Ansible&#8217;s core is a little over 1000 lines.</p> Ansible&#8217;s core is a little over 1000 lines.</p>
<p>Ansible isn&#8217;t just for configuration &#8211; it&#8217;s also great for Ad-Hoc <p>Ansible isn&#8217;t just for configuration &#8211; it&#8217;s also great for Ad-Hoc
tasks, quickly firing off commands against nodes. Where Ansible tasks, quickly firing off commands against nodes. See <a class="reference internal" href="examples.html"><em>Command Line Examples</em></a>.
excels though, is expressing complex multi-node deployment processes, Where Ansible excels though, is expressing complex multi-node
executing complex sequences of commands on different hosts through deployment processes, executing complex sequences of commands on
<a class="reference internal" href="playbooks.html"><em>Playbooks</em></a>.</p> different hosts through <a class="reference internal" href="playbooks.html"><em>Playbooks</em></a>.</p>
<p>Extending ansible does not require programming in any particular <p>Extending ansible does not require programming in any particular
language &#8211; you can write modules as scripts or programs that return language &#8211; you can write <a class="reference internal" href="modules.html"><em>Ansible Modules</em></a> as scripts or programs that return
simple JSON. It&#8217;s also trivially easy to just execute useful shell simple JSON. It&#8217;s also trivially easy to just execute useful shell
commands.</p> commands.</p>
<p>Why use Ansible versus something else? (Puppet, Chef, Fabric, <p>Why use Ansible versus something else? (Puppet, Chef, Fabric,

View file

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible-playbook</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible-playbook" lang="en"><a id="id365972"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible-playbook — run an ansible playbook</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible-playbook &lt;filename.yml&gt; … [options]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible playbooks</strong></span> are a configuration and multinode deployment system. Ansible-playbook is the tool <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible-playbook</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible-playbook" lang="en"><a id="id490422"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible-playbook — run an ansible playbook</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible-playbook &lt;filename.yml&gt; … [options]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible playbooks</strong></span> are a configuration and multinode deployment system. Ansible-playbook is the tool
used to run them. See the project home page (link below) for more information.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term"> used to run them. See the project home page (link below) for more information.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term">
<span class="strong"><strong>filename.yml</strong></span> <span class="strong"><strong>filename.yml</strong></span>
</span></dt><dd> </span></dt><dd>

View file

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible" lang="en"><a id="id471818"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible — run a command somewhere else</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible &lt;host-pattern&gt; [-f forks] [-m module_name] [-a args]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible</strong></span> is an extra-simple tool/framework/API for doing 'remote things' over <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>ansible</title><link rel="stylesheet" href="./docbook-xsl.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div xml:lang="en" class="refentry" title="ansible" lang="en"><a id="id531620"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ansible — run a command somewhere else</p></div><div class="refsynopsisdiv" title="Synopsis"><a id="_synopsis"></a><h2>Synopsis</h2><p>ansible &lt;host-pattern&gt; [-f forks] [-m module_name] [-a args]</p></div><div class="refsect1" title="DESCRIPTION"><a id="_description"></a><h2>DESCRIPTION</h2><p><span class="strong"><strong>Ansible</strong></span> is an extra-simple tool/framework/API for doing 'remote things' over
SSH.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term"> SSH.</p></div><div class="refsect1" title="ARGUMENTS"><a id="_arguments"></a><h2>ARGUMENTS</h2><div class="variablelist"><dl><dt><span class="term">
<span class="strong"><strong>host-pattern</strong></span> <span class="strong"><strong>host-pattern</strong></span>
</span></dt><dd> </span></dt><dd>

View file

@ -40,7 +40,7 @@ optionally use them as template sources.
To just transfer a file directly to many different servers:: To just transfer a file directly to many different servers::
ansible atlanta copy -a "/etc/hosts /tmp/hosts" ansible atlanta -m copy -a "/etc/hosts /tmp/hosts"
To use templating, first run the setup module to put the template To use templating, first run the setup module to put the template
variables you would like to use on the remote host. Then use the variables you would like to use on the remote host. Then use the
@ -119,7 +119,7 @@ to poll, it looks like this::
If you do decide you want to check on the job status later, you can:: If you do decide you want to check on the job status later, you can::
ansible all -n job_status -a jid=123456789 ansible all -m async_status -a "jid=123456789"
Polling is built-in and looks like this:: Polling is built-in and looks like this::

View file

@ -25,13 +25,13 @@ For comparison, Puppet and Chef have about 60k lines of code.
Ansible's core is a little over 1000 lines. Ansible's core is a little over 1000 lines.
Ansible isn't just for configuration -- it's also great for Ad-Hoc Ansible isn't just for configuration -- it's also great for Ad-Hoc
tasks, quickly firing off commands against nodes. Where Ansible tasks, quickly firing off commands against nodes. See :doc:`examples`.
excels though, is expressing complex multi-node deployment processes, Where Ansible excels though, is expressing complex multi-node
executing complex sequences of commands on different hosts through deployment processes, executing complex sequences of commands on
:doc:`playbooks`. different hosts through :doc:`playbooks`.
Extending ansible does not require programming in any particular Extending ansible does not require programming in any particular
language -- you can write modules as scripts or programs that return language -- you can write :doc:`modules` as scripts or programs that return
simple JSON. It's also trivially easy to just execute useful shell simple JSON. It's also trivially easy to just execute useful shell
commands. commands.

File diff suppressed because one or more lines are too long