summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_mux
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>
* Set default image tag to openshift_image_tag for servicesVadim Rutkovsky2018-02-081-1/+1
| | | | Signed-off-by: Vadim Rutkovsky <vrutkovs@redhat.com>
* Merge pull request #7015 from sdodson/v310Scott Dodson2018-02-061-2/+2
|\ | | | | Initial support for 3.10
| * Initial support for 3.10Scott Dodson2018-02-051-2/+2
| |
* | Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-057-3/+268
|/
* Merge pull request #6614 from mgugino-upstream-stage/plugins-to-lib-utilsScott Dodson2018-01-111-0/+1
|\ | | | | Move more plugins to lib_utils
| * Move more plugins to lib_utilsMichael Gugino2018-01-101-0/+1
| | | | | | | | | | | | | | This commit continues moving plugins into lib_utils. This commit does not move any plugins for add-on roles such as logging and metrics.
* | Merge pull request #6670 from nhosoi/allowed_versions2Scott Dodson2018-01-111-2/+2
|\ \ | | | | | | Bug 1527178 - installation of logging stack failed: Invalid version s…
| * | Bug 1527178 - installation of logging stack failed: Invalid version ↵Noriko Hosoi2018-01-091-2/+2
| |/ | | | | | | | | | | | | | | specified for Elasticsearch openshift_logging_{curator,elasicsearch,fluentd,kibana,mux}/vars/main.yml: - adding "3_9" to __allowed_.*_versions - bumping __latest_.*_version to "3_9"
* | Merge pull request #6609 from nkinder/openshift_logging_mux-interfaceOpenShift Merge Robot2018-01-102-1/+2
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | 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-042-1/+2
| | | | | | | | | | | | | | | | | | | | | | 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.
* Merge pull request #5894 from ewolinetz/logging_defaults_from_existingOpenShift Merge Robot2018-01-021-13/+11
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Update logging to use existing cluster deployment for defaults This will allow us to use logging facts to set defaults of specific configurations such as ES index replicas and shard count. The update to logging facts yields us output like: ```json "elasticsearch": { "clusterrolebindings": {}, "configmaps": { "logging-elasticsearch": { "elasticsearch.yml": { "cloud": { "kubernetes": { "namespace": "${NAMESPACE}", "pod_label": "${POD_LABEL}", "pod_port": 9300 } }, "cluster": { "name": "${CLUSTER_NAME}" }, "discovery": { "type": "kubernetes", "zen.minimum_master_nodes": "${NODE_QUORUM}", "zen.ping.multicast.enabled": false }, "gateway": { "expected_nodes": "${RECOVER_EXPECTED_NODES}", "recover_after_nodes": "${NODE_QUORUM}", "recover_after_time": "${RECOVER_AFTER_TIME}" }, "index": { "number_of_replicas": 0, "number_of_shards": 1, "translog": { "flush_threshold_period": "5m", "flush_threshold_size": "256mb" }, "unassigned.node_left.delayed_timeout": "2m" }, "io.fabric8.elasticsearch.authentication.users": [ "system.logging.kibana", "system.logging.fluentd", "system.logging.curator", "system.admin" ], ``` TODO: - [x] Update logging facts to pull out settings from config maps - [x] Move `openshift_sanitize_inventory/library/conditional_set_fact.py` up to repo level - [x] Generate diffs against currently deployed configs and correctly patch in custom changes from customers - [x] Use `conditional_set_fact` to easily set defaults for logging based on logging facts, or falling back to role defaults when not specified in the inventory - [x] Update all components to follow patching configmaps
| * 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
* | Bug 1527178 - installation of logging stack failed: Invalid version ↵Noriko Hosoi2017-12-271-2/+2
|/ | | | | | | | specified for Elasticsearch openshift_logging_{curator,elasicsearch,fluentd,kibana,mux}/vars/main.yml: - adding "3_8" to __allowed_.*_versions - replacing the value of __latest_.*_version "3_6" with "3_8".
* 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.
* Relocate filter plugins to lib_utilsMichael Gugino2017-12-181-0/+1
| | | | | | | | | | | | | | This commit relocates filter_plugings to lib_utils, changes the namespacing to prevent unintended use of older versions that may be present in filter_plugins/ directory on existing installs. Add lib_utils to meta depends for roles Also consolidate some plugins into lib_utils from various other areas. Update rpm spec, obsolete plugin rpms.
* openshift_logging_{fluentd,mux}_file_buffer_limit mismatchNoriko Hosoi2017-12-141-1/+1
| | | | | . fixing a typo in fluentd template . adjusting the default value of openshift_logging_mux_file_buffer_limit
* Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-1/+1
|
* Fix hosted varsMichael Gugino2017-12-052-1/+2
| | | | | | Remove hosted vars from openshift_facts. The current pattern is causing a bunch of undesired sideffects.
* dist.iteritems() no longer exists in Python 3.Jan Pazdziora2017-11-271-1/+1
|
* containerPort must be an int; correctly quote/brace replicas valueRich Megginson2017-11-211-1/+1
| | | | | | | | | The mux containerPort must be an int The eventrouter REPLICAS must use the double quote/double brace syntax documented here: https://docs.openshift.org/latest/dev_guide/templates.html#writing-parameters And must be escaped because it uses double braces, as explained here: http://jinja.pocoo.org/docs/dev/templates/#escaping
* Merge pull request #5652 from ruromero/bz1498398OpenShift Merge Robot2017-11-181-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Add enclosing <store> tags to sample secure-forward.conf files This fixes [BZ#1498398](https://bugzilla.redhat.com/show_bug.cgi?id=1498398) The examples provided in the documentation to configure the secure forward mention the configuration must be enclosed between the <store> tag. For that I think the examples should include it as well. See [3.6 Documentation](https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html#aggregated-fluentd) ~~~ <store> @type secure_forward self_hostname pod-${HOSTNAME} shared_key thisisasharedkey secure yes enable_strict_verification yes ca_cert_path /etc/fluent/keys/your_ca_cert ca_private_key_path /etc/fluent/keys/your_private_key ca_private_key_passphrase passphrase <server> host ose1.example.com port 24284 </server> <server> host ose2.example.com port 24284 standby </server> <server> host ose3.example.com port 24284 standby </server> </store> ~~~
| * bug 1498398. Enclose content between store tagRuben Romero Montes2017-10-041-0/+2
| |
* | Addressing tox errorsEric Wolinetz2017-11-071-18/+18
| |
* | Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-065-7/+24
| | | | | | | | openshift_logging pattern
* | bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-1/+1
| |
* | Bug 1452939 - change Logging & Metrics imagePullPolicyJan Wozniak2017-10-231-1/+1
| | | | | | | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent
* | Use "requests" for CPU resources instead of limitsPeter Portante2017-10-193-11/+22
|/ | | | | | | | | | | | | | | 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)
* Added new variables for logging role for remote-syslog pluginstran2017-09-271-0/+46
| | | | | | | | Includes the following code review fixes, and a rebase with upstream/master - mux.j2 template needed mux specific parameters for syslog configs - fixed bug in IF condition not checking for true-ness - updated README wording to remove ambiguity of payload_key's datatype
* Fluentd: one output tag, one output pluginNoriko Hosoi2017-09-251-0/+2
| | | | Adding <label @OUTPUT> to fluent.conf.
* Merge pull request #5289 from jcantrill/1487573_fix_allowed_es_versionOpenShift Bot2017-09-081-2/+2
|\ | | | | Merged by openshift-bot
| * bug 1487573. Bump the allowed ES versionsJeff Cantrill2017-09-011-2/+2
| |
* | logging set memory request to limitJeff Cantrill2017-08-301-0/+2
|/
* Revert "logging set memory request to limit"Scott Dodson2017-08-291-2/+0
|
* Merge pull request #5119 from jcantrill/logging_memory_same_as_limitScott Dodson2017-08-291-0/+2
|\ | | | | logging set memory request to limit
| * logging set memory request to limitJeff Cantrill2017-08-231-0/+2
| |
* | Bug 1471322: logging roles based image versionsJan Wozniak2017-08-182-3/+3
|/ | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* use mux_client_mode instead of use_mux_clientRich Megginson2017-08-012-2/+1
| | | | | | | | | | | | | | | | | | | | | Instead of the `openshift_logging_use_mux_client` boolean parameter, use `openshift_logging_mux_client_mode` which will allow us to support different mux client use cases: The value `maximal` will cause Fluentd to perform as much of the processing as possible at the local node. This currently means all of the processing *except* for the Kubernetes metadata processing, which will be done by mux. This is the currently recommended mode to use due to current scaling issues. The value `minimal` means that Fluentd will do *no* processing at all, and send the raw logs to mux for processing. This is currently not recommended to use due to current scaling issues. Ansible will warn you if you try to use this mode. `MUX_ALLOW_EXTERNAL` is no longer needed in the mux dc. mux now always operates to process external logs. The ansible setting `openshift_logging_mux_allow_external` is still required in order to set up the mux service to accept connections from outside of the cluster.
* Impl fluentd file bufferNoriko Hosoi2017-07-283-0/+43
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Updating template parameter replica to be more unique to avoid var scope ↵ewolinetz2017-07-272-2/+2
| | | | creeping
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-062-3/+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.
* Merge pull request #4618 from nhosoi/resource_limitsScott Dodson2017-06-291-2/+8
|\ | | | | Sync environment variables FLUENTD/MUX_CPU_LIMIT FLUENTD/MUX_MEMORY_L…
| * Sync environment variables FLUENTD/MUX_CPU_LIMIT FLUENTD/MUX_MEMORY_LIMIT ↵Noriko Hosoi2017-06-271-2/+8
| | | | | | | | with the resource limit values.
* | Bug 1465168 - mux doesn't recognize ansible boolean parameters correctlyRich Megginson2017-06-271-1/+1
|/ | | | | | https://bugzilla.redhat.com/show_bug.cgi?id=1465168 The fix is to pass the value through the `lower` filter. The value is set in defaults/main.yaml so it should always have a value.
* Merge pull request #4356 from nhosoi/mux_params-0OpenShift Bot2017-06-152-1/+11
|\ | | | | Merged by openshift-bot
| * Reverted most of this pr 4356 except:Noriko Hosoi2017-06-051-4/+4
| | | | | | | | | | | | | | | | | | adding openshift_logging_fluentd_buffer_queue_limit: 1024 openshift_logging_fluentd_buffer_size_limit: 1m openshift_logging_mux_buffer_queue_limit: 1024 openshift_logging_mux_buffer_size_limit: 1m and setting the matched environment variables.
| * Adding the defaults for openshift_logging_fluentd_{cpu,memory}_limit to ↵Noriko Hosoi2017-06-051-4/+4
| | | | | | | | | | | | | | | | roles/openshift_logging_fluentd/defaults/main.yml. Adding the description for openshift_hosted_logging_fluentd_{cpu,memory}_limit to README.md. Replaced openshift_hosted_logging_mux_.* with openshift_logging_mux_.*.
| * Adding environment variables FLUENTD_CPU_LIMIT, FLUENTD_MEMORY_LIMIT, ↵Noriko Hosoi2017-06-021-0/+4
| | | | | | | | MUX_CPU_LIMIT, MUX_MEMORY_LIMIT.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-22 09:31:31 +0000