anchor.diff:  +
   ====
   ----
  -$ oc create -n openshift -f \
  +$ oc apply -n openshift -f \
       /usr/share/openshift/examples/infrastructure-templates/enterprise/logging-deployer.yaml
   ----
   ====
  
positive.code: volumes between all its pods. So, when scaled up, the EFK deployer ensures each
  replica of Elasticsearch has its own deployment configuration.
  
  *Viewing all Elasticsearch Deployments*
  
  To view all current Elasticsearch deployments:
  
negative.code: See the https://www.elastic.co/guide/en/kibana/4.1/discover.html[Kibana
  documentation] for more information on Kibana.
  
  [[configuring-curator]]
  === Curator
  
  Curator allows administrators to configure scheduled Elasticsearch maintenance
  operations to be performed automatically on a per-project basis. It is scheduled
  to perform actions daily based on its configuration. Only one Curator pod is
  recommended per Elasticsearch cluster. Curator is configured via a YAML
  configuration file with the following structure:
  
  ====
  ----
  $PROJECT_NAME:
    $ACTION:
      $UNIT: $VALUE
  
  $PROJECT_NAME:
    $ACTION:
      $UNIT: $VALUE
   ...
  
  ----
  ====
  
  The available parameters are:
  
  [cols="3,7",options="header"]
  |===
  |Variable Name
  |Description
  
  |`*$PROJECT_NAME*`
  |The actual name of a project, such as `myapp-devel`.  For {product-title} `operations`
  logs, use the name `.operations` as the project name.
  
  |`*$ACTION*`
  |The action to take, currently only `delete` is allowed.
  
  |`*$UNIT*`
  |One of `days`, `weeks`, or `months`.
  
  |`*$VALUE*`
  |An integer for the number of units.
  
  |`*.defaults*`
  |Use `.defaults` as the `$PROJECT_NAME` to set the defaults for projects that are
  not specified.
  
  |`*runhour*`
  |(Number) the hour of the day in 24-hour format at which to run the Curator jobs. For
  use with `.defaults`.
  
  |`*runminute*`
  |(Number) the minute of the hour at which to run the Curator jobs. For use with `.defaults`.
  |===
  
  For example, to configure Curator to
  
  - delete indices in the `myapp-dev` project older than `1 day`
  - delete indices in the `myapp-qe` project older than `1 week`
  - delete `operations` logs older than `8 weeks`
  - delete all other projects indices after they are `30 days` old
  - run the Curator jobs at midnight every day
  
  you would use:
  
  ----
  myapp-dev:
   delete:
     days: 1
  
  myapp-qe:
    delete:
      weeks: 1
  
  .operations:
    delete:
      weeks: 8
  
  .defaults:
    delete:
      days: 30
    runhour: 0
    runminute: 0
  ----
  
  
  [IMPORTANT]
  ====
  When you use `month` as the `$UNIT` for an operation, Curator starts counting at
  the first day of the current month, not the current day of the current month.
  For example, if today is April 15, and you want to delete indices that are 2 months
  older than today (delete: months: 2), Curator does not delete indices that are dated
  older than February 15; it deletes indices older than February 1. That is, it
  goes back to the first day of the current month, then goes back two whole months
  from that date. If you want to be exact with Curator, it is best to use days
  (for example, `delete: days: 30`).
  ====
  
  [[aggregate-logging-creating-the-curator-configuration]]
  ==== Creating the Curator Configuration
  
  The deployer provides a configmap from which Curator reads its
  configuration.  You may edit or replace this configmap to reconfigure
  Curator. Currently the `logging-curator` configmap is used to
  configure both your ops and non-ops Curator instances. Any `.operations`
  configurations will be in the same location as your application logs
  configurations.
  
  . To edit the provided configmap to configure your Curator instances:
  +
  ----
  $ oc edit configmap/logging-curator
  ----
  
  . To replace the provided configmap instead:
  +
  ----
  $ create /path/to/mycuratorconfig.yaml
  $ oc create configmap logging-curator -o yaml \
    --from-file=config.yaml=/path/to/mycuratorconfig.yaml | \
    oc replace -f -
  ----
  
  . After you make your changes, redeploy Curator:
  +
  ----
  $ oc deploy --latest dc/logging-curator
  $ oc deploy --latest dc/logging-curator-ops
  ----
  
  == Cleanup
  
  You can remove everything generated during the deployment while
  leaving other project contents intact:
  
  ----
  $ oc new-app logging-deployer-template --param MODE=uninstall
  ----
  
  [[aggregate-logging-upgrading]]
  