-
Notifications
You must be signed in to change notification settings - Fork 30
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
DTT1 - Execution time analysis #5191
Comments
UpdateWorking first on #5125 |
Update1. Analyze results of issue #5125 and provide times in a single commentAllocation + All the agent tests (install,registration,restart,stop,uninstall) (no clean-up) VAGRANT (1 Manager + 12 agents)
AWS (1 Manager + 13 agents)
2. Launch new battery of test after fixing the bugs #5125 (comment)VAGRANT (Antonio localhost)
(Federico localhost)
(Antonio localhost)
AWS
3. Central components testsVAGRANT (Antonio localhost)
AWS
Note:Antonio LocalhostLenovo ThinkPad T14 Gen 1 Federico Localhost🚧 |
UpdateWaiting for some definitions to move to the next analysis. |
UpdateYAML
1 Manager 1 Agents
1 Manager 6 Agents
1 Manager 10 Agents
1 Manager 13 Agents
|
UpdateYAML
1 Managers 0 Agents
6 Managers 0 Agents
10 Managers 0 Agents
13 Managers 0 Agents
@pro-akim I modified the YAML input to fix some errors, I updated it, and here are the results:
|
UpdateSome error found in the provision:
NoteThe EC2 is being provisioned but it is still not approachable by the provision, this error is related to that unavailability. The Allocation module will have to check the EC2 before moving to the next step, then this issue will be blocked until that update. Related issue: #5198 |
After the daily meeting today, it has been discussed the time results, these comment result times include the stack (Wazuh manager, Filebeat, Wazuh dashboard, and Wazuh indexer) but the Testing module is only testing the Wazuh manager The original idea of this issue was to check the flow using the Wazuh manager and Wazuh agent, we need to review this behavior as the flow should allow provisioning of the stack components individually, for example:
Those cases should contemplate installing the Filebeat, Wazuh dashboard, and Wazuh indexer (single or cluster), so the provision should generate certificates and copy them between nodes, also, the AIO deployment should be considered If any of those cases are not contemplated in the current development, we should create an issue and discuss if it should be added for DTT1 or DTT2 |
Moved this issue to DTT1 as we need to test the threading fix |
Updated #5191 (comment) with AWS results Due to the thread bug issue, this issue will be edited so it reports the following data:
The parallel tests will have to report the same test cases (1-N, M-1) but for multiple threads {2, 4, 6, 8, 10), with this data, we will be able to determine which AWS instance type we need for the Jenkins CI Blocked as |
Moved ETA to 30/04/2024 as we need all DTT1 changes to test it correctly (main ETA 29/04/2024) |
Moved ETA to 02/05/2024 as we need time to test the main branch: #4495 (comment) |
TEST PLAN - ETA May 15Testing Plan Guideline
Test mix table and time metrics
Workflow filesAGENTSTest Agents workflow fileTBDPLATFORMS:
Agent platform not included in the tests
MANAGERSTest Managers workflow fileTBDPLATFORMS: (TBD)
AIOTest AIO workflow fileTBDPLATFORMS: (TBD)
|
Description
We need to perform an analysis of DTT1 execution times so that we have reference times. The idea of this issue is to collect the following information for future improvements:
This analysis must be carried out in a way that considers different deployments such as time-based when using
N
agents andM
managers.Since local execution will vary from machine to machine, this analysis will be performed in AWS.
Due to the #5193 limitation, we will use the following system matrix:
1 Manager - N agents
Debian 12
Ubuntu 22
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 11, Debian 10, CentOS 8
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 11, Debian 10, CentOS 8, CentOS 7, Oracle 9, RedHat 9, RedHat 8
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 11, Debian 10, CentOS 8, CentOS 7, Oracle 9, RedHat 9, RedHat 8, RedHat 7, Amazon Linux 2, Amazon Linux 2023
M Manager - 0 agent*
Ubuntu 22
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 11, Debian 10, CentOS 8
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 11, Debian 10, CentOS 8, CentOS 7, Oracle 9, RedHat 9, RedHat 8
Ubuntu 22, Ubuntu 20, Ubuntu 18, Debian 12, Debian 11, Debian 10, CentOS 8, CentOS 7, Oracle 9, RedHat 9, RedHat 8, RedHat 7, Amazon Linux 2
Note: The workflow will be executed locally, but the allocation, provision, and testing should be done in AWS
Note*: Manager test does not use agents in their workflow, this will only test the manager's side
This issue is not a stopper for DTT1 but it is related to DTT1 to improve it
Related:
Tasks
Deliverable 1 - Concurrence
Note**: The procedure needs two managers to be in a cluster to test the deployment: #5191
Deliverable 2 - Multithreading
2 threads
4 threads
6 threads
8 threads
10 threads
The text was updated successfully, but these errors were encountered: