Skip to content

Migrate the generate_ova.sh script to Python for local OVA compilation #252

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

Closed
2 tasks done
c-bordon opened this issue Apr 9, 2025 · 5 comments · Fixed by #299
Closed
2 tasks done

Migrate the generate_ova.sh script to Python for local OVA compilation #252

c-bordon opened this issue Apr 9, 2025 · 5 comments · Fixed by #299
Assignees
Labels
level/task Task issue type/bug Bug issue

Comments

@c-bordon
Copy link
Member

c-bordon commented Apr 9, 2025

Description

We need to investigate migrating the generate_ova.sh script code to Python to use all the modules created during Level 1 of the DevOps Review.

Tasks

  • Investigate the changes needed to migrate the bash script to Python.
  • Generate the necessary migration plan.

Related

@c-bordon c-bordon added level/task Task issue type/enhancement Enhancement issue labels Apr 9, 2025
@wazuhci wazuhci moved this to Blocked in XDR+SIEM/Release 6.0.0 Apr 10, 2025
@Enaraque Enaraque self-assigned this May 6, 2025
@Enaraque
Copy link
Member

Enaraque commented May 7, 2025

Update report 07/05/2025

I’ve been reviewing what needs to be developed, as a large part of the script is focused on setting up wazuh-install.sh, which will not be used in main. Based on what actually needs to be implemented, I created this issue related to the use of the box for the local build.

@Enaraque
Copy link
Member

Enaraque commented May 8, 2025

Update report 08/05/2025

I have been researching how to implement the logic in the simplest and cleanest way possible. For now, the plan is to have the script bring up a machine with the custom Vagrantfile. In this Vagrantfile, the virtual machines repo will be included using rsync, and Hatch will be installed on the machine. Once Hatch is installed, the run command from the Hatch ova-post-configurer environment will be used to begin the installation of everything related to the OVA (except the pre-configurer, as it is responsible for generating the box, which we don't need).

For now, I am running some tests to see if this idea can be implemented and if there are no issues during its development.

@Enaraque
Copy link
Member

Enaraque commented May 9, 2025

Update report 09/05/2025

The creation and configuration of the OVA has been completed. What's left is exporting the OVA and testing that everything works correctly.

Image

@wazuhci wazuhci moved this from Blocked to In progress in XDR+SIEM/Release 6.0.0 May 9, 2025
@Enaraque
Copy link
Member

Update report 12/05/2025

I have finished the development concerning the export of the OVA. I still need to do the necessary tests to know if there is anything to be added to the local construction process.

@wazuhci wazuhci moved this to In progress in XDR+SIEM/Release 6.0.0 May 12, 2025
@Dwordcito Dwordcito added type/bug Bug issue and removed type/enhancement Enhancement issue labels May 12, 2025
@Enaraque
Copy link
Member

Update report 13/05/2025

Testing has been carried out to ensure everything is working as expected. An issue was detected with the generation of the server certificates, and a corresponding issue has been opened (#291)

Once the problem with the server certificates was fixed, it was found that the indexer was not starting correctly. It is currently being investigated whether the issue is related to the OVA generation or the Wazuh indexer package itself.

@wazuhci wazuhci moved this from In progress to Pending review in XDR+SIEM/Release 6.0.0 May 14, 2025
@wazuhci wazuhci moved this from Pending review to Done in XDR+SIEM/Release 6.0.0 May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment