csa/devops/ansible-patches/openshift.git/playbooks/byo/openshift-cluster/upgrades/v3_3, branch ands

Remove upgrade playbooks for 3.3 through 3.5

2017-11-08T21:32:07+00:00

v3.3 Upgrade Refactor

2017-05-02T15:32:14+00:00

Refactor initialize groups tasks

2017-04-12T19:34:01+00:00

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

2017-03-07T21:27:48+00:00

- 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

2017-02-16T12:38:42+00:00

Move excluder disablement into control plane and node upgrade playbooks

2017-02-06T19:23:49+00:00

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

2017-01-27T21:04:03+00:00

Validate system restart policy during pre-upgrade.

2017-01-18T14:40:21+00:00

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.

YAML Linting

2016-12-12T18:54:24+00:00

* Added checks to make ci for yaml linting
* Modified y(a)ml files to pass lint checks

Fix rare failure to deploy new registry/router after upgrade.

2016-11-21T15:29:07+00:00

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