From 38e846e542a93b11034557d7bff9fbebe30f010b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Han?= Date: Mon, 21 Nov 2016 11:29:05 +0100 Subject: [PATCH] rolling_update: clarify "serial" usage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Prior to this commit the serial variable was poorly documented. Now we are making clear that this value should be left untouched as the rolling update mechanism should happen serially. Solves: bz-1396742 Signed-off-by: Sébastien Han --- infrastructure-playbooks/rolling_update.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/infrastructure-playbooks/rolling_update.yml b/infrastructure-playbooks/rolling_update.yml index 3a4b39f6e..9b74f7048 100644 --- a/infrastructure-playbooks/rolling_update.yml +++ b/infrastructure-playbooks/rolling_update.yml @@ -1,6 +1,10 @@ --- # This playbook does a rolling update for all the Ceph services -# Change the value of 'serial:' to adjust the number of server to be updated. +# +# The value of 'serial:' adjusts the number of servers to be updated simultaneously. +# We recommend a value of 1, which means hosts of a group (e.g: monitor) will be +# upgraded one by one. It is really crucial for the update process to happen +# in a serialized fashion. DO NOT CHANGE THIS VALUE. # # The four roles that apply to the ceph hosts will be applied: ceph-common, # ceph-mon, ceph-osd and ceph-mds. So any changes to configuration, package updates, etc,