Skip to content
Snippets Groups Projects
  1. Nov 28, 2023
  2. Nov 07, 2023
  3. Oct 20, 2023
  4. Jan 31, 2023
  5. Jan 05, 2023
  6. Dec 08, 2022
  7. Dec 01, 2022
  8. Nov 11, 2022
    • Doug Szumski's avatar
      Remove support for deploying OpenStack Monasca · adb8f89a
      Doug Szumski authored
      Kolla Ansible is switching to OpenSearch and is dropping support for
      deploying ElasticSearch. This is because the final OSS release of
      ElasticSearch has exceeded its end of life.
      
      Monasca is affected because it uses both Logstash and ElasticSearch.
      Whilst it may continue to work with OpenSearch, Logstash remains an
      issue.
      
      In the absence of any renewed interest in the project, we remove
      support for deploying it. This helps to reduce the complexity
      of log processing configuration in Kolla Ansible, freeing up
      development time.
      
      Change-Id: I6fc7842bcda18e417a3fd21c11e28979a470f1cf
      adb8f89a
  9. Oct 31, 2022
  10. Sep 21, 2022
  11. Mar 25, 2022
  12. Mar 21, 2022
    • Mark Goddard's avatar
      libvirt: make it possible to run libvirt on the host · 4e41acd8
      Mark Goddard authored
      In some cases it may be desirable to run the libvirt daemon on the host.
      For example, when mixing host and container OS distributions or
      versions.
      
      This change makes it possible to disable the nova_libvirt container, by
      setting enable_nova_libvirt_container to false. The default values of
      some Docker mounts and other paths have been updated to point to default
      host directories rather than Docker volumes when using a host libvirt
      daemon.
      
      This change does not handle migration of existing systems from using
      a nova_libvirt container to libvirt on the host.
      
      Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/830504
      
      Change-Id: Ia1239069ccee39416b20959cbabad962c56693cf
      4e41acd8
  13. Mar 17, 2022
    • jinyuanliu's avatar
      ADD venus for kolla-ansible · 3ccb176f
      jinyuanliu authored
      This project [1] can provide a one-stop solution to log collection,
      cleaning, indexing, analysis, alarm, visualization, report generation
      and other needs, which involves helping operator or maintainer to
      quickly solve retrieve problems, grasp the operational health of the
      platform, and improve the level of platform management.
      
      [1] https://wiki.openstack.org/wiki/Venus
      
      Change-Id: If3562bbed6181002b76831bab54f863041c5a885
      3ccb176f
  14. Feb 24, 2022
  15. Jan 10, 2022
  16. Dec 28, 2021
    • Radosław Piliszek's avatar
      Fluentd cleanup · df2a29e4
      Radosław Piliszek authored
      We no longer have to support multiple fluentd versions and rely
      on the workaround.
      
      Change-Id: Id4083a9f07317fc04467e52176850f3909703169
      df2a29e4
  17. Dec 23, 2021
  18. Dec 20, 2021
  19. Oct 08, 2021
  20. Sep 30, 2021
  21. Aug 13, 2021
  22. Aug 09, 2021
  23. Jul 07, 2021
    • wu.chunyang's avatar
      Remove tempest role · 52619984
      wu.chunyang authored
      Remove tempest role as planned
      
      Change-Id: If3cf073e88c83f670c867a49afe48845f9e81008
      52619984
  24. Jun 16, 2021
  25. Jun 11, 2021
    • Matthias Runge's avatar
      Remove support for panko · ccf8cc5d
      Matthias Runge authored
      the project is deprecated and in the process of being removed
      from OpenStack upstream.
      
      Change-Id: I9d5ebed293a5fb25f4cd7daa473df152440e8b50
      ccf8cc5d
  26. May 27, 2021
    • Scott Shambarger's avatar
      fluentd: Fix check for external elasticsearch · 283b0dec
      Scott Shambarger authored
      When enable_elasticsearch is False, and kolla_internal_fqdn is set
      and elasticsearch_address is the default, fluentd is still enabling
      output to elasticsearch.
      
      elasticsearch_address defaults to kolla_internal_fqdn, but the
      check to enable logging to an "external" elasticsearch host
      compares with kolla_internal_vip_address (fqdn != vip address).
      
      This patch fixes the comparison to use the kolla_internal_fqdn.
      
      Closes-Bug: #1927880
      Change-Id: If23a6b1273c2639d1296becc9d222546d52f63ac
      283b0dec
  27. Apr 08, 2021
  28. Mar 18, 2021
  29. Mar 07, 2021
  30. Mar 04, 2021
    • Doug Szumski's avatar
      Support bypassing Monasca Log API for control plane logs · ca1a80ab
      Doug Szumski authored
      This change allows a user to forward control plane logs
      directly to Elasticsearch from Fluentd, rather than via
      the Monasca Log API when Monasca is enabled. The Monasca
      Log API can continue to handle tenant logs.
      
      For many use cases this is simpler, reduces resource
      consumption and helps to decouple control plane logging
      services from tenant logging services.
      
      It may not always be desired, so is optional and off by
      default.
      
      Change-Id: I195e8e4b73ca8f573737355908eb30a3ef13b0d6
      ca1a80ab
  31. Dec 22, 2020
  32. Dec 16, 2020
  33. Oct 12, 2020
    • Radosław Piliszek's avatar
      Performance: optimize genconfig · 3411b9e4
      Radosław Piliszek authored
      Config plays do not need to check containers. This avoids skipping
      tasks during the genconfig action.
      
      Ironic and Glance rolling upgrades are handled specially.
      
      Swift and Bifrost do not use the handlers at all.
      
      Partially-Implements: blueprint performance-improvements
      Change-Id: I140bf71d62e8f0932c96270d1f08940a5ba4542a
      3411b9e4
    • James Kirsch's avatar
      Add support for encrypting backend Neutron API Server · 93ad57f4
      James Kirsch authored
      Add TLS support for backend Neutron API Server communication using
      HAProxy to perform TLS termination. When used in conjunction with
      enabling TLS for service API endpoints, network communication will be
      encrypted end to end, from client through HAProxy to the Neutron
      service.
      
      Change-Id: Ib333a1f1bd12491df72a9e52d961161210e2d330
      Partially-Implements: blueprint add-ssl-internal-network
      93ad57f4
  34. Sep 22, 2020
    • Mark Goddard's avatar
      Fix common role when using external mariadb · 68820133
      Mark Goddard authored
      If the common role is executed against a set of hosts that are not all
      in the fluentd group, the run_once tasks that find customisations may be
      skipped. This causes a later failure when accessing the registered
      variables for those tasks.
      
      This issue was raised on the mailing list:
      http://lists.openstack.org/pipermail/openstack-discuss/2020-September/016932.html
      
      This issue only affects the master branch, due to addition of groups
      for the common role in I6a4676bf6efeebc61383ec7a406db07c7a868b2a.
      
      This change fixes the issue by always running the find tasks, if fluentd
      is enabled.
      
      Change-Id: I559c4b94d18c7f36d43e1d88629ed44668abf859
      68820133
  35. Sep 18, 2020
  36. Jul 28, 2020
    • Mark Goddard's avatar
      Performance: use a single config file for fluentd · 56a07702
      Mark Goddard authored
      Currently we generate multiple fluentd configuration files for inputs,
      filters, formatters and outputs.
      These are then included from the main td-agent.conf configuration file.
      With a large number of hosts, this can take a long time to template.
      
      Benchmarking of templating is available at [1].
      
      This change switches to a single fluentd configuration file, with the
      include done locally. For the default template files included with Kolla
      Ansible we use Jinja includes, but this does not work with templates in
      a different directory. We therefore use the Ansible template lookup
      plugin, which has a slightly higher overhead than a jinja include, but
      far lower than generating multiple templates. This should drastically
      improve the performance of this task.
      
      [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/template.md
      
      Partially-Implements: blueprint performance-improvements
      
      Change-Id: Ia8623be0aa861fea3e54d2c9e1c971dfd8e3afa9
      56a07702
    • Mark Goddard's avatar
      Performance: use a single config file for logrotate · f329af7d
      Mark Goddard authored
      Currently we generate a logrotate configuration file for each enabled
      service. These are then included from a logrotate.d directory. With a
      large number of hosts, this can take a long time to template.
      
      Benchmarking of templating is available at [1].
      
      This change switches to a single logrotate configuration file for all
      services, with the include done locally using jinja. This should
      drastically improve the performance of this task.
      
      [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/template.md
      
      Partially-Implements: blueprint performance-improvements
      
      Change-Id: I39cfa70bef6560f615cad516c43aaef6a523b964
      f329af7d
Loading