1af7c6c003
* Feature freeze date has been merged with Ansible-2.10.0beta1 (#71494) (cherry picked from commitc586d436fa
) * Add --allow-disabled to sanity docs (#71524) (cherry picked from commitbc6461432e
) * Update intro_patterns.rst (#71542) Call out the trailing comma when specifying a single host. Small snag that took me a while to notice. (cherry picked from commitec3920cef1
) * ansible-vault: Fix typo in help message (#71485) (cherry picked from commit215eb730e1
) * update install for 2.10 (#71543) * update install for 2.10 (cherry picked from commitf75223d2c6
) * User guide overhaul, Table of Contents (#71553) (cherry picked from commitb694dbadfe
) * update backport instructions for 2.11 (#71567) * update backport instructions in docs/docsite/rst/community/development_process.rst Co-authored-by: Matt Martz <matt@sivel.net> (cherry picked from commit7f9258b024
) * More docs updates to reflect collections ecosystem (#71597) (cherry picked from commit96aee766f4
) * DOCS: Mentions ansible-base, adds collections pointers to Community and Dev Guides (#71480) (cherry picked from commit29b20bd1b1
) Co-authored-by: Toshio Kuratomi <a.badger@gmail.com> Co-authored-by: Amin Vakil <info@aminvakil.com> Co-authored-by: Matt Deacalion <matt@dirtymonkey.co.uk> Co-authored-by: Fabien Malfoy <fabien.malfoy@laposte.net> Co-authored-by: Alicia Cozine <879121+acozine@users.noreply.github.com>
21 lines
1.3 KiB
ReStructuredText
21 lines
1.3 KiB
ReStructuredText
.. _working_with_playbooks:
|
|
|
|
Working with playbooks
|
|
======================
|
|
|
|
Playbooks record and execute Ansible's configuration, deployment, and orchestration functions. They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process.
|
|
|
|
If Ansible modules are the tools in your workshop, playbooks are your instruction manuals, and your inventory of hosts are your raw material.
|
|
|
|
At a basic level, playbooks can be used to manage configurations of and deployments to remote machines. At a more advanced level, they can sequence multi-tier rollouts involving rolling updates, and can delegate actions to other hosts, interacting with monitoring servers and load balancers along the way.
|
|
|
|
Playbooks are designed to be human-readable and are developed in a basic text language. There are multiple ways to organize playbooks and the files they include, and we'll offer up some suggestions on that and making the most out of Ansible.
|
|
|
|
You should look at `Example Playbooks <https://github.com/ansible/ansible-examples>`_ while reading along with the playbook documentation. These illustrate best practices as well as how to put many of the various concepts together.
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
playbooks_templating
|
|
playbooks_special_topics
|
|
guide_rolling_upgrade
|