Unnamed repository; edit this file 'description' to name the repository. http://suren.me/cgit/csa/devops/ansible-patches/openshift.git/atom?h=ands 2018-01-11T23:43:36+00:00 2018-01-11T23:43:36+00:00 Scott Dodson sdodson@redhat.com 2018-01-11T23:43:36+00:00 urn:sha1:fa649787c6a19bbfffb16d9cce3f8e3f7de5a8a1 Move more plugins to lib_utils 2018-01-10T16:34:36+00:00 Michael Gugino mgugino@redhat.com 2018-01-05T04:55:34+00:00 urn:sha1:d3fefc32a727fe3c13159c4e9fe4399f35b487a8 This commit continues moving plugins into lib_utils. This commit does not move any plugins for add-on roles such as logging and metrics. 2018-01-04T20:01:11+00:00 Nathan Kinder nkinder@redhat.com 2018-01-04T20:01:11+00:00 urn:sha1:3c5539a339145af54536d2731d7444b04f4cdf64 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. 2017-12-14T18:08:55+00:00 Noriko Hosoi nhosoi@redhat.com 2017-12-12T18:18:38+00:00 urn:sha1:f1748bdcb0d9b14af2f319a02ff72afd9074fae0 . fixing a typo in fluentd template . adjusting the default value of openshift_logging_mux_file_buffer_limit 2017-12-05T14:40:51+00:00 Michael Gugino mgugino@redhat.com 2017-11-29T02:03:25+00:00 urn:sha1:0de559c8f2fd310fe36047ae000574229b7858c9 Remove hosted vars from openshift_facts. The current pattern is causing a bunch of undesired sideffects. 2017-11-06T21:56:54+00:00 Eric Wolinetz ewolinet@redhat.com 2017-11-06T21:53:55+00:00 urn:sha1:6575595891f71e7d9b9ac929b9ba58117a65e17b 2017-10-19T15:02:14+00:00 Peter Portante peter.portante@redhat.com 2017-10-13T15:04:49+00:00 urn:sha1:578ac5b348fa3e9c7d0d05e3a0f579839ecd79dd 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) 2017-08-18T07:41:14+00:00 Jan Wozniak jwozniak@redhat.com 2017-08-09T15:31:00+00:00 urn:sha1:00e7908e983f97ab31360aeff32824f52fd25efd Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322 2017-08-01T17:12:06+00:00 Rich Megginson rmeggins@redhat.com 2017-07-27T15:50:03+00:00 urn:sha1:ace4a6cf7c5f9e3abea46a1811d04f4d5a03505f 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. 2017-07-28T20:10:49+00:00 Noriko Hosoi nhosoi@redhat.com 2017-06-29T19:43:52+00:00 urn:sha1:61fe309c853946585a2a6a6404ef89dc5ebfb9f0 (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)