Include package provision for system test docker environment

[Rebits]

Related issue
#3965

Description

Include package support for system tests.

Added

• Package support for system tests

Testing performed

Environment provision: #3966 (comment)

[Rebits]

Testing

agentless_cluster

LAY RECAP **************************************************************************************************************************************************************************************************************************
localhost                  : ok=7    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
wazuh-master               : ok=10   changed=8    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-worker1              : ok=10   changed=9    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-worker2              : ok=10   changed=9    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   

basic_cluster

PLAY RECAP *********************************************************************************************************************************************
localhost                  : ok=13   changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
wazuh-agent1               : ok=10   changed=8    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-agent2               : ok=10   changed=9    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-agent3               : ok=10   changed=9    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-master               : ok=16   changed=9    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-worker1              : ok=12   changed=7    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   
wazuh-worker2              : ok=12   changed=7    unreachable=0    failed=0    skipped=3    rescued=0    ignored=0   

Tuesday 21 February 2023  17:12:01 +0000 (0:00:07.474)       0:04:41.590 ****** 
=============================================================================== 
roles/agent-role : Installing dependencies using apt ------------------------------------------------------------------------------------------- 16.93s
roles/agent-role : Installing dependencies using apt ------------------------------------------------------------------------------------------- 15.91s
roles/worker-role : Restart Wazuh -------------------------------------------------------------------------------------------------------------- 15.65s
roles/worker-role : Restart Wazuh -------------------------------------------------------------------------------------------------------------- 14.00s
roles/master-role : Start Wazuh ---------------------------------------------------------------------------------------------------------------- 12.97s
roles/master-role : Clone wazuh-qa repository --------------------------------------------------------------------------------------------------

one_manager_agent

PLAY RECAP *********************************************************************************************************************************************
localhost                  : ok=5    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
wazuh-agent1               : ok=9    changed=7    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
wazuh-manager              : ok=11   changed=4    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   

[juliamagan]

How will the new parameters be set? Can you update the system README with the instructions for provisioning with packages?

[Rebits]

To provide a system environment using the built package, it is required to use the package_repository, repository, package_version, package_revision
parameters. For example, to provision a production environment we will use the following command:

ansible-playbook -i inventory.yml playbook.yml --extra-vars='{"package_repository":"packages", "repository": "4.x", "package_version": "4.4.0", "package_revision": "1"}'

Note
This example was included in the system README documentation

The decision to specify the package using those multiple parameters instead of a single one with the full package URL was motivated by the following conditions:

• System tests currently only support the deb system, so it is not necessary to include architecture or OS information in the path
• Full package path could be not intuitive
• It would be necessary to include agent and manager URLs
• It is consistent with Jenkins pipelines.

---

Also, it has tested the improvement of speed in environment provision. For this example, it has been used the basic_cluster environment. For this environment, the use of packages for system test provisioning is significantly faster compared to using sources. While the sources take around 23 minutes, the packages take only 9 minutes to complete the provisioning process. Therefore, I recommend shifting to using packages for system test provisioning when possible.

[Rebits]

Evidences

Evidences.zip

Tests have been found to be stable with this change.