| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Sync all openshift.common.use_openshift_sdn uses in yaml files
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Most occurrences are in a form:
```yaml
openshift.common.use_openshift_sdn | default(true) | bool
```
Let's make all occurences this way given the use_openshift_sdn is set to true anyway.
See https://github.com/openshift/openshift-ansible/blob/0c350dcc7d06d62be5ba3a8e468dff85cdd96dd7/roles/openshift_facts/library/openshift_facts.py#L2035
|
|/
|
|
| |
Also, add log dumping to master service startup too
|
| |
|
|
|
|
|
| |
At least in my smoke testing of a containerized install i had to
manually reload systemd
|
| |
|
|
|
|
|
|
|
| |
Fixes "Could not find the requested service atomic-openshift-master:
cannot enable" error during reinstall.
https://bugzilla.redhat.com/show_bug.cgi?id=1451693
|
|\
| |
| | |
Merged by openshift-bot
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit allows to specify imageConfig.format specifically for master
or for nodes.
One use case of this could be if you want to use customer builder
images. In this case imageConfig.format only needs to be changed in the
master-config.yml but not in the node-config.yml.
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
| |
* Lines are commented out vice being removed
* Comment is added indicating why the change happened
* Variable openshift_disable_swap added to allow user control
|
| |
|
|
|
|
| |
https://github.com/openshift/openshift-ansible/pull/2707)
|
|\
| |
| | |
node: ensure conntrack-tools is installed
|
| |
| |
| |
| |
| |
| | |
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1420182
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use use_system_containers=true in the inventory file
alternatively you can select each component as:
use_openvswitch_system_container=true
use_node_system_container=true
use_master_system_container=true
system_images_registry holds the registry from where to fetch system
containers.
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
|
|\
| |
| | |
Pre-pull master/node/ovs images during upgrade.
|
| |
| |
| |
| |
| |
| |
| |
| | |
We did this for install but not upgrade, leading to situations where the
service restarts after upgrade could take much longer than expected as
docker pulls down the new image. Now the images are present when we
restart services and should allow them to come back online much more
quickly, equivalent to rpm service restarts.
|
|/ |
|
|
|
|
|
|
| |
* Ansible systemd module used in place of service module
* Refactored command tasks which are no longer necessary
* Applying rules from openshift-ansible Best Practices Guide
|
|\
| |
| | |
Refactor to use Ansible package module
|
| |
| |
| |
| |
| | |
The Ansible package module will call the correct package manager for the
underlying OS.
|
|/
|
|
|
|
| |
Fedora Atomic Host does not have tuned installed.
Fixes #2809
|
|\
| |
| | |
Support 3rd party scheduler
|
| | |
|
| | |
|
|/
|
|
| |
* Node labels are parsed from openshift_node_labels if they exist
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm testing with a bleeding edge RHEL Atomic Host, and it looks
like we pulled in a new version of selinux-policy that has
`virt_sandbox_use_nfs` aliased to `virt_use_nfs`.
In https://github.com/openshift/openshift-ansible/pull/2356
Adam changed this to check for Fedora. This changes things
to drop the distribution check, and instead parse the `getsebool`
output to determine whether or not the boolean is an alias,
and should hence work on all distributions/versions.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1372388
|
|\
| |
| | |
Reload units after node container service modified.
|
| | |
|
|/ |
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Per-service environment variables
|
| | | |
|
|\| | |
|
| | | |
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It appears that in some situations (can't reliably reproduce yet), node
will fail to start. This appears to be related to the node-dep service
and possibly it's environment file.
This file is also an EnvironmentFile for the node service, but it's only
created by the node-dep service, and it looks like it may try to read
it's environment before the node-dep service has fully started and
created the file.
Workaround with a an explicit service start.
|
| |
| |
| |
| |
| | |
Allows the use of arbitrary tags, precise control over containers and
rpms, and likely mixed environments.
|
|\| |
|