Skip to content
Snippets Groups Projects
  1. Feb 13, 2017
  2. Feb 10, 2017
  3. Feb 04, 2017
  4. Jan 12, 2017
  5. Nov 08, 2016
  6. Nov 03, 2016
    • Jeffrey Zhang's avatar
      Move precheck into its own role · fa458019
      Jeffrey Zhang authored
      * Merge prechecks.yml and site.yml playbook
      * Create empty precheck.yml into all roles.
      
      Change-Id: I8a138558a26c0a2a66c5fd48ed37be657c99c1dd
      Implements: blueprint condition-pre-check
      fa458019
  7. Nov 01, 2016
  8. Oct 24, 2016
  9. Oct 10, 2016
  10. Sep 23, 2016
    • Serguei Bezverkhi's avatar
      ES and Kibana config modification for Kube · 911dfe4e
      Serguei Bezverkhi authored
      This PS modifies Elasticsearch and Kibana configuration templates
      so genconfig can genarate Kubernetes compatible config for these
      services.
      
      TrivialFix
      
      Change-Id: I6886307a163a9ca27a29e6dbdac4f9080948e4b5
      911dfe4e
  11. Sep 21, 2016
  12. May 03, 2016
  13. Mar 05, 2016
    • É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
  14. Feb 26, 2016
    • SamYaple's avatar
      Change kolla_internal_address variable · d3cfb205
      SamYaple authored
      Due to poor planning on our variable names we have a situation where
      we have "internal_address" which must be a VIP, but "external_address"
      which should be a DNS name. Now with two vips "external_vip_address"
      is a new variable.
      
      This corrects that issue by deprecating kolla_internal_address and
      replacing it with 4 nicely named variables.
      
      kolla_internal_vip_address
      kolla_internal_fqdn
      kolla_external_vip_address
      kolla_external_fqdn
      
      The default behaviour will remain the same, and the way the variable
      inheritance is setup the kolla_internal_address variable can still be
      set in globals.yml and propogate out to these 4 new variables like it
      normally would, but all reference to kolla_internal_address has been
      completely removed.
      
      Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
      Partially-Implements: blueprint ssl-kolla
      d3cfb205
  15. Feb 25, 2016
  16. Feb 15, 2016
    • Dave McCowan's avatar
      Use variables to specify http or https when constructing URLs · 1cedf77f
      Dave McCowan authored
      To allow for TLS to protect the service endpoints, the protocol
      in the URLs for the endpoints will be either http or https.
      
      This patch removes the hardcoded values of http and replaces them
      with variables that can be adjusted accordingly in future patches.
      
      Change-Id: Ibca6f8aac09c65115d1ac9957410e7f81ac7671e
      Partially-implements: blueprint ssl-kolla
      1cedf77f
  17. Feb 09, 2016
  18. Jan 26, 2016
    • akwasniewska's avatar
      Added Kibana and its deployment. · 3672152d
      akwasniewska authored
      Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu.
      
      Change-Id: I1d955a5c51e416cc572eb2c9b4c57982a1d6ab67
      Partially-implements: blueprint central-logging-service
      3672152d
Loading