Skip to content
Snippets Groups Projects
  1. Sep 04, 2017
    • Bertrand Lallau's avatar
      Fluentd: manage multiline log pattern · 38a6d304
      Bertrand Lallau authored
      Actual Fluentd config doesn't manage multiline log pattern like:
      
      2017-08-16 21:41:03.097 7 WARNING oslo_config.cfg [-] Option "firewall_driver" from group "DEFAULT" is deprecated for removal (
      nova-network is deprecated, as are any related configuration options.
      ). Its value may be silently ignored in the future.
      
      This log will generate 1 Fluentd event for each line (in previous
      example 3 events).
      This is really a wrong behaviour and made Kibana interface not friendly.
      This patch uses a multiline parser.
      
      Change-Id: Iee337645d1dc42876ec79be08ee3715f11a53d87
      Closes-Bug: #1711399
      38a6d304
  2. Aug 29, 2017
    • Bertrand Lallau's avatar
      Fluentd: rework and fix tail source config · eab91d42
      Bertrand Lallau authored
      Actually a unique 'tail' source is used for all logs files in
      kolla/*/*.log.
      
      So log files from services like: chrony, elasticsearch, etcd, grafana,
      influxdb, kibana, mongodb... are actually processed by our Fluentd
      config, but should not cause all following config will failed to parse
      them. It just uses CPU for nothing cause they will
      never match the following filters:
      * record_transformer => add Hostname, Logger, programname field
      * rewrite_tag_filter => rewrite 'programname' TAG if needed
      
      Hence these filters should only be applied to Openstack services logs to
      avoid CPU usage.
      
      Furthermore WGI and Apache logs files must be treated differently.
      
      Change-Id: I425979160291e1123e3775e39243bca06ed22c2f
      Closes-Bug: #1711390
      eab91d42
  3. Aug 24, 2017
  4. Aug 23, 2017
  5. Aug 22, 2017
  6. Aug 21, 2017
  7. Aug 20, 2017
  8. Aug 19, 2017
    • Sam Yaple's avatar
      Revert "Update Keystone haproxy config to balance based on source ip" · 0fc512e0
      Sam Yaple authored
      This reverts commit 91321ac8.
      
      The reasoning given in this commit is incorrect. Keystone/oslo.cache
      uses memcached hosts based on a hashing of the key to determine which
      memcached host to check. If you have different configured memcached
      servers per keystone deployment you have a mis-configured deployment.
      
      Any RESTapi should be capable of roundrobin load-balancing. I am not
      familiar with the Murano case with uploading a package, but this change
      also does not address Murano at all.
      
      As far as Horizon goes, that hasn't had a problem with shared backends
      since the beginning because we use memcached servers with a shared
      secret key [1].
      
      All this change has done is lowered the efficiency of loadbalancing
      keystone.
      
      [1] https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/horizon/templates/local_settings.j2#L149
      
      Change-Id: Ic0b550e7c96d67c39153933b527ab3edf7d90f27
      0fc512e0
  9. Aug 18, 2017
  10. Aug 17, 2017
  11. Aug 16, 2017
Loading