From 6dad0124e962ea7b5f6cb2342ada5accca687cd4 Mon Sep 17 00:00:00 2001 From: Gourav Shah Date: Wed, 27 May 2015 09:47:52 +0530 Subject: [PATCH] corrected the playbook name from rolling_upgrade.yml to rolling_update.yml as per example playbook --- docsite/rst/guide_rolling_upgrade.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/guide_rolling_upgrade.rst b/docsite/rst/guide_rolling_upgrade.rst index c1b66b5c42a..405610d2309 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::