kolla-ansible/releasenotes/notes/opensearch-log-retention-598c3389456a67e6.yaml
Doug Szumski 5e5a2dca09 Set a log retention policy for OpenSearch
We previously used ElasticSearch Curator for managing log
retention. Now that we have moved to OpenSearch, we can use
the Index State Management (ISM) plugin which is bundled with
OpenSearch.

This change adds support for automating the configuration of
the ISM plugin via the OpenSearch API. By default, it has
similar behaviour to the previous ElasticSearch Curator
default policy.

Closes-Bug: #2047037

Change-Id: I5c6d938f2bc380f1575ee4f16fe17c6dca37dcba
2023-12-21 10:51:17 +01:00

21 lines
1.0 KiB
YAML

---
features:
- |
Set a log retention policy for OpenSearch via Index State Management (ISM).
`Documentation
<https://docs.openstack.org/kolla-ansible/latest/reference/logging-and-monitoring/central-logging-guide.html#applying-log-retention-policies>`__.
fixes:
- |
Added log retention in OpenSearch, previously handled by Elasticsearch
Curator, now using Index State Management (ISM) OpenSearch bundled plugin.
`LP#2047037 <https://bugs.launchpad.net/kolla-ansible/+bug/2047037>`__.
upgrade:
- |
Added log retention in OpenSearch, previously handled by Elasticsearch
Curator. By default the soft and hard retention periods are 30 and 60 days
respectively. If you are upgrading from Elasticsearch, and have previously
configured ``elasticsearch_curator_soft_retention_period_days`` or
``elasticsearch_curator_hard_retention_period_days``, those variables will
be used instead of the defaults. You should migrate your configuration
to use the new variable names before the Caracal release.