Skip to content
Snippets Groups Projects
  1. Mar 07, 2016
  2. Mar 06, 2016
  3. Mar 05, 2016
    • Jenkins's avatar
      01b0be02
    • Jenkins's avatar
      Merge "Make Heka send logs to Elasticsearch" · 08101fd4
      Jenkins authored
      08101fd4
    • Serguei Bezverkhi's avatar
      Reconfigure for Swift · 514da176
      Serguei Bezverkhi authored
      This implements reconfigure for Swift service. Fixes swift-rsyncd in
      All-in-One deployment
      
      Partially-Implements: blueprint kolla-reconfig
      
      Change-Id: I82bfa3c73b7365bc3a0ea35d3fc102a3525ebd8c
      514da176
    • Éric Lemoine's avatar
      Use alphabetical order in cleanup-containers · 97ae0634
      Éric Lemoine authored
      TrivialFix
      Change-Id: I95f2e6d17ba7960b2f87344f30b7884d621f9ecb
      97ae0634
    • Éric Lemoine's avatar
      Make Heka send logs to Elasticsearch · 491aff0b
      Éric Lemoine authored
      This patch includes changes relative to integrating Heka with
      Elasticsearch and Kibana.
      
      The main change is the addition of an Heka ElasticSearchOutput plugin
      to make Heka send the logs it collects to Elasticsearch.
      
      Since Logstash is not used the enable_elk deploy variable is renamed
      to enable_central_logging.
      
      If enable_central_logging is false then Elasticsearch and Kibana are
      not started, and Heka won't attempt to send logs to Elasticsearch.
      
      By default enable_central_logging is set to false. If
      enable_central_logging is set to true after deployment then the Heka
      container needs to be recreated (for Heka to get the new
      configuration).
      
      The Kibana configuration used property names that are deprecated in
      Kibana 4.2. This is changed to use non-deprecated property names.
      
      Previously logs read from files and from Syslog had a different Type
      in Heka. This is changed to always use "log" for the Type. In this
      way just one index instead of two is used in Elasticsearch, making
      things easier to the user on the visualization side.
      
      The HAProxy configuration is changed to add entries for Kibana.
      Kibana server is now accessible via the internal VIP, and also via
      the external VIP if there's one configured.
      
      The HAProxy configuration is changed to add an entry for
      Elasticsearch. So Elasticsearch is now accessible via the internal
      VIP. Heka uses that channel for communicating with Elasticsearch.
      
      Note that currently the Heka logs include "Plugin
      elasticsearch_output" errors when Heka starts. This occurs when Heka
      starts processing logs while Elasticsearch is not yet started. These
      are transient errors that go away when Elasticsearch is ready. And
      with buffering enabled on the ElasticSearchOuput plugin logs will be
      buffered and then retransmitted when Elasticsearch is ready.
      
      Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb
      Implements: blueprint central-logging-service
      491aff0b
    • Jenkins's avatar
      Merge "Bump ansible version to head of devel" · 89762631
      Jenkins authored
      89762631
  4. Mar 04, 2016
Loading