summaryrefslogtreecommitdiffstats
path: root/playbooks/byo
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #3083 from rhcarvalho/doc-playbooksScott Dodson2017-01-171-0/+11
|\ | | | | Document playbook directories
| * Document playbook directoriesRodolfo Carvalho2017-01-131-0/+11
| |
* | Rename subrole facts -> initRodolfo Carvalho2017-01-131-1/+1
| | | | | | | | | | | | | | | | Trying to improve the name, `init` needs to be loaded before calling other subroles. We don't make `init` a dependency of `common`, `masters` and `nodes` to avoid running the relatively slow `openshift_facts` multiple times.
* | Replace custom variables with openshift_factsRodolfo Carvalho2017-01-121-1/+0
| | | | | | | | | | | | | | Note: on a simple example run of ansible-playbook against a single docker-based host, I saw the execution time jump from 7s to 17s. That's unfortunate, but it is probably better to reuse openshift_facts, than to come up with new variables.
* | Move playbook to BYORodolfo Carvalho2017-01-122-0/+75
|/ | | | Because that's the main playbook directory in use.
* 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-128-35/+32
| | | | | * 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-085-14/+2
|
* Drop 3.2 upgrade playbooks.Devan Goodwin2016-12-082-83/+0
|
* Merge pull request #2920 from detiber/schedulerVarFixAndrew Butcher2016-12-051-0/+2
|\ | | | | Scheduler var fix
| * fix tagsJason DeTiberus2016-12-011-0/+2
| |
* | Explictly set etcd vars for byo scaleupSamuel Munilla2016-11-301-0/+2
|/ | | | Fixes #2738
* 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
| |/
* | Merge pull request #2831 from dgoodwin/upgrade-orderingScott Dodson2016-11-292-4/+4
|\ \ | |/ |/| Fix rare failure to deploy new registry/router after upgrade.
| * 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
* | Merge pull request #2771 from stevekuznetsov/skuznets/network-managerScott Dodson2016-11-221-0/+36
|\ \ | |/ |/| Added a BYO playbook for configuring NetworkManager on nodes
| * Added a BYO playbook for configuring NetworkManager on nodesSteve Kuznetsov2016-11-221-0/+36
| | | | | | | | | | | | | | | | | | | | In order to do a full install of OpenShfit using the byo/config.yml playbook, it is currently required that NetworkManager be installed and configured on the nodes prior to the installation. This playbook introduces a very simple default configuration that can be used to install, configure and enable NetworkManager on their nodes. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* | 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-146-6/+6
|/
* 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
| |
| * Split upgrade entry points into control plane/node.Devan Goodwin2016-09-283-48/+19
| |
* | Update play names for consistency.Andrew Butcher2016-09-291-2/+4
|/
* Fix OpenStack cloud providerLénaïc Huard2016-09-261-3/+3
|
* Remove atomic check and cockpit.socketSamuel Munilla2016-08-261-1/+1
|
* Add support for Atomic Registry InstallsSamuel Munilla2016-08-261-0/+1
| | | | Add the Registry deployment subtype as an option in the quick installer.
* [tags] add some support for running a subset of config via tagsJason DeTiberus2016-08-241-0/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 20:37:22 +0000