summaryrefslogtreecommitdiffstats
path: root/playbooks/byo/openshift-cluster/upgrades/docker/upgrade.yml
Commit message (Collapse)AuthorAgeFilesLines
* Include Deprecation: Convert to import_playbookRussell Teague2017-12-071-2/+2
|
* Playbook Consolidation - InitializationRussell Teague2017-11-151-1/+1
|
* Refactor initialize groups tasksRussell Teague2017-04-121-23/+1
| | | | | | | | | | | | 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-101-10/+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.
* Adding names to plays and standardizingRussell Teague2017-01-271-2/+8
|
* Standardize add_host: with name and changed_whenRussell Teague2017-01-251-2/+3
| | | | | | | 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.
* 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.
* | YAML LintingRussell Teague2016-12-121-0/+1
|/ | | | | * Added checks to make ci for yaml linting * Modified y(a)ml files to pass lint checks
* Template with_items for upstream ansible-2.2 compat.Andrew Butcher2016-10-141-1/+1
|
* 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.
* Docker 1.10 UpgradeDevan Goodwin2016-06-031-0/+29
Adds a separate playbook for Docker 1.10 upgrade that can be run standalone on a pre-existing 3.2 cluster. The upgrade will take each node out of rotation, and remove *all* containers and images on it, as this is reportedly faster and more storage efficient than performing the in place 1.10 upgrade. This process is integrated into the 3.1 to 3.2 upgrade process. Normal config playbooks now become 3.2 only, and require Docker 1.10. Users of older environments will have to use an appropriate openshift-ansible version. Config playbooks no longer are in the business of upgrading or downgrading docker.