summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-cluster/upgrades
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Fix rare failure to deploy new registry/router after upgrade.Devan Goodwin2016-11-212-4/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Router/registry update and re-deploy was recently reordered to immediately follow control plane upgrade, right before we proceed to node upgrade. In some situations (small or single host clusters) it appears possible that the deployer pods are running when the node in question is evacuated for upgrade. When the deployer pod dies the deployment is failed and the router/registry continue running the old version, despite the deployment config being updated correctly. This change re-orderes the router/registry upgrade to follow node upgrade. However for separate control plane upgrade, the router/registry still occurs at the end. This is because router/registry seems like they should logically be included in a control plane upgrade, and presumably the user will not manually launch node upgrade so quickly as to trigger an evac on the node in question. Workaround for this problem when it does occur is simply to: oc deploy docker-registry --latest
* / Add etcd upgrade for RHEL and FedoraScott Dodson2016-11-141-0/+26
|/ | | | | On Fedora we just blindly upgrade to the latest. On RHEL we do stepwise upgrades 2.0,2.1,2.2,2.3,3.0
* Revert "Revert openshift.node.nodename changes"Scott Dodson2016-11-081-5/+5
|
* Revert "Fix OpenStack cloud provider"Scott Dodson2016-11-071-5/+5
| | | | This reverts commit 1f2276fff1e41c1d9440ee8b589042ee249b95d7.
* Merge pull request #2662 from blues-man/update_doc_upgrade_openshiftScott Dodson2016-10-251-2/+2
|\ | | | | Update link to latest versions upgrade README
| * Update link to latest versions upgrade READMENatale Vinto2016-10-251-2/+2
| |
* | Merge pull request #2663 from dgoodwin/34-upgradeScott Dodson2016-10-255-0/+313
|\ \ | | | | | | Add support for 3.4 upgrade.
| * | Add support for 3.4 upgrade.Devan Goodwin2016-10-255-0/+313
| |/ | | | | | | | | This is a direct copy of 3.3 upgrade playbooks, with 3.3 specific hooks removed and version numbers adjusted appropriately.
* | Merge pull request #2637 from dgoodwin/ctrl-plane-restartScott Dodson2016-10-252-3/+3
|\ \ | |/ |/| Fix and reorder control plane service restart.
| * 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.
* | Merge pull request #2621 from dgoodwin/symlink-fixScott Dodson2016-10-191-3/+3
|\ \ | | | | | | Switch from "oadm" to "oc adm" and fix bug in binary sync.
| * | Switch from "oadm" to "oc adm" and fix bug in binary sync.Devan Goodwin2016-10-191-3/+3
| |/ | | | | | | | | | | | | | | Found bug syncing binaries to containerized hosts where if a symlink was pre-existing, but pointing to the wrong destination, it would not be corrected. Switched to using oc adm instead of oadm.
* / Template with_items for upstream ansible-2.2 compat.Andrew Butcher2016-10-142-2/+2
|/
* Fix standalone docker upgrade playbook skipping nodes.Devan Goodwin2016-10-131-0/+2
| | | | | Transition to being able to specify nodes to upgrade caused standalone nodes to get skipped in this playbook.
* 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-294-16/+16
|
* 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
|
* Fix OpenStack cloud providerLénaïc Huard2016-09-261-3/+3
|
* Fix standalone Docker upgrade missing symlink.Devan Goodwin2016-08-191-0/+1
|
* Upgrade configs for protobuf support.Devan Goodwin2016-08-081-0/+2
|
* Introduce 1.3/3.3 upgrade path.Devan Goodwin2016-07-254-5/+98
| | | | | | | | | | | | | | | | 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+.
* Correct relative include for ansible version check.Andrew Butcher2016-07-211-1/+1
|
* Check ansible version prior to evaluating cluster hosts and groups.Andrew Butcher2016-07-201-0/+2
|
* Remove 3.0 and 3.1 upgrade sub-dirs.Devan Goodwin2016-07-123-54/+0
|
* Rename upgrade to just v3_2 as it's now major and minor.Devan Goodwin2016-07-122-0/+0
|
* Fixes for Ansible 2.1.Devan Goodwin2016-07-041-4/+0
|
* Update repoquery_cmd definitions to match latest in master.Devan Goodwin2016-07-041-1/+1
|
* Merge branch 'master' into upgrade33Devan Goodwin2016-06-281-2/+1
|\
| * Block Docker 1.10 upgrade playbook when run against an Atomic OS.Devan Goodwin2016-06-171-4/+5
| |
* | More docker upgrade fixes.Devan Goodwin2016-06-271-5/+7
| |
* | Refactor 3.2 upgrade to avoid killing nodes without evac.Devan Goodwin2016-06-232-108/+3
| | | | | | | | | | We now handle the two pieces of upgrade that require a node evac in the same play. (docker, and node itself)
* | Update docker upgrade playbook to be more flexible.Devan Goodwin2016-06-231-18/+41
| | | | | | | | | | | | | | | | | | | | Now more of a generic upgrade playbook to go to the latest Docker version. Added support for docker_version inventory variable, in which case we disable the check for >= 1.10 and make sure you're running at least the specified version. (we will not downgrade you to the requested version however, this is much too complicated)
* | Merge branch 'master' into upgrade33Devan Goodwin2016-06-231-2/+2
|\|
| * Fix docker 1.10 upgrade on embedded etcd masters.Devan Goodwin2016-06-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | The tasks were attempting to stop/start etcd, which would be fine on the stop but on start could actually kick the non-containerized etcd service which happens to be layed down even though it's unused. When the service was requested to start again it would claim the port embedded etcd needs and the master would then fail to come up. Instead use the correct etcd_container service.
* | Remove old upgrade playbooks.Devan Goodwin2016-06-153-88/+0
|/
* Restore mistakenly reverted code.Devan Goodwin2016-06-091-0/+4
|
* Docker 1.10 UpgradeDevan Goodwin2016-06-035-4/+158
| | | | | | | | | | | | | | | | | Adds a separate playbook for Docker 1.10 upgrade that can be run standalone on a pre-existing 3.2 cluster. The upgrade will take each node out of rotation, and remove *all* containers and images on it, as this is reportedly faster and more storage efficient than performing the in place 1.10 upgrade. This process is integrated into the 3.1 to 3.2 upgrade process. Normal config playbooks now become 3.2 only, and require Docker 1.10. Users of older environments will have to use an appropriate openshift-ansible version. Config playbooks no longer are in the business of upgrading or downgrading docker.
* remove interpolated g_all_hosts with_items arg from upgrade playbooksCody Boggs2016-05-173-3/+3
|
* Block upgrading w/ ansible v2.Andrew Butcher2016-05-124-0/+16
|
* Remove vars_files on play includes for upgrade playbooks.Andrew Butcher2016-05-124-26/+72
|
* Fix cli_docker_additional_registries being erased during upgrade.Devan Goodwin2016-05-091-0/+25
| | | | | | Legacy options (cli_*) were not being migrated during upgrade. Add the oo_all_hosts group, and migrate the facts as we do in the normal cluster playbooks.
* Set g_new_master_hosts in upgrade playbooks.Andrew Butcher2016-03-073-0/+3
|
* upgrade README fixesBrenton Leanhardt2016-03-032-2/+0
|
* Adding newly required variableBrenton Leanhardt2016-03-031-0/+1
|
* First past at the upgrade processBrenton Leanhardt2016-03-032-0/+35
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 14:39:18 +0000