santerikainulainen/ansible-role-elasticsearch
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Changes to restart correctly on multi node install

Browse source
This commit is contained in:
Dale McDiarmid 2015-12-24 13:21:18 +00:00
parent 0767456e22
commit 4aee0098ce
3 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
README.md
View file

@ -198,3 +198,4 @@ all supported platforms.
* The role aims to be idempotent. Running the role multiple times, with no changes, should result in no state change on the server. If the configuration is changed, these will be applied and * The role aims to be idempotent. Running the role multiple times, with no changes, should result in no state change on the server. If the configuration is changed, these will be applied and
Elasticsearch restarted where required. Elasticsearch restarted where required.
* Systemd is used for Ubuntu versions >= 15, Debian >=8, Centos >=7. All other versions use init for service scripts. * Systemd is used for Ubuntu versions >= 15, Debian >=8, Centos >=7. All other versions use init for service scripts.

3
tasks/elasticsearch-templates.yml
View file

@ -1,6 +1,5 @@
--- ---
#TODO: How to handle in multi node
# 1. Template directory needs to be specifiable
- name: Copy templates to elasticsearch - name: Copy templates to elasticsearch
copy: src=templates dest=/etc/elasticsearch/ owner={{ es_user }} group={{ es_group }} copy: src=templates dest=/etc/elasticsearch/ owner={{ es_user }} group={{ es_group }}

1
tasks/main.yml
View file

@ -11,3 +11,4 @@
when: es_scripts when: es_scripts
- include: elasticsearch-templates.yml - include: elasticsearch-templates.yml
when: es_templates when: es_templates
- meta: flush_handlers