Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Attempt to tease apart pre upgrade for masters/nodes. | Devan Goodwin | 2016-09-28 | 1 | -305/+0 |
| | |||||
* | Split upgrade entry points into control plane/node. | Devan Goodwin | 2016-09-28 | 1 | -1/+1 |
| | |||||
* | Drop atomic-enterprise as a valid deployment type in upgrade. | Devan Goodwin | 2016-09-28 | 1 | -2/+2 |
| | |||||
* | Stop guarding against pacemaker in upgrade, no longer necessary. | Devan Goodwin | 2016-09-28 | 1 | -8/+0 |
| | |||||
* | Support openshift_upgrade_dry_run=true for pre-upgrade checks only. | Devan Goodwin | 2016-09-28 | 1 | -0/+7 |
| | |||||
* | Improvements for Docker 1.10+ upgrade image nuking. | Devan Goodwin | 2016-08-11 | 1 | -12/+8 |
| | | | | | | | | | | | | | | | | In a parallel step prior to real upgrade tasks, clear out all unused Docker images on all hosts. This should be relatively safe to interrupt as no real upgrade steps have taken place. Once into actual upgrade, we again clear all images only this time with force, and after stopping and removing all containers. Both rmi commands use a new and hopefully less error prone command to do the removal, this should avoid missed orphans as we were hitting before. Added some logging around the current image count before and after this step, most of them are only printed if we're crossing the 1.10 boundary but one does not, just for additional information in your ansible log. | ||||
* | Introduce 1.3/3.3 upgrade path. | Devan Goodwin | 2016-07-25 | 1 | -0/+315 |
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+. |