summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging/tasks/install_logging.yaml
Commit message (Collapse)AuthorAgeFilesLines
* Whenever we create a new es node ignore health checks, changing prometheus ↵Eric Wolinetz2018-02-131-0/+2
| | | | pw gen for increased secret idempotency
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-0/+8
|
* Merge pull request #6952 from sdodson/bz1540462OpenShift Merge Robot2018-01-311-1/+3
|\ | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Don't update master-config.yaml with logging/metrics urls >= 3.9 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1540462 I thought about refactoring things just to move the assetConfig vs ConfigMap update into update_master_config but the tasks get called on different hosts via plays.
| * Only perform console configmap ops when >= 3.9Scott Dodson2018-01-311-1/+3
| |
* | No longer compare with legacy hosted varEric Wolinetz2018-01-261-2/+2
| |
* | Preserving ES dc storage type unless overridden by inventory variableEric Wolinetz2018-01-261-7/+16
|/
* Remove old assetConfig from master-config.yamlSamuel Padgett2018-01-251-1/+1
| | | | | | | | The `assetConfig` is no longer used now that the console is split into its own pod. - Remove `assetConfig` on upgrades to 3.9 - Stop writing logging and metrics URLs to assetConfig for 3.9
* Remove old console asset configSamuel Padgett2018-01-191-5/+0
| | | | Stop writing deprecated config to the console config map.
* Merge pull request #6747 from ewolinetz/logging_fix_pvc_storageclassOpenShift Merge Robot2018-01-171-4/+4
|\ | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Setting default storage_class_names for when calling openshift_loggin… …g_elasticsearch role Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1521218
| * Setting default storage_class_names for when calling ↵Eric Wolinetz2018-01-161-4/+4
| | | | | | | | openshift_logging_elasticsearch role
* | Update console config for API changesSamuel Padgett2018-01-161-2/+7
|/
* logging: fix jinja filters to support py3Vadim Rutkovsky2018-01-101-2/+2
| | | | | | | Since py3 returns `dict_items` for dict.keys() call instead of a list, it should be converted into a list for compatibility Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* Switch back to dynamic include_role in logging loopsScott Dodson2018-01-071-4/+4
| | | | | We'd switched to import_role to avoid increased memory consumption but we must use include_role whenever we loop.
* Merge pull request #6359 from spadgett/web-console-serverScott Dodson2018-01-061-0/+12
|\ | | | | Install web console server
| * Install web console serverSamuel Padgett2018-01-051-0/+12
| |
* | Migrate to import_role for static role inclusionScott Dodson2018-01-051-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-0/+3
|/ | | | files, use diffs to keep custom changes, white list certain settings when creating diffs
* Remove openshift.common.{is_atomic|is_containerized}Michael Gugino2017-12-201-1/+1
| | | | | We set these variables using facts in init, no need to duplicate the logic all around the codebase.
* Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-3/+3
|
* Merge pull request #6029 from boeboe/masterOpenShift Merge Robot2017-11-161-0/+4
|\ | | | | | | | | | | | | Automatic merge from submit-queue. logging with static pvc: allow specifying the storage class name See https://github.com/openshift/openshift-ansible/issues/6028 for more info and motivation.
| * logging with static pvc: allow specifying the storage class nameBart Van Bos2017-11-061-0/+4
| |
* | Bug 1510496 - logging: honor ES PVC sizeJan Wozniak2017-11-101-0/+2
|/
* Using the currently attached pvc for an ES dc if available, otherwise ↵Eric Wolinetz2017-11-011-2/+2
| | | | falling back to current logic
* Merge pull request #5888 from jcantrill/1501599_allow_project_overcommitOpenShift Merge Robot2017-10-301-0/+8
|\ | | | | | | | | | | | | | | Automatic merge from submit-queue. bug 1501599. Omit logging project from overcommit restrictions This PR: * Annotates the logging project to remove overcommit restrictions
| * bug 1501599. Omit logging project from overcommit restrictionsJeff Cantrill2017-10-251-0/+8
| |
* | Fix loop_var warnings during logging installMichael Gugino2017-10-241-12/+21
|/ | | | | | | | | Currently, install_logging.yml in openshift_logging role loops over other roles. This creates a collision with the keyword 'item' in those roles. This commit adds the loop_var as suggested by ansible warnings.
* Merge pull request #5748 from portante/fix-cpu-limitsScott Dodson2017-10-201-0/+5
|\ | | | | Use "requests" for CPU resources instead of limits
| * Use "requests" for CPU resources instead of limitsPeter Portante2017-10-191-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 1489498. preserve replica and shard settingsJeff Cantrill2017-10-171-0/+4
|/
* Merge pull request #5637 from wozniakjan/1496271_fixOpenShift Merge Robot2017-10-051-5/+10
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Bug 1496271 - Perserve SCC for ES local persistent storage ES can be modified to use node local persistent storage. This requires changing SCC and is described in docs: https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html During an upgrade, SCC defined by the user is ignored. This fix fetches SCC user defined as a fact and adds it to the ES DC which is later used. Also includes cherrypicked fix for - Bug 1482661 - Preserve ES dc nodeSelector and supplementalGroups cc @jcantrill
| * Bug 1496271 - Perserve SCC for ES local persistent storageJeff Cantrill2017-10-031-0/+2
| | | | | | | | | | | | | | | | | | | | ES can be modified to use node local persistent storage. This requires changing SCC and is described in docs: https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html During an upgrade, SCC defined by the user is ignored. This fix fetches SCC user defined as a fact and adds it to the ES DC which is later used.
| * bug 1482661. Preserve ES dc nodeSelector and supplementalGroupsJeff Cantrill2017-09-291-5/+8
| | | | | | | | (cherry picked from commit 601e35cbf4410972c7fa0a1d3d5c6327b82353ac)
* | Merge pull request #5543 from ewolinetz/bz1495150OpenShift Merge Robot2017-10-041-4/+0
|\ \ | |/ |/| | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Removing setting pvc size and dynamic to remove looped var setting If we don't set openshift_logging_es_pvc_size but have `openshift_logging_es_pvc_dynamic=True` we see the variable openshift_logging_elasticsearch_pvc_size is set recursively as itself. Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1495150 https://bugzilla.redhat.com/show_bug.cgi?id=1496202
| * Removing setting pvc size and dynamic to remove looped var settingEric Wolinetz2017-09-261-4/+0
| |
* | logging: introducing event routerJan Wozniak2017-09-261-0/+8
|/ | | | | | | | - eventrouter has its own role 'openshift_logging_eventrouter' written as a template - 'openshift_logging_install_eventrouter' controls whether it gets included in the playbook or not - deployed by default to 'default' namespace
* Bug 1491636 - honor openshift_logging_es_ops_nodeselectorJan Wozniak2017-09-141-0/+2
|
* Merge pull request #5219 from jcantrill/bz1480988_kibana_ops_linksScott Dodson2017-08-291-0/+1
|\ | | | | annotate the infra projects for logging to fix bz1480988
| * annotate the infra projects for logging to fix bz1480988Jeff Cantrill2017-08-281-0/+1
| |
* | Merge pull request #5044 from wozniakjan/logging_role_based_image_versionsOpenShift Bot2017-08-251-12/+0
|\ \ | |/ |/| Merged by openshift-bot
| * Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-12/+0
| | | | | | | | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* | Passing memory and cpu limit for ops ES installEric Wolinetz2017-08-221-0/+4
|/
* Updating how storage type is determined, adding bool filter in ↵ewolinetz2017-07-241-4/+12
| | | | openshift_logging_elasticsearch
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-061-1/+0
| | | | | | | | | | "openshift_logging_fluentd_use_journal=false" nor omitted collects the log entries https://bugzilla.redhat.com/show_bug.cgi?id=1466152 Do not set openshift_logging_fluentd_use_journal or USE_JOURNAL at all unless it is explicitly set as an ansible param. It is almost always better to let fluentd figure out which log driver docker is using.
* fix 1466680. Fix logging deploying to the specified namespaceJeff Cantrill2017-06-301-0/+4
|
* Fixing ops storage options being passed to openshift_logging_elasticsearch ↵ewolinetz2017-06-291-10/+12
| | | | role fixing default ops pv selector
* fix es routes for new logging rolesRich Megginson2017-06-071-0/+12
| | | | | | | | | | | | port the code that creates the external Elasticsearch routes to the new logging roles Have to suppress this error message: SSL Problem illegal change cipher spec msg, conn state = 6, handshake state = 1 which is coming from the router health check, until https://github.com/openshift/origin/issues/14515 is fixed - otherwise, the es log is spammed relentlessly
* Merge pull request #4327 from ewolinetz/fix_logging_secretOpenShift Bot2017-06-061-2/+5
|\ | | | | Merged by openshift-bot
| * Updating Kibana-proxy secret key name, fixing deleting secrets, fixed extra ↵ewolinetz2017-05-311-2/+5
| | | | | | | | ES dc creation
* | fix curator host, port params; remove curator es volumesRich Megginson2017-05-311-0/+4
|/
* Adding default value for openshift_hosted_logging_storage_kindewolinetz2017-05-301-4/+4
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-07 17:20:20 +0000