Make additional reference to playbooks examples dir
This commit is contained in:
parent
a4c23463fb
commit
bbc2aca10f
5 changed files with 23 additions and 17 deletions
|
@ -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="id503630"></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 <filename.yml> … [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="id522232"></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 <filename.yml> … [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>
|
||||||
|
|
|
@ -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="id302414"></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 <host-pattern> [-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="id477142"></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 <host-pattern> [-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>
|
||||||
|
|
|
@ -174,17 +174,21 @@ s.parentNode.insertBefore(ga, s);
|
||||||
<div class="section" id="playbooks">
|
<div class="section" id="playbooks">
|
||||||
<h1>Playbooks<a class="headerlink" href="#playbooks" title="Permalink to this headline">¶</a></h1>
|
<h1>Playbooks<a class="headerlink" href="#playbooks" title="Permalink to this headline">¶</a></h1>
|
||||||
<p>Playbooks are a completely different way to use ansible and are
|
<p>Playbooks are a completely different way to use ansible and are
|
||||||
particularly awesome.</p>
|
particularly awesome. They are the basis for a really simple
|
||||||
<p>They are the basis for a really simple configuration management and
|
configuration management and multi-machine deployment system,
|
||||||
multi-machine deployment system, unlike any that already exist, and
|
unlike any that already exist, and
|
||||||
one that is very well suited to deploying complex applications.</p>
|
one that is very well suited to deploying complex applications.</p>
|
||||||
<p>Playbooks can declare configurations, or they can automate steps of
|
<p>Playbooks can declare configurations, but they can also orchestrate steps of
|
||||||
a manual ordered process. They can launch tasks synchronously or asynchronously.</p>
|
any manual ordered process, even as different steps must bounce back and forth
|
||||||
|
between sets of machines in particular orders. They can launch tasks
|
||||||
|
synchronously or asynchronously.</p>
|
||||||
<p>While you might run the main /usr/bin/ansible program for ad-hoc
|
<p>While you might run the main /usr/bin/ansible program for ad-hoc
|
||||||
tasks, playbooks are more likely to be kept in source control and used
|
tasks, playbooks are more likely to be kept in source control and used
|
||||||
to push out your configuration or assure the configurations of your
|
to push out your configuration or assure the configurations of your
|
||||||
remote systems are in spec.</p>
|
remote systems are in spec.</p>
|
||||||
<p>Let’s dive in and see how they work.</p>
|
<p>Let’s dive in and see how they work. As you go, you may wish to open
|
||||||
|
the <a class="reference external" href="https://github.com/ansible/ansible/tree/master/examples/playbooks">github examples directory</a> in
|
||||||
|
another tab, so you can apply the theory to what things look like in practice.</p>
|
||||||
<div class="section" id="playbook-example">
|
<div class="section" id="playbook-example">
|
||||||
<h2>Playbook Example<a class="headerlink" href="#playbook-example" title="Permalink to this headline">¶</a></h2>
|
<h2>Playbook Example<a class="headerlink" href="#playbook-example" title="Permalink to this headline">¶</a></h2>
|
||||||
<p>Playbooks are expressed in YAML format and have a minimum of syntax.
|
<p>Playbooks are expressed in YAML format and have a minimum of syntax.
|
||||||
|
|
|
@ -2,22 +2,24 @@ Playbooks
|
||||||
=========
|
=========
|
||||||
|
|
||||||
Playbooks are a completely different way to use ansible and are
|
Playbooks are a completely different way to use ansible and are
|
||||||
particularly awesome.
|
particularly awesome. They are the basis for a really simple
|
||||||
|
configuration management and multi-machine deployment system,
|
||||||
They are the basis for a really simple configuration management and
|
unlike any that already exist, and
|
||||||
multi-machine deployment system, unlike any that already exist, and
|
|
||||||
one that is very well suited to deploying complex applications.
|
one that is very well suited to deploying complex applications.
|
||||||
|
|
||||||
Playbooks can declare configurations, or they can automate steps of
|
Playbooks can declare configurations, but they can also orchestrate steps of
|
||||||
a manual ordered process. They can launch tasks synchronously or asynchronously.
|
any manual ordered process, even as different steps must bounce back and forth
|
||||||
|
between sets of machines in particular orders. They can launch tasks
|
||||||
|
synchronously or asynchronously.
|
||||||
|
|
||||||
While you might run the main /usr/bin/ansible program for ad-hoc
|
While you might run the main /usr/bin/ansible program for ad-hoc
|
||||||
tasks, playbooks are more likely to be kept in source control and used
|
tasks, playbooks are more likely to be kept in source control and used
|
||||||
to push out your configuration or assure the configurations of your
|
to push out your configuration or assure the configurations of your
|
||||||
remote systems are in spec.
|
remote systems are in spec.
|
||||||
|
|
||||||
Let's dive in and see how they work.
|
Let's dive in and see how they work. As you go, you may wish to open
|
||||||
|
the `github examples directory <https://github.com/ansible/ansible/tree/master/examples/playbooks>`_ in
|
||||||
|
another tab, so you can apply the theory to what things look like in practice.
|
||||||
|
|
||||||
Playbook Example
|
Playbook Example
|
||||||
````````````````
|
````````````````
|
||||||
|
|
File diff suppressed because one or more lines are too long
Loading…
Reference in a new issue