-
Notifications
You must be signed in to change notification settings - Fork 192
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
Ubuntu support #10
Comments
I'm also interested in debian compatibility ! |
+1 For Debian I'll take ubuntu as well. |
Thanks for filing this. I'd like to extend Debian/Ubuntu functionality into ansible-elk but it's fairly low-priority given I'm working on a whole lot of other stuff. Ideally we'd just build in OS detection using Ansible facts. I don't know when I'll have time to work on it but I think it's a great idea and something I will plan for in the future. |
@sadsfae I figured I would start on this now, as I need to support some debian based systems. I figured I would start by supporting beats installation on them and then extend the ELK installation to be able to be installed on Ubuntu/Debian. Seem like a good road map? |
See PR #48 for more info on the Ubuntu/Debian support for beats installation. Will be looking into ELK installation support. |
It would be great if we have the Ubuntu support as this is found more stable in production systems and more supported on certain applications than Linux or CentOS |
I think a reasonable approach here is to first start with ubuntu client support for
While this definitely isn't true (and Ubuntu is Linux) I think a good first step is to provide Ubuntu client support (for clients / beats). Actual Ubuntu/Debian support for ELK/EFK may come later, depending on any LSB differences in configuration files. I'll need to setup a few testing Debian/Ubuntu VMs to get this going as I don't use it in my day-to-day. |
Could you please add an ansible script for ubuntu?
The text was updated successfully, but these errors were encountered: