csa/devops/ansible-patches/openshift.git/roles/openshift_logging_curator/templates, branch ands

Adding support for ES 5.x tech preview opt in

2018-02-05T19:44:16+00:00

dist.iteritems() no longer exists in Python 3.

2017-11-27T12:11:45+00:00

Bug 1452939 - change Logging & Metrics imagePullPolicy

2017-10-23T08:06:30+00:00

- all images logging and metrics change their default imagePullPolicy
  from Always to IfNotPresent

Use "requests" for CPU resources instead of limits

2017-10-19T15:02:14+00:00

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)

logging set memory request to limit

2017-08-30T22:48:35+00:00

Revert "logging set memory request to limit"

2017-08-30T02:00:11+00:00

logging set memory request to limit

2017-08-23T18:07:12+00:00

Updating template parameter replica to be more unique to avoid var scope creeping

2017-07-27T16:57:07+00:00

fix curator host, port params; remove curator es volumes

2017-05-31T21:22:52+00:00

Create logging deployments with non-zero replica counts

2017-05-22T17:07:59+00:00

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