| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- introduce block and simplify when conditions
- introduce config.yml so the self-standing etcd role can be run (e.g. to test etcd cluster deployment)
- remove empty task files
- skip dependency on openshift_etcd_ca
- replace cert paths with their appropriate variables
|
|\
| |
| | |
Create openshift-metrics entrypoint playbook
|
| | |
|
|/ |
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| | |
Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
|
|\ \
| | |
| | | |
Merged by openshift-bot
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
| |
The playbooks were crossing byo/common boundaries for task includes.
This moves all 'common' files/tasks into the 'common' folder.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|\
| |
| | |
Merged by openshift-bot
|
| | |
|
|/ |
|
|\
| |
| | |
WIP: update excluders to latest by default, in non-upgrade scenarios do not update
|
| |
| |
| |
| |
| |
| | |
- check both available excluder versions are at most of upgrade target version
- get excluder status through status command
- make excluders enablement configurable
|
|/ |
|
|
|
|
| |
upgrade README file
|
|
|
|
| |
Fixes Bug 1423425
|
|\
| |
| | |
Fixed issue where upgrade fails when using daemon sets (e.g. aggregated logging)
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Add upgrade job step after the entire upgrade performs
|
| |/ |
|
|/ |
|
| |
|
|
|
|
| |
This allows us to refer to a group of checks using a single handle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This approach should make it easier to add new checks without having to
write lots of YAML and doing things against Ansible (e.g.
ignore_errors).
A single action plugin determines what checks to run per each host,
including arguments to the check. A check is implemented as a class with
a run method, with the same signature as an action plugin and module,
and is normally backed by a regular Ansible module.
Each check is implemented as a separate Python file. This allows whoever
adds a new check to focus solely in a single Python module, and
potentially an Ansible module within library/ too.
All checks are automatically loaded, and only active checks that are
requested by the playbook get executed.
|
|
|
|
| |
Fixes Bug 1419893
|
|
|
|
|
|
|
|
|
| |
It turned out that the playbook
`playbooks/byo/openshift-preflight/check.yml` would only work under a
certain `ansible.cfg` in which `roles/` was added to `roles_path`.
It was the case with the example config prior to
b804e70cdd0bc8601bfc87fcf3e34043223828ee.
|
|\
| |
| | |
Manage the excluder functionality
|
| |
| |
| |
| |
| | |
So that excluder is disabled and reset within the scope of each of those
in addition to the overall playbook
|
|/
|
|
| |
Closes #3268
|
| |
|
| |
|
| |
|
|\
| |
| | |
Correct usage of draining nodes
|
| | |
|
|/
|
|
|
|
|
| |
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.
|
| |
|
|\
| |
| | |
Correct consistency between upgrade playbooks
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| | |
| | | |
Logging deployer tasks
|
| | | |
|