-
Notifications
You must be signed in to change notification settings - Fork 6
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
Investigate elasticsearch configuration using ansible #366
Comments
The first thing I found is an archived github repo: https://github.com/elastic/ansible-elasticsearch?tab=readme-ov-file The second thing I found is stuff to manage elastic (snapshots, reindex) using ansible, so not applicable in THIS situation: The third thing: https://github.com/geerlingguy/ansible-role-elasticsearch |
At Ansible Galaxy: https://galaxy.ansible.com/ui/standalone/roles/ricardobarbosams/elasticsearch/ https://galaxy.ansible.com/ui/standalone/roles/shaneholloman/elasticsearch/ https://galaxy.ansible.com/ui/standalone/roles/claranet/elasticsearch/ |
Looking at forks of archived elastic role (the first link in this issue): Searching for elasticsearch 8 ansible: YouTube: ElasticSearch 8.x installation on Ubuntu 20.04 LTS with Ansible https://medium.com/@abdullah.pelit/installation-of-elk-stack-version-8-9-with-ansible-aaec8a0f2765 |
Of the forks of the original elastic ansible role (first link), these seem to have been updated for 8.x: Unclear how many (if any) changes are ACTUALLY needed for v8! Many have changes for changes to ansible "include" directive. |
Great work compiling resources! So it seems we're stuck using a fork of ansible to get this done- I say just pick one that looks good, I'm not sure what input I have that might help differentiate, other than it should probably be minimally different from ansible core so we can keep up with changes there. |
The repos I'm looking at aren't forks of ansible proper, but rather add-ins to ansible. ansible has an ecosystem called "ansible galaxy" of add-ins, but I haven't spotted the candidates (last two links above) that seem most promising.... Since we're looking at using someone's github fork (almost certainly of the "role" that elastic published, then dropped support for), I'm wondering if we'll want to make a sub-fork into the mediacloud project, so we're not at risk of having something we depend on disappear or break.... I've put together a "task" to install the agent to report system stats to grafana, testing against a Docker container, and have worked on collecting and arranging the parameters for configuring ES, getting a quick reminder of all the things I hate about ansible (primarily yaml and jinja2 related, but also that it expects data structures to be layed out JUST so), edging closer to trying to install ES into athe container.. |
Nice work getting a draft up in #367- @thepsalmist, can you take a look at that PR when you get a chance? I think you have the most direct experience setting up ES clusters so I'd love for you to take the lead in making sure we've covered our bases with the main setup procedure here. |
Hey Xavier! Just wanted to ask for a status update here- do you think we'll have something working here before next wednesday? |
Keeping notes about what I learn here...
The issue about cluster configuration is #365
The text was updated successfully, but these errors were encountered: