aboutsummaryrefslogtreecommitdiffstats
path: root/puppet/services/README.rst
diff options
context:
space:
mode:
authorJenkins <jenkins@review.openstack.org>2017-02-03 21:42:33 +0000
committerGerrit Code Review <review@openstack.org>2017-02-03 21:42:33 +0000
commitb64f7fa512b4209e781d7159fe7d93bc3d37a99e (patch)
tree8ea38ef91c57f9395416555b4cb34b66e96d952e /puppet/services/README.rst
parent3aff42dde21c19247961b78f07e9b5b2cc1e8f00 (diff)
parent1b58806a6214f01af74785f5d7791984b7180ce1 (diff)
Merge "Reduce number of steps for upgrades"
Diffstat (limited to 'puppet/services/README.rst')
-rw-r--r--puppet/services/README.rst18
1 files changed, 11 insertions, 7 deletions
diff --git a/puppet/services/README.rst b/puppet/services/README.rst
index 34cb350b..9c2d8c5c 100644
--- a/puppet/services/README.rst
+++ b/puppet/services/README.rst
@@ -57,10 +57,14 @@ is a list of ansible tasks to be performed during the upgrade process.
Similar to the step_config, we allow a series of steps for the per-service
upgrade sequence, defined as ansible tasks with a tag e.g "step1" for the first
-step, "step2" for the second, etc. Note that each step is performed in batches,
-then we move on to the next step which is also performed in batches (we don't
-perform all steps on one node, then move on to the next one which means you
-can sequence rolling upgrades of dependent services via the step value).
+step, "step2" for the second, etc (currently only two steps are supported, but
+more may be added when required as additional services get converted to batched
+upgrades).
+
+Note that each step is performed in batches, then we move on to the next step
+which is also performed in batches (we don't perform all steps on one node,
+then move on to the next one which means you can sequence rolling upgrades of
+dependent services via the step value).
The tasks performed at each step is service specific, but note that all batch
upgrade steps are performed before the `upgrade_tasks` described below. This
@@ -93,9 +97,9 @@ step, "step2" for the second, etc.
5) Perform any migration tasks, e.g DB sync commands
- 6) Start control-plane services
-
- 7) Any additional online migration tasks (e.g data migrations)
+Note that the services are not started in the upgrade tasks - we instead re-run
+puppet which does any reconfiguration required for the new version, then starts
+the services.
Nova Server Metadata Settings
-----------------------------