summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_mux
Commit message (Collapse)AuthorAgeFilesLines
* 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.
| * Introducing fluentd/mux buffer_queue_limit, buffer_size_limit, cpu_limit, ↵Noriko Hosoi2017-06-022-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and memory_limit. Default values: openshift_logging_fluentd_cpu_limit: 100m openshift_logging_fluentd_memory_limit: 512Mi openshift_logging_fluentd_buffer_queue_limit: 1024 openshift_logging_fluentd_buffer_size_limit: 16m openshift_logging_fluentd_buffer_size_limit: 1m openshift_logging_mux_cpu_limit: 500m openshift_logging_mux_memory_limit: 1Gi openshift_logging_mux_buffer_queue_limit: 1024 openshift_logging_mux_buffer_size_limit: 1m
* | Merge pull request #4342 from richm/mux-uses-fluentd-secretOpenShift Bot2017-06-051-1/+1
|\ \ | |/ |/| Merged by openshift-bot
| * mux uses fluentd cert/key to talk to ESRich Megginson2017-05-311-1/+1
| |
* | add mux docs; allow to specify mux namespacesRich Megginson2017-05-312-12/+21
|/ | | | | | | | | | | 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-222-10/+2
| | | | | | | | | | | | 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-228-0/+460
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-09 20:08:15 +0000