summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-cluster/upgrades/v3_3
Commit message (Collapse)AuthorAgeFilesLines
* Fix and reorder control plane service restart.Devan Goodwin2016-10-212-3/+3
| | | | | | | | | This was missed in the standalone upgrade control plane playbook. However it also looks to be out of order, we should restart before reconciling and upgrading nodes. As such moved the restart directly into the control plane upgrade common code, and placed it before reconciliation.
* Use pre_upgrade tag instread of a dry run variable.Devan Goodwin2016-09-293-19/+70
|
* Move etcd backup from pre-upgrade to upgrade itself.Devan Goodwin2016-09-292-4/+0
|
* Skip the docker role in early upgrade stages.Devan Goodwin2016-09-293-12/+18
| | | | | | | | This improves the situation further and prevents configuration changes from accidentally triggering docker restarts, before we've evacuated nodes. Now in two places, we skip the role entirely, instead of previous implementation which only skipped upgrading the installed version. (which did not catch config issues)
* Allow filtering nodes to upgrade by label.Devan Goodwin2016-09-293-11/+11
|
* Split upgrade for control plane/nodes.Devan Goodwin2016-09-294-22/+84
|
* Verify masters are upgraded before proceeding with node only upgrade.Devan Goodwin2016-09-282-2/+8
|
* Attempt to tease apart pre upgrade for masters/nodes.Devan Goodwin2016-09-283-2/+147
|
* Split upgrade entry points into control plane/node.Devan Goodwin2016-09-283-48/+19
|
* Upgrade configs for protobuf support.Devan Goodwin2016-08-081-0/+2
|
* Introduce 1.3/3.3 upgrade path.Devan Goodwin2016-07-252-0/+83
Refactored the 3.2 upgrade common files out to a path that does not indicate they are strictly for 3.2. 3.3 upgrade then becomes a relatively small copy of the byo entry point, all calling the same code as 3.2 upgrade. Thus far there are no known 3.3 specific upgrade tasks. In future we will likely want to allow hooks out to version specific pre/upgrade/post tasks. Also fixes a bug where the handlers were not restarting nodes/openvswitch containers doing upgrades, due to a change in Ansible 2+.