summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_mux/tasks
Commit message (Collapse)AuthorAgeFilesLines
* Fix indentation to make yamllint happyVadim Rutkovsky2018-02-101-24/+24
| | | | Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* Verify that requested services have schedulable nodes matching the selectorsVadim Rutkovsky2018-02-101-0/+7
| | | | Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-3/+3
|
* Merge pull request #6609 from nkinder/openshift_logging_mux-interfaceOpenShift Merge Robot2018-01-101-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Don't hardcode the network interface in the openshift_logging_mux role The openshift_logging_mux role hardcodes the 'eth0' interface alias for determining the IP address to use for incoming external client connections. This will cause the playbook to fail with an undefined variable error on systems where an 'eth0' interface does not exist. This patch changes the default IP address for external connections to use the 'ansible_default_ipv4' fact. It also allows this to be overridden by a new 'openshift_logging_mux_external_address' variable.
| * Don't hardcode the network interface in the openshift_logging_mux roleNathan Kinder2018-01-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | The openshift_logging_mux role hardcodes the 'eth0' interface alias for determining the IP address to use for incoming external client connections. This will cause the playbook to fail with an undefined variable error on systems where an 'eth0' interface does not exist. This patch changes the default IP address for external connections to use the 'ansible_default_ipv4' fact. It also allows this to be overridden by a new 'openshift_logging_mux_external_address' variable.
* | Migrate to import_role for static role inclusionScott Dodson2018-01-051-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | 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.
* Updating logging_facts to be able to pull values from config maps yaml ↵Eric Wolinetz2018-01-021-13/+11
| | | | files, use diffs to keep custom changes, white list certain settings when creating diffs
* Remove references to deployment_typeMichael Gugino2017-12-211-2/+2
| | | | | | | Move openshift_deployment_type check into sanity_check action plugin. Remove compatibility for deployment_type. deployment_type has been deprecated for some time now.
* Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-1/+1
|
* Addressing tox errorsEric Wolinetz2017-11-071-18/+18
|
* Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-062-5/+18
| | | | openshift_logging pattern
* bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-1/+1
|
* Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-0/+1
| | | | | | | | | | | | | | | We now use a CPU request to ensure logging infrastructure pods are not capped by default for CPU usage. It is still important to ensure we have a minimum amount of CPU. We keep the use of the variables *_cpu_limit so that the existing behavior is maintained. Note that we don't want to cap an infra pod's CPU usage by default, since we want to be able to use the necessary resources to complete it's tasks. Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
* Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-1/+1
| | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* Impl fluentd file bufferNoriko Hosoi2017-07-281-0/+12
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Updating template parameter replica to be more unique to avoid var scope ↵ewolinetz2017-07-271-1/+1
| | | | creeping
* add mux docs; allow to specify mux namespacesRich Megginson2017-05-311-9/+13
| | | | | | | | | | | This adds the necessary documentation for the mux parameters and behavior. This also adds new parameters which allow to specify the namespaces mux must create by default, and which can be optionally added. This casts openshift_logging_use_mux to bool wherever it is used as a boolean. Also - use oc_service `labels` and `external_ips` which are now available.
* Fixing tux warnings and some final clean upewolinetz2017-05-231-6/+9
|
* Create logging deployments with non-zero replica countsSteve Kuznetsov2017-05-221-9/+1
| | | | | | | | | | | | When we currently create the set of logging `DeploymentConfig`s, we create them with zero desired replicas. This causes the deployment to immediately succeed as there is no work to be done. This inhibits our ability to use nice CLI UX features like `oc rollout status` to monitor the logging stack deployments. Instead, we should can create the configs with the correct number of replicas in the first place and stop using `oc scale` to bring them up after the fact. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
* Pulling in changes from masterewolinetz2017-05-222-0/+219