Skip to content

Fix example playbook #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .config/ansible-lint.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ warn_list:
- key-order[task] # Ensure specific order of keys in mappings.
- name[casing]
- 'risky-shell-pipe'
- no-handler # backup of old certificates
skip_list:
- '106'
- 'command-instead-of-module'
Expand Down
56 changes: 49 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,20 +86,66 @@ Our default configuration will collect filesystem logs placed by `rsyslog`. Ther

There are some comments in the Playbook. Either fill them with the correct values (`remote_user`) or consider them as a hint to commonly used options.

_Note_: The roles rely on hardcoded group names for placing services on hosts. Please make sure you have groups named `elasticsearch`, `logstash` and `kibana` in your Ansible inventory. Hosts in these groups will get the respective services. Restricting your plays to the appropriate hosts will not work because the roles interact with hosts from other groups e.g. for certificate generation.
_Note_: The roles rely on hardcoded group names for placing services on hosts. Please make sure you have groups named `elasticsearch`, `logstash` and `kibana` in your Ansible inventory. Hosts in these groups will get the respective services. Just restricting your plays to the appropriate hosts will not work because the roles interact with hosts from other groups e.g. for certificate generation.

The execution order of the roles is important! (see below)

```
---
- hosts: all
# remote_user: my_username
# remote_user: my_username
become: true
collections:
- netways.elasticstack
vars:
elastic_variant: elastic #oss
# elastic_release: 8 #7
roles:
- repos

- hosts: elasticsearch
# remote_user: my_username
become: true
collections:
- netways.elasticstack
vars:
elastic_variant: elastic #oss
elasticsearch_jna_workaround: true
# elastic_release: 8 #7
roles:
- elasticsearch

- hosts: logstash
# remote_user: my_username
become: true
collections:
- netways.elasticstack
vars:
elastic_variant: elastic #oss
elastic_override_beats_tls: true
# elastic_release: 8 #7
roles:
- geerlingguy.redis
- logstash

- hosts: kibana
# remote_user: my_username
become: true
collections:
- netways.elasticstack
vars:
elastic_variant: elastic #oss
# elastic_release: 8 #7
roles:
- kibana

- hosts: all
# remote_user: my_username
become: true
collections:
- netways.elasticstack
vars:
elastic_variant: elastic #oss
elastic_override_beats_tls: true
# elastic_release: 8 #7
pre_tasks:
Expand All @@ -112,12 +158,8 @@ The execution order of the roles is important! (see below)
state: started
enabled: true
roles:
- repos
- elasticsearch
- geerlingguy.redis
- logstash
- kibana
- beats

```

## Contributing
Expand Down