<feed xmlns='http://www.w3.org/2005/Atom'>
<title>csa/devops/ansible-patches/openshift.git/roles/openshift_logging_eventrouter/defaults, branch ands</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/'/>
<entry>
<title>Updating logging components image defaulting pattern to match openshift_logging pattern</title>
<updated>2017-11-06T21:56:54+00:00</updated>
<author>
<name>Eric Wolinetz</name>
<email>ewolinet@redhat.com</email>
</author>
<published>2017-11-06T21:53:55+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=6575595891f71e7d9b9ac929b9ba58117a65e17b'/>
<id>6575595891f71e7d9b9ac929b9ba58117a65e17b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Use "requests" for CPU resources instead of limits</title>
<updated>2017-10-19T15:02:14+00:00</updated>
<author>
<name>Peter Portante</name>
<email>peter.portante@redhat.com</email>
</author>
<published>2017-10-13T15:04:49+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=578ac5b348fa3e9c7d0d05e3a0f579839ecd79dd'/>
<id>578ac5b348fa3e9c7d0d05e3a0f579839ecd79dd</id>
<content type='text'>
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)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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)
</pre>
</div>
</content>
</entry>
<entry>
<title>logging: introducing event router</title>
<updated>2017-09-26T08:50:15+00:00</updated>
<author>
<name>Jan Wozniak</name>
<email>jwozniak@redhat.com</email>
</author>
<published>2017-08-01T13:24:41+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.master.suren.me/cgit/csa/devops/ansible-patches/openshift.git/commit/?id=4e30a4243a6c9692c24a574ecfd83c2bcd1e2785'/>
<id>4e30a4243a6c9692c24a574ecfd83c2bcd1e2785</id>
<content type='text'>
- 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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- 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
</pre>
</div>
</content>
</entry>
</feed>
