summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-cluster
Commit message (Collapse)AuthorAgeFilesLines
* Move excluder disablement into control plane and node upgrade playbooksScott Dodson2017-02-069-0/+36
| | | | | So that excluder is disabled and reset within the scope of each of those in addition to the overall playbook
* Restructure certificate redeploy playbooksAndrew Butcher2017-02-028-45/+61
|
* Create v3_5 upgrade playbooksRussell Teague2017-01-306-2/+322
|
* Adding names to plays and standardizingRussell Teague2017-01-279-18/+34
|
* Merge pull request #3198 from mtnbikenc/drain-fixRussell Teague2017-01-261-1/+1
|\ | | | | Correct usage of draining nodes
| * Correct usage of draining nodesRussell Teague2017-01-261-1/+1
| |
* | Standardize add_host: with name and changed_whenRussell Teague2017-01-256-7/+17
|/ | | | | | | The add_host: task does not change any data on the host and as practice has been configured to changed_when: False. This commit standardizes that usage in the byo and common playbooks. Additionally, taks names are added to each task to improve troubleshooting.
* Cleaning repo cache earlierRussell Teague2017-01-191-2/+2
|
* Merge pull request #3093 from mtnbikenc/upgrade-fixScott Dodson2017-01-191-0/+2
|\ | | | | Correct consistency between upgrade playbooks
| * Correct consistency between upgrade playbooksRussell Teague2017-01-131-0/+2
| |
* | Validate system restart policy during pre-upgrade.Devan Goodwin2017-01-184-0/+16
| | | | | | | | | | | | | | | | | | | | This was done far into the process potentially leaving the user in a difficult situation if they had now considered they were running the upgrade playbook on a host that would be restarted. Instead check configuration and what host we're running on in pre-upgrade and allow the user to abort before making any substantial changes. This is a step towards merging master upgrade into one serial process.
* | Merge pull request #2640 from ewolinetz/logging_deployer_tasksScott Dodson2017-01-171-0/+35
|\ \ | | | | | | Logging deployer tasks
| * | minor updates for code reviews, remove unused paramsJeff Cantrill2016-12-191-0/+5
| | |
| * | Creating openshift_logging role for deploying Aggregated Logging without a ↵ewolinetz2016-12-141-0/+30
| | | | | | | | | | | | deployer image
* | | Merge pull request #2786 from dgoodwin/docker-1.12Scott Dodson2017-01-171-2/+0
|\ \ \ | |_|/ |/| | Begin requiring Docker 1.12.
| * | Begin requiring Docker 1.12.Devan Goodwin2016-11-101-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Building off the work done for Docker 1.10, we now require Docker 1.12 by default. The upgrade process was already set to ensure you are running the latest docker during upgrade, and the standalone docker upgrade playbook can also be used if desired. As before, you can override this Docker 1.12 requirement by setting a docker_version=1.10.3 (or similar), and you can skip the default to upgrade docker by setting docker_upgrade=False.
* | | Add a fact to select --evacuate or --drain based on your OCP versionTim Bielawa2017-01-111-1/+1
| | | | | | | | | | | | Closes #3070
* | | Merge pull request #2986 from tbielawa/deprecate_node_evacuationTim Bielawa2016-12-191-4/+4
|\ \ \ | | | | | | | | Deprecate node 'evacuation' with 'drain'
| * | | Deprecate node 'evacuation' with 'drain'Tim Bielawa2016-12-161-4/+4
| | | | | | | | | | | | | | | | * https://trello.com/c/TeaEB9fX/307-3-deprecate-node-evacuation
* | | | Add master config hook for 3.4 upgrade and fix facts ordering for config ↵Andrew Butcher2016-12-161-0/+2
|/ / / | | | | | | | | | hook run.
* | | YAML LintingRussell Teague2016-12-126-13/+10
| | | | | | | | | | | | | | | * Added checks to make ci for yaml linting * Modified y(a)ml files to pass lint checks
* | | Removed verify_ansible_version playbook refsRussell Teague2016-12-084-12/+2
| | |
* | | Drop 3.2 upgrade playbooks.Devan Goodwin2016-12-082-83/+0
| | |
* | | fix tagsJason DeTiberus2016-12-011-0/+2
| | |
* | | Merge pull request #2855 from detiber/updateSchedulerDefaultsScott Dodson2016-11-291-0/+1
|\ \ \ | | | | | | | | Update scheduler defaults
| * | | do not report changed for group mappingJason DeTiberus2016-11-291-0/+1
| | | |
* | | | Merge pull request #2880 from mtnbikenc/docker-dupJason DeTiberus2016-11-291-1/+0
|\ \ \ \ | | | | | | | | | | Remove duplicate when key
| * | | | Remove duplicate when keyRussell Teague2016-11-291-1/+0
| |/ / /
* / / / 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.
* | Merge pull request #2441 from dgoodwin/34-upgrade-improvementsAndrew Butcher2016-10-045-57/+294
|\ \ | | | | | | 3.4 Upgrade Improvements
| * | 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
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-06 04:41:57 +0000