NETWAYS / NETWAYS/ansible-collection-elasticstack
Handle hosts with multiple IP addresses
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
The current implementation automatically uses one IPv4 address Ansible finds as fact for connections. This works with nodes with one interface but it may or may not work with multihomed hosts.
We need a way to tackle this issue in a default way. Solutions to bin different connections to different networks is definitely a "nice to have" but beyond the scope of a single issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the collection obtains the IPv4 fact used for connections and how that address is passed to Elastic Stack services. Define a default, predictable choice for multihomed hosts; support for binding different connections to different networks is explicitly out of scope. Done means connections work reliably when a host has multiple IP addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100