| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Discovered situations where the inventory hostname may not be resolvable
with operations. Switching to the ssh host (an IP) should always be
correct.
|
|
|
|
|
| |
Containerized upgrades of openvswitch are already handled by updating
the container images and pulling them again.
|
|\
| |
| | |
Create v3_5 upgrade playbooks
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Updating openshift_logging role to add kibana public url to loggingPu…
|
| | |
|
| |
| |
| |
| | |
other masters
|
|/ |
|
|\
| |
| | |
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.
|
|\
| |
| | |
Wait for nodes to be ready before proceeding with upgrade.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Near the end of node upgrade, we now wait for the node to report Ready
before marking it schedulable again. This should help eliminate delays
when pods need to relocate as the next node in line is evacuated.
Happens near the end of the process, the only remaining task would be to
mark it schedulable again so easy for admins to detect and recover from.
|
|\ \
| | |
| | | |
Add new option 'docker_selinux_enabled'
|
| | |
| | |
| | |
| | |
| | | |
Allows controlling 'selinux-enabled' docker options
Can be set to true or false
|
|\ \ \
| |/ /
|/| | |
Implement simple hooks pre/post master upgrade.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Correct consistency between upgrade playbooks
|
| | | |
|
|\ \ \
| | | |
| | | | |
Serial master upgrade
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This would fail in some environments where openshift.common.hostname was
not reachable from the local system running ansible. Additionally it is
also possible the API port would not be available even if the host were.
Instead we wait for master ssh connection to come back up, then wait for
the master API on the remote host just as we do for the "service" style
restart.
|
|\ \ \ \
| |/ / /
|/| | | |
Serialize cert creation in delegated commands
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Deprecates use of 'create-master-certs' for generating master serving
certificate and loopback kubeconfig in order to reference the first
master's CA serial file.
|
|\ \ \ \
| | | | |
| | | | | |
Logging deployer tasks
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
deployer image
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Begin requiring Docker 1.12.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Document playbook directories
|
| | |_|_|/ /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
use etcdctl from the container when containerized=True
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|\ \ \ \ \ \ \
| |_|_|_|_|/ /
|/| | | | | | |
Add RPM checks as a byo playbook
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Trying to improve the name, `init` needs to be loaded before calling other
subroles.
We don't make `init` a dependency of `common`, `masters` and `nodes` to
avoid running the relatively slow `openshift_facts` multiple times.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Note: on a simple example run of ansible-playbook against a single
docker-based host, I saw the execution time jump from 7s to 17s. That's
unfortunate, but it is probably better to reuse openshift_facts, than to
come up with new variables.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Because that's the main playbook directory in use.
|
| | | | | | | |
|