| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Many plays only target a select subset of hosts,
especially oo_first_master for components such
as logging and registry.
This commit limits the scope of most plays to
eliminate unnecessary task execution on node
groups. This will result in great time
savings for large deployments.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1516526
|
| |
|
|
|
|
|
| |
That would prevent possible container runtime upgrades during cluster
config
Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
|
| |
|
|
|
|
|
|
|
| |
Currently, etcd scaleup playbook has no way to account
for newly added prerequisites.yml play.
This commit allows adding new etcd hosts via scaleup play
and accounts for etcd hosts that are standalone or part
of nodes or masters group.
|
| |\
| |
| | |
Fix node scaleup plays
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Currently, users have no way to run preqrequisites.yml
on just newly added nodes during scaleup.
This commit ensures only the new nodes are changed during
scaleup as well as ensure prerequisites are run.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some setups, system containers may be used
in conjunction with package_docker.
This commit ensures that the atomic
proxies are configured while using package_docker
and containerized components.
This commit also ensures containerized_groups
are based on openshift_is_containerized instead
of 'containerized' variable directly to
account for possible use of atomic hosts which
users may not specify containerized in inventory
directly.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1535323
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we are using some inventory variables
to determine what host groups should be considered
containerized.
This is problematic and has several edge cases.
This commit removes the variable l_containerized_host_groups
and builds a dynamic group of hosts named
'oo_hosts_containerized_managed_true' based on the value of
'containerized'
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In Ansible 2.2, the include_role directive came into existence as
a Tech Preview. It is still a Tech Preview through Ansible 2.4
(and in current devel branch), but with a noteable change. The
default behavior switched from static: true to static: false
because that functionality moved to the newly introduced
import_role directive (in order to stay consistent with include*
being dynamic in nature and `import* being static in nature).
The dynamic include is considerably more memory intensive as it will
dynamically create a role import for every host in the inventory
list to be used. (Also worth noting, there is at the time of this
writing an object allocation inefficiency in the dynamic include
that can in certain situations amplify this effect considerably)
This change is meant to mitigate the pressure on memory for the
Ansible control host.
We need to evaluate where it makes sense to dynamically include roles
and revert back to dynamic inclusion if and where it makes sense to do
so.
|
| |
|
|
|
|
|
|
|
|
| |
openshift_containerized_host_groups needs to be referenced via
hostvars.
This commit also updates tox ansible syntax checks to account
for unavailability of hostsvars during syntax checks.
Fixes: https://github.com/openshift/openshift-ansible/issues/6540
|
| | |
|
|
|
This commit refactors some duplicate code, removes
usage of set_fact where not needed, and reorganizes
container_runtime role to use include_role.
|
