Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Added 3.5 -> 3.6 upgrade playbooks | Steve Kuznetsov | 2017-03-24 | 5 | -0/+349 |
| | |||||
* | Merge pull request #3626 from mtnbikenc/module_rename | OpenShift Bot | 2017-03-15 | 1 | -2/+2 |
|\ | | | | | Merged by openshift-bot | ||||
| * | Renaming oadm_manage_node to oc_adm_manage_node | Russell Teague | 2017-03-10 | 1 | -2/+2 |
| | | |||||
* | | re-enable excluders if they are enabled after openshift version detection | Jan Chaloupka | 2017-03-09 | 1 | -0/+2 |
|/ | |||||
* | Merge pull request #3529 from ingvagabund/upgrade-excluders-in-upgrade-only | Jan Chaloupka | 2017-03-07 | 9 | -9/+9 |
|\ | | | | | WIP: update excluders to latest by default, in non-upgrade scenarios do not update | ||||
| * | - update excluders to latest, in non-upgrade scenarios do not update | Jan Chaloupka | 2017-03-07 | 9 | -9/+9 |
| | | | | | | | | | | | | - check both available excluder versions are at most of upgrade target version - get excluder status through status command - make excluders enablement configurable | ||||
* | | Add oc_objectvalidator to upgrade check | Scott Dodson | 2017-03-07 | 2 | -0/+8 |
|/ | |||||
* | Fix issue #3505, add notes about origin upgrade versions support in BYO ↵ | Stéphane Klein | 2017-02-27 | 1 | -2/+2 |
| | | | | upgrade README file | ||||
* | Fix typo, add symlinks for roles | Scott Dodson | 2017-02-17 | 2 | -2/+2 |
| | | | | Fixes Bug 1423425 | ||||
* | Merge pull request #3370 from adbaldi/work | Scott Dodson | 2017-02-16 | 1 | -1/+1 |
|\ | | | | | Fixed issue where upgrade fails when using daemon sets (e.g. aggregated logging) | ||||
| * | Fixed issue where upgrade fails when using daemon sets (e.g. aggregated logging) | Andrew Baldi | 2017-02-15 | 1 | -1/+1 |
| | | |||||
* | | initialize oo_nodes_to_upgrade group when running control plane upgrade only | Jan Chaloupka | 2017-02-16 | 3 | -0/+9 |
| | | |||||
* | | Merge pull request #3367 from soltysh/upgrade_jobs | Scott Dodson | 2017-02-15 | 2 | -0/+4 |
|\ \ | | | | | | | Add upgrade job step after the entire upgrade performs | ||||
| * | | Add upgrade job step after the entire upgrade performs | Maciej Szulik | 2017-02-15 | 2 | -0/+4 |
| |/ | |||||
* / | upgrades: fix path to disable_excluder.yml | Jan Chaloupka | 2017-02-15 | 1 | -1/+1 |
|/ | |||||
* | Modify playbooks to use oadm_manage_node module | Russell Teague | 2017-02-13 | 1 | -7/+24 |
| | |||||
* | Move excluder disablement into control plane and node upgrade playbooks | Scott Dodson | 2017-02-06 | 9 | -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 playbooks | Andrew Butcher | 2017-02-02 | 8 | -45/+61 |
| | |||||
* | Create v3_5 upgrade playbooks | Russell Teague | 2017-01-30 | 6 | -2/+322 |
| | |||||
* | Adding names to plays and standardizing | Russell Teague | 2017-01-27 | 9 | -18/+34 |
| | |||||
* | Merge pull request #3198 from mtnbikenc/drain-fix | Russell Teague | 2017-01-26 | 1 | -1/+1 |
|\ | | | | | Correct usage of draining nodes | ||||
| * | Correct usage of draining nodes | Russell Teague | 2017-01-26 | 1 | -1/+1 |
| | | |||||
* | | Standardize add_host: with name and changed_when | Russell Teague | 2017-01-25 | 6 | -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 earlier | Russell Teague | 2017-01-19 | 1 | -2/+2 |
| | |||||
* | Merge pull request #3093 from mtnbikenc/upgrade-fix | Scott Dodson | 2017-01-19 | 1 | -0/+2 |
|\ | | | | | Correct consistency between upgrade playbooks | ||||
| * | Correct consistency between upgrade playbooks | Russell Teague | 2017-01-13 | 1 | -0/+2 |
| | | |||||
* | | Validate system restart policy during pre-upgrade. | Devan Goodwin | 2017-01-18 | 4 | -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_tasks | Scott Dodson | 2017-01-17 | 1 | -0/+35 |
|\ \ | | | | | | | Logging deployer tasks | ||||
| * | | minor updates for code reviews, remove unused params | Jeff Cantrill | 2016-12-19 | 1 | -0/+5 |
| | | | |||||
| * | | Creating openshift_logging role for deploying Aggregated Logging without a ↵ | ewolinetz | 2016-12-14 | 1 | -0/+30 |
| | | | | | | | | | | | | deployer image | ||||
* | | | Merge pull request #2786 from dgoodwin/docker-1.12 | Scott Dodson | 2017-01-17 | 1 | -2/+0 |
|\ \ \ | |_|/ |/| | | Begin requiring Docker 1.12. | ||||
| * | | Begin requiring Docker 1.12. | Devan Goodwin | 2016-11-10 | 1 | -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 version | Tim Bielawa | 2017-01-11 | 1 | -1/+1 |
| | | | | | | | | | | | | Closes #3070 | ||||
* | | | Merge pull request #2986 from tbielawa/deprecate_node_evacuation | Tim Bielawa | 2016-12-19 | 1 | -4/+4 |
|\ \ \ | | | | | | | | | Deprecate node 'evacuation' with 'drain' | ||||
| * | | | Deprecate node 'evacuation' with 'drain' | Tim Bielawa | 2016-12-16 | 1 | -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 Butcher | 2016-12-16 | 1 | -0/+2 |
|/ / / | | | | | | | | | | hook run. | ||||
* | | | YAML Linting | Russell Teague | 2016-12-12 | 6 | -13/+10 |
| | | | | | | | | | | | | | | | * Added checks to make ci for yaml linting * Modified y(a)ml files to pass lint checks | ||||
* | | | Removed verify_ansible_version playbook refs | Russell Teague | 2016-12-08 | 4 | -12/+2 |
| | | | |||||
* | | | Drop 3.2 upgrade playbooks. | Devan Goodwin | 2016-12-08 | 2 | -83/+0 |
| | | | |||||
* | | | fix tags | Jason DeTiberus | 2016-12-01 | 1 | -0/+2 |
| | | | |||||
* | | | Merge pull request #2855 from detiber/updateSchedulerDefaults | Scott Dodson | 2016-11-29 | 1 | -0/+1 |
|\ \ \ | | | | | | | | | Update scheduler defaults | ||||
| * | | | do not report changed for group mapping | Jason DeTiberus | 2016-11-29 | 1 | -0/+1 |
| | | | | |||||
* | | | | Merge pull request #2880 from mtnbikenc/docker-dup | Jason DeTiberus | 2016-11-29 | 1 | -1/+0 |
|\ \ \ \ | | | | | | | | | | | Remove duplicate when key | ||||
| * | | | | Remove duplicate when key | Russell Teague | 2016-11-29 | 1 | -1/+0 |
| |/ / / | |||||
* / / / | Fix rare failure to deploy new registry/router after upgrade. | Devan Goodwin | 2016-11-21 | 2 | -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 Fedora | Scott Dodson | 2016-11-14 | 1 | -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 Dodson | 2016-11-08 | 1 | -5/+5 |
| | | |||||
* | | Revert "Fix OpenStack cloud provider" | Scott Dodson | 2016-11-07 | 1 | -5/+5 |
| | | | | | | | | This reverts commit 1f2276fff1e41c1d9440ee8b589042ee249b95d7. | ||||
* | | Merge pull request #2662 from blues-man/update_doc_upgrade_openshift | Scott Dodson | 2016-10-25 | 1 | -2/+2 |
|\ \ | | | | | | | Update link to latest versions upgrade README | ||||
| * | | Update link to latest versions upgrade README | Natale Vinto | 2016-10-25 | 1 | -2/+2 |
| | | |