summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-cluster/upgrades
Commit message (Collapse)AuthorAgeFilesLines
* Add missing byo v3_7 playbooksScott Dodson2017-08-084-0/+52
|
* evalute groups when running etcd upgrade from ↵Jan Chaloupka2017-06-281-0/+2
| | | | byo/openshift-cluster/upgrades/upgrade_etcd.yml
* v3.3 Upgrade RefactorRussell Teague2017-05-024-302/+3
|
* v3.4 Upgrade RefactorRussell Teague2017-05-024-298/+3
|
* v3.5 Upgrade RefactorRussell Teague2017-05-024-308/+3
|
* v3.6 Upgrade RefactorRussell Teague2017-05-024-308/+3
|
* Minor v3.6 upgrade docs fixesRussell Teague2017-04-182-6/+9
|
* Refactor initialize groups tasksRussell Teague2017-04-1214-46/+26
| | | | | | | | | | | | Two tasks for initializing group names for the byo playbooks was located in the common folder in the std_include.yml file. Byo dependencies should not be in the common folder. The two tasks have been removed from common/openshift-cluster/std_include.yml to a new file byo/openshift-cluster/initialize_groups.yml. All references where these tasks were included from either std_include.yml or other various files have been updated to use the byo initialize_groups.yml. The methodology implemented follows the pattern of having groups set up in byo then calling out to playbooks in common, which are common to all deployments.
* Refactor docker upgrade playbooksRussell Teague2017-04-104-74/+1
| | | | | The playbooks were crossing byo/common boundaries for task includes. This moves all 'common' files/tasks into the 'common' folder.
* validate and normalize inventory variablesLuke Meyer2017-03-291-1/+0
| | | | | | | | | | In openshift_repos and everywhere, ensure deployment_type and openshift_deployment_type are defined and the same. We really want to set openshift_deployment_type, but users will likely still have just deployment_type, so accept both. And don't make every playbook default openshift_deployment_type to deployment_type. This introduces the openshift_sanitize_inventory role to run before anything else.
* Added 3.5 -> 3.6 upgrade playbooksSteve Kuznetsov2017-03-245-0/+349
|
* Merge pull request #3626 from mtnbikenc/module_renameOpenShift Bot2017-03-151-2/+2
|\ | | | | Merged by openshift-bot
| * Renaming oadm_manage_node to oc_adm_manage_nodeRussell Teague2017-03-101-2/+2
| |
* | re-enable excluders if they are enabled after openshift version detectionJan Chaloupka2017-03-091-0/+2
|/
* Merge pull request #3529 from ingvagabund/upgrade-excluders-in-upgrade-onlyJan Chaloupka2017-03-079-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 updateJan Chaloupka2017-03-079-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 checkScott Dodson2017-03-072-0/+8
|/
* Fix issue #3505, add notes about origin upgrade versions support in BYO ↵Stéphane Klein2017-02-271-2/+2
| | | | upgrade README file
* Fix typo, add symlinks for rolesScott Dodson2017-02-172-2/+2
| | | | Fixes Bug 1423425
* Merge pull request #3370 from adbaldi/workScott Dodson2017-02-161-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 Baldi2017-02-151-1/+1
| |
* | initialize oo_nodes_to_upgrade group when running control plane upgrade onlyJan Chaloupka2017-02-163-0/+9
| |
* | Merge pull request #3367 from soltysh/upgrade_jobsScott Dodson2017-02-152-0/+4
|\ \ | | | | | | Add upgrade job step after the entire upgrade performs
| * | Add upgrade job step after the entire upgrade performsMaciej Szulik2017-02-152-0/+4
| |/
* | upgrades: fix path to disable_excluder.ymlJan Chaloupka2017-02-151-1/+1
|/
* Modify playbooks to use oadm_manage_node moduleRussell Teague2017-02-131-7/+24
|
* 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
* Create v3_5 upgrade playbooksRussell Teague2017-01-306-2/+322
|
* Adding names to plays and standardizingRussell Teague2017-01-276-12/+18
|
* 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-252-3/+6
|/ | | | | | | 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 #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-125-5/+2
| | | | | | | | | | * 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-081-2/+0
| |
* | Drop 3.2 upgrade playbooks.Devan Goodwin2016-12-082-83/+0
| |
* | 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
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-24 19:07:45 +0000