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

	Commit message (Collapse)	Author	Age	Files	Lines
*	v3.4 Upgrade Refactor	Russell Teague	2017-05-02	1	-98/+1
\|
*	Refactor initialize groups tasks	Russell Teague	2017-04-12	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \|	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.
*	- update excluders to latest, in non-upgrade scenarios do not update	Jan Chaloupka	2017-03-07	1	-1/+1
\| \| \| \| \| \|	- check both available excluder versions are at most of upgrade target version - get excluder status through status command - make excluders enablement configurable
*	initialize oo_nodes_to_upgrade group when running control plane upgrade only	Jan Chaloupka	2017-02-16	1	-0/+3
\|
*	Move excluder disablement into control plane and node upgrade playbooks	Scott Dodson	2017-02-06	1	-0/+4
\| \| \| \| \|	So that excluder is disabled and reset within the scope of each of those in addition to the overall playbook
*	Adding names to plays and standardizing	Russell Teague	2017-01-27	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	1	-0/+4
\|/ \| \| \| \| \| \| \| \| \|	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.
*	Add support for 3.4 upgrade.	Devan Goodwin	2016-10-25	1	-0/+98
	This is a direct copy of 3.3 upgrade playbooks, with 3.3 specific hooks removed and version numbers adjusted appropriately.