Skip to content
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

MVP - Ansible - Playbooks: wazuh-distributed playbook #1524

Open
2 tasks done
YisDav opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1584
Open
2 tasks done

MVP - Ansible - Playbooks: wazuh-distributed playbook #1524

YisDav opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1584
Assignees

Comments

@YisDav
Copy link
Member

YisDav commented Jan 23, 2025

Description

The wazuh-distributed.yml playbook will be created to facilitate the deployment of a distributed Wazuh architecture. This playbook will enable the installation and configuration of multiple Wazuh components across different servers, ensuring that they work together seamlessly.

For a more detailed description, please refer to the parent commit (#1491).

Tasks

  • Develop the wazuh-distributed.yml playbook. The playbook must support installation across all platforms, ensuring compatibility with the Central Components tier 1 OS versions and architectures.
  • Test the playbook with all supported distributed Wazuh environments to validate functionality and performance.
@teddytpc1 teddytpc1 changed the title Ansible MVP - Playbooks: wazuh-distributed playbook MVP - Ansible - Playbooks: wazuh-distributed playbook Feb 6, 2025
@wazuhci wazuhci moved this to Backlog in XDR+SIEM/Release 5.0.0 Feb 6, 2025
@YisDav YisDav linked a pull request Mar 13, 2025 that will close this issue
@wazuhci wazuhci moved this from Backlog to Pending review in XDR+SIEM/Release 5.0.0 Mar 13, 2025
@YisDav YisDav linked a pull request Mar 13, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Pending review
Development

Successfully merging a pull request may close this issue.

1 participant