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 - OVA - Deployment #182

Open
c-bordon opened this issue Jan 28, 2025 · 0 comments
Open

MVP - OVA - Deployment #182

c-bordon opened this issue Jan 28, 2025 · 0 comments
Assignees
Labels
level/task Task issue type/enhancement Enhancement issue

Comments

@c-bordon
Copy link
Member

c-bordon commented Jan 28, 2025

Implementation Plan

The initial implementation plan covers the following steps sequentially:

  1. Upgrade the OVA base OS and the Build OVA workflow to use AL2023 #147
    Change the OVA Base OS from AL2 to AL2023.

  2. MVP - Create OVA and AMI Configuration Modules #157
    After changing the OS, the next step is to implement the modules responsible for provisioning and configuring the Wazuh components, establishing a logic that allows the creation of a functional Wazuh OVA. (SPIKE - AMI #120 (comment))
    2.1. Provisioner
    This will be the first module to configure. It is responsible for installing the central Wazuh components on an instance (previously created using the allocator), including the cert-tool and the necessary dependencies for each component.

    2.2. Configurer
    Once the Provisioner module is implemented, the Configurer module must be created. This module is responsible for configuring all Wazuh components to ensure their proper functionality.

    The Configurer module will have three submodules, each handling specific configurations depending on the target use case (SPIKE - AMI #120 (comment)):

    • Installation Assistant: This submodule is responsible for configuring everything previously handled by the installation assistant.
    • OVA: This submodule configures everything related to the generation of the OVA. (Note: This submodule is not part of the AMI implementation but rather the OVA implementation).
    • AMI: This submodule is responsible for configuring everything related to the generation of the AMI.
  3. MVP - OVA - Testing #181
    The testing phase will consist of two types of tests:
    3.1. Logic testing: Ensures that the logic behaves as expected. Depending on the input data, it checks that the correct functions are called, the necessary data is generated, etc.
    3.2. VM functionality testing: Ensures that, once the VM is created and configured, everything works as it should:

    • The provisioner installs the requested packages correctly.
    • The configurer sets up all the components correctly. This includes verifying the state, checking for error messages in logs, ensuring proper API connectivity, verifying certificates are created, and confirming correct connectivity with Filebeat.
  1. MVP - OVA - Documentation

    • Modification of the documentation for the use of the Wazuh OVA, according to the changes generated in it during the overhaul process

Related

@c-bordon c-bordon added level/task Task issue type/enhancement Enhancement issue labels Jan 28, 2025
@wazuhci wazuhci moved this to Backlog in XDR+SIEM/Release 5.0.0 Jan 29, 2025
@teddytpc1 teddytpc1 changed the title MVP - OVA deployment MVP - OVA - Deployment Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/enhancement Enhancement issue
Projects
Status: Backlog
Development

No branches or pull requests

2 participants