diff options
| author | scottb <sydtech@gmail.com> | 2016-10-26 17:37:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-26 17:37:42 -0700 |
| commit | c47d580743e50c6e7cdfbb304d8378af41f56c7d (patch) | |
| tree | 02fa55252a95f6aa68a0bc275b9f8e4f6b5502f0 | |
| parent | c683d01c0089d86103e848f72ce9bea3dc1f38d2 (diff) | |
| parent | 6dad0124e962ea7b5f6cb2342ada5accca687cd4 (diff) | |
| download | ansible-c47d580743e50c6e7cdfbb304d8378af41f56c7d.tar.gz | |
Merge pull request #11075 from initcron/devel
corrected the playbook name from rolling_upgrade.yml to rolling_updat…
| -rw-r--r-- | docsite/rst/guide_rolling_upgrade.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docsite/rst/guide_rolling_upgrade.rst b/docsite/rst/guide_rolling_upgrade.rst index 521429e0c1..c5dfcd206c 100644 --- a/docsite/rst/guide_rolling_upgrade.rst +++ b/docsite/rst/guide_rolling_upgrade.rst @@ -186,7 +186,7 @@ Now you have a fully-deployed site with web servers, a load balancer, and monito orchestration features come into play. While some applications use the term 'orchestration' to mean basic ordering or command-blasting, Ansible refers to orchestration as 'conducting machines like an orchestra', and has a pretty sophisticated engine for it. -Ansible has the capability to do operations on multi-tier applications in a coordinated way, making it easy to orchestrate a sophisticated zero-downtime rolling upgrade of our web application. This is implemented in a separate playbook, called ``rolling_upgrade.yml``. +Ansible has the capability to do operations on multi-tier applications in a coordinated way, making it easy to orchestrate a sophisticated zero-downtime rolling upgrade of our web application. This is implemented in a separate playbook, called ``rolling_update.yml``. Looking at the playbook, you can see it is made up of two plays. The first play is very simple and looks like this:: |