rolling_update: clarify "serial" usage

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 <seb@redhat.com>
pull/1109/head
Sébastien Han 2016-11-21 11:29:05 +01:00
parent 25d8ce958f
commit 38e846e542
1 changed files with 5 additions and 1 deletions

View File

@ -1,6 +1,10 @@
--- ---
# This playbook does a rolling update for all the Ceph services # 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, # 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, # ceph-mon, ceph-osd and ceph-mds. So any changes to configuration, package updates, etc,