Unnamed repository; edit this file 'description' to name the repository. http://suren.me/cgit/csa/devops/ansible-patches/openshift.git/atom?h=ands 2018-02-05T19:44:16+00:00 2018-02-05T19:44:16+00:00 Eric Wolinetz ewolinet@redhat.com 2018-01-05T17:06:43+00:00 urn:sha1:d5879135f077e4aaaa09c8e4ebf5d9ef2a063a78 2017-11-27T12:11:45+00:00 Jan Pazdziora jpazdziora@redhat.com 2017-11-27T11:32:48+00:00 urn:sha1:37636c325aed612c06f86cbb042fc14bcbde218c 2017-11-21T17:17:27+00:00 Rich Megginson rmeggins@redhat.com 2017-11-21T00:55:20+00:00 urn:sha1:9196bc888bf481b05c3dba03e2e501d25aff6890 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 2017-10-23T08:06:30+00:00 Jan Wozniak jwozniak@redhat.com 2017-10-09T14:58:32+00:00 urn:sha1:862f50ff66324d7d1f23fe9bedd5d9d664578302 - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent 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-09-27T14:54:47+00:00 stran steveqtran@gmail.com 2017-09-25T21:46:29+00:00 urn:sha1:5a8736cab14618e6c9dd11183613ac5eff403c66 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 2017-08-30T22:48:35+00:00 Jeff Cantrill jcantril@redhat.com 2017-08-17T16:18:57+00:00 urn:sha1:f0a12fafd1320cd717eea896bb27cf222df6e9c3 2017-08-30T02:00:11+00:00 Scott Dodson sdodson@redhat.com 2017-08-30T02:00:11+00:00 urn:sha1:ace1f0b63bd0347990ffc3db806f23972f13560c 2017-08-23T18:07:12+00:00 Jeff Cantrill jcantril@redhat.com 2017-08-17T16:18:57+00:00 urn:sha1:f03e4edbb449848e9519c57be463c220f9870799 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.