Wazuh packages redesign tier 2

[havidarou]

Description

Wazuh-packages (DevOps, QA, Agent, CppServer)

• Migrate allocator DevOps to virtual-machine repository
• Clean up everything

Wazuh-jenkins (QA, CppServer, DevOps, Javi)

• Demo and trainings

• Adapt QA release publication to DevOps repositories changes

CI (DevOps)

• Investigate and implement self-hosted runners in AWS with ASG for GitHub actions

Previous tier

• https://github.com/wazuh/internal-devel-requests/issues/187

Requirements and Restrictions

• Wazuh packages redesign tier 1 requirements should be taken into account
• New Jenkins should be used for everything QA related after 5.0
• Current wazuh-packages repository is deprecated after 4.10
• Current wazuh-jenkins repository is deprecated after 4.10
• Current wazuh-tools repository is deprecated after 4.10
• The new repository must include QA related code and tools
• The adaptation of the QA publication process to the DevOps repositories' changes must be done accordingly to the requirements from Wazuh packages redesign tier 1
  • Migrate current Jenkins procedures related to DevOps deployments to GitHub Actions
• The new Jenkins developed during Jenkins redesign tier 1 should be used exclusively for QA team related tasks
• The following installers will not be migrated from wazuh-packages repository:
  • Agent installers:
  • Alpine
  • HP-UX
  • Solaris Intel/SPARC
  • AIX
• The following will not be migrated to the new DevOps repositories (both packages and automation):
  • OVA
  • AMI
  • Wazuh unattended scripts
  • Wazuh Puppet
  • Wazuh Docker
  • Wazuh Kubernetes
  • Wazuh Ansible
  • The allocator must be migrated to the new virtual-machines repositories.
• The release procedure should be improved by:
  • Improving repository metadata generation (avoid full metadata sync)
  • Reducing execution time
  • Incorporating backups and storage
  • Mirroring production bucket (release to the mirror, sync main with the mirror, restore main with the mirror)
  • Investigate and implement Self-hosted Runners in AWS with ASG for GitHub actions

Dependencies

• https://github.com/wazuh/wazuh-jenkins/issues/5927
• https://github.com/wazuh/wazuh-jenkins/issues/6357
• https://github.com/wazuh/wazuh-jenkins/issues/6471

---

Plan

Spike

• https://github.com/wazuh/wazuh-packages/issues/3019 (DevOps)
• https://github.com/wazuh/wazuh-qa/issues/5527 (QA)
• https://github.com/wazuh/wazuh-agent-packages/issues/42 (Agent)

MVP

• Develop GitHub actions for the DevOps repositories (DevOps)
• Migrate selected Jenkins pipelines to the new Jenkins (QA)
• Migrate new Jenkins and QA tools to the new repository (QA)
• Migrate any agent related code from wazuh-packages to wazuh-agent-packages (Agent)
• Investigate and implement self-hosted runners in AWS with ASG for GitHub actions (DevOps)

Feature complete

• Adapt QA publication procedures to the changes in DevOps repositories (QA)
• Migrate QA procedures from wazuh-tools to the new repository (QA)

Assignees:

• @wazuh/devel-qa-div3

---

Approved by

• DRI name: @davidjiglesias
• Objective: Wazuh packages redesign tier 2

[rauldpm]

Issue content migrated from https://github.com/wazuh/internal-devel-requests/issues/993