d2dc07e299
We always start upgrade from Controllers role, that's a requirement.
Other roles are upgrade in the order in which they apper in
'overcloud' hostgroup from tripleo-ansible-inventory.
So far we cannot guarantee more than upgrading controllers first.
This change introduces new variable 'roles_upgrade_order'
(semi-colon separated list of roles), which can specify desired order
of roles' upgrade.
WARNING: it's operator's responsibility to specify 'controller'
role as first item of a list.
Example of using 'roles_upgrade_order' variable:
-e 'roles_upgrade_order=Controller,Database;Networker;Compute'
Here we start upgrade with Controller and Database roles,
then Networker role and finishing with Compute role.
Default behavior is unchanged: we start by upgrading Controller role,
followed by a roles from tripleo-ansible-inventory.
Change-Id: I8807877990f569cf6eec76e162bc353e8a34ffe8
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| common | ||
| fast-forward-upgrade | ||
| update | ||
| upgrade | ||
| main.yml | ||