csa/devops/ansible-patches/openshift.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove duplicate when key	Russell Teague	2016-11-29	1	-1/+0
\|
*	Merge pull request #2771 from stevekuznetsov/skuznets/network-manager	Scott Dodson	2016-11-22	1	-0/+36
\|\ \| \| \| \|	Added a BYO playbook for configuring NetworkManager on nodes
\| *	Added a BYO playbook for configuring NetworkManager on nodes	Steve Kuznetsov	2016-11-22	1	-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 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
\| \|
* \|	Merge pull request #2663 from dgoodwin/34-upgrade	Scott Dodson	2016-10-25	5	-0/+313
\|\ \ \| \| \| \| \| \|	Add support for 3.4 upgrade.
\| * \|	Add support for 3.4 upgrade.	Devan Goodwin	2016-10-25	5	-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-restart	Scott Dodson	2016-10-25	2	-3/+3
\|\ \ \| \|/ \|/\|	Fix and reorder control plane service restart.
\| *	Fix and reorder control plane service restart.	Devan Goodwin	2016-10-21	2	-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-fix	Scott Dodson	2016-10-19	1	-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 Goodwin	2016-10-19	1	-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 Butcher	2016-10-14	6	-6/+6
\|/
*	Fix standalone docker upgrade playbook skipping nodes.	Devan Goodwin	2016-10-13	1	-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-improvements	Andrew Butcher	2016-10-04	5	-57/+294
\|\ \| \| \| \|	3.4 Upgrade Improvements
\| *	Use pre_upgrade tag instread of a dry run variable.	Devan Goodwin	2016-09-29	3	-19/+70
\| \|
\| *	Move etcd backup from pre-upgrade to upgrade itself.	Devan Goodwin	2016-09-29	2	-4/+0
\| \|
\| *	Skip the docker role in early upgrade stages.	Devan Goodwin	2016-09-29	3	-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 Goodwin	2016-09-29	4	-16/+16
\| \|
\| *	Split upgrade for control plane/nodes.	Devan Goodwin	2016-09-29	4	-22/+84
\| \|
\| *	Verify masters are upgraded before proceeding with node only upgrade.	Devan Goodwin	2016-09-28	2	-2/+8
\| \|
\| *	Attempt to tease apart pre upgrade for masters/nodes.	Devan Goodwin	2016-09-28	3	-2/+147
\| \|
\| *	Split upgrade entry points into control plane/node.	Devan Goodwin	2016-09-28	3	-48/+19
\| \|
* \|	Update play names for consistency.	Andrew Butcher	2016-09-29	1	-2/+4
\|/
*	Fix OpenStack cloud provider	Lénaïc Huard	2016-09-26	1	-3/+3
\|
*	Remove atomic check and cockpit.socket	Samuel Munilla	2016-08-26	1	-1/+1
\|
*	Add support for Atomic Registry Installs	Samuel Munilla	2016-08-26	1	-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 tags	Jason DeTiberus	2016-08-24	1	-0/+4
\|
*	Fix standalone Docker upgrade missing symlink.	Devan Goodwin	2016-08-19	1	-0/+1
\|
*	Support for redeploying certificates.	Andrew Butcher	2016-08-11	2	-1/+25
\|
*	Merge pull request #2211 from dgoodwin/33-upgrade-playbook	Scott Dodson	2016-08-08	4	-5/+100
\|\ \| \| \| \|	1.3 / 3.3 Upgrades
\| *	Upgrade configs for protobuf support.	Devan Goodwin	2016-08-08	1	-0/+2
\| \|
\| *	Introduce 1.3/3.3 upgrade path.	Devan Goodwin	2016-07-25	4	-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+.
* \|	Convert ansible facts callback to v2.	Andrew Butcher	2016-08-08	1	-1/+1
\|/
*	Correct relative include for ansible version check.	Andrew Butcher	2016-07-21	1	-1/+1
\|
*	Check ansible version prior to evaluating cluster hosts and groups.	Andrew Butcher	2016-07-20	3	-0/+6
\|
*	Resolve some deprecation warnings.	Andrew Butcher	2016-07-18	1	-1/+1
\|
*	Remove 3.0 and 3.1 upgrade sub-dirs.	Devan Goodwin	2016-07-12	3	-54/+0
\|
*	Rename upgrade to just v3_2 as it's now major and minor.	Devan Goodwin	2016-07-12	2	-0/+0
\|
*	Fixes for Ansible 2.1.	Devan Goodwin	2016-07-04	1	-4/+0
\|
*	Update repoquery_cmd definitions to match latest in master.	Devan Goodwin	2016-07-04	1	-1/+1
\|
*	Merge branch 'master' into upgrade33	Devan Goodwin	2016-06-28	1	-2/+1
\|\
\| *	Block Docker 1.10 upgrade playbook when run against an Atomic OS.	Devan Goodwin	2016-06-17	1	-4/+5
\| \|
* \|	More docker upgrade fixes.	Devan Goodwin	2016-06-27	1	-5/+7
\| \|
* \|	Refactor 3.2 upgrade to avoid killing nodes without evac.	Devan Goodwin	2016-06-23	2	-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 Goodwin	2016-06-23	1	-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 upgrade33	Devan Goodwin	2016-06-23	1	-2/+2
\|\\|
\| *	Fix docker 1.10 upgrade on embedded etcd masters.	Devan Goodwin	2016-06-10	1	-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.