openstack/openstack-ansible-ops
Code Issues Proposed changes

Explicitly use Elasticsearch data node for ILM index update

Browse Source 
When installing/configuring beats, it may be the case that elastic-logstash
nodes are not running Elasticsearch directly, and so can't update the ILM
config accordingly. This commit explicitly delegates the ILM config update
to an elasticsearch data node, in order that this will always be possible.
As Elasticsearch and logstash are by default installed together, the default
behaviour is unchanged.

Change-Id: I6833585b9a02eddc3c9a1179e487cdeaefa30ac2
This commit is contained in:
Duncan Martin Walker 2020-02-05 16:44:53 +00:00
parent b21034c4b8
commit 1214e42b85
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
elk_metrics_7x/roles/elastic_ilm/defaults/main.yml
View File

@ -16,3 +16,5 @@ default_ilm_policy:
delete: {}
default_ilm_policy_filename: "default-ilm-policy.json"
default_ilm_policy_file_location: "/tmp"
elastic_beat_no_proxy: "{{ hostvars[groups['elastic-logstash'][0]]['ansible_host'] }}"

4
elk_metrics_7x/roles/elastic_ilm/tasks/main.yml
View File

@ -5,8 +5,8 @@
- block:
- name: Update policy and template when not upgrading
include_tasks: "elastic_ilm_update_policy.yml"
delegate_to: "{{ groups['elastic-logstash'][0] }}"
delegate_to: "{{ elasticsearch_data_node_details[0] | regex_replace(':' ~ elastic_port,'') }}"
environment:
no_proxy: "{{ hostvars[groups['elastic-logstash'][0]]['ansible_host'] }},127.0.0.1"
no_proxy: "{{ elastic_beat_no_proxy }},127.0.0.1"
run_once: True
when: (elk_package_state | default('present')) != "latest"