Skip to content

Commit

Permalink
Merge pull request #23 from wazuh/7-add-agent-files
Browse files Browse the repository at this point in the history 
Add agent files from wazuh/wazuh
  • Loading branch information
@vikman90
vikman90 authored Jul 9, 2024
2 parents 3ba933c + 3e4fd4a commit 3895d9d
Show file tree
Hide file tree
Showing 1,745 changed files with 496,610 additions and 2 deletions.
27 changes: 27 additions & 0 deletions .github/ISSUE_TEMPLATE/default.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
name: Issue
about: Report a bug or make a feature request.
title: ''
labels: ''
assignees: ''

---

|Wazuh version|Component|Install type|Install method|Platform|
|---|---|---|---|---|
| X.Y.Z-rev | Wazuh component | Manager/Agent | Packages/Sources | OS version |

<!--
Whenever possible, issues should be created for bug reporting and feature requests.
For questions related to the user experience, please refer:
- Wazuh mailing list: https://groups.google.com/forum/#!forum/wazuh
- Join Wazuh on Slack: https://wazuh.com/community/join-us-on-slack
Please fill the table above. Feel free to extend it at your convenience.
-->

<!--
You may want to set debug options `<component>.debug=2` (see https://documentation.wazuh.com/current/user-manual/reference/internal-options.html) to get verbose logs. This may help investigate the issue.
-->
47 changes: 47 additions & 0 deletions .github/ISSUE_TEMPLATE/planned__epic_support_new_oss.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
name: 'Planned: Epic support new OSs'
about: Add support for a new OS.
title: Support new OSs - <OS name & version>
labels: level/epic, request/operational, type/maintenance
assignees: ''

---

# Description
| Related issue |
|---|
| Issue number |

| Agent tier | Central components support | OS type |
|-|-|-|
| 1/2/3 | Yes/No | New family/Major/Minor |

# Specific issues

<!-- Always -->
**QA**
-

<!-- Central components/Major/New family -->
**CppServer**
-

<!-- Central components -->
**Indexer**
-

<!-- Always -->
**DevOps**
-

<!-- Always -->
**Dashboard**
-

<!-- Always -->
**ThreatIntel**
-

<!-- Always -->
**Agent**
-
100 changes: 100 additions & 0 deletions .github/ISSUE_TEMPLATE/planned__specific_support_new_oss.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
---
name: 'Planned: Specific support new OSs'
about: Test compatibility with new OS.
title: Support new OSs - <OS name & version> - <Specific test name>
labels: level/task, request/operational, type/maintenance
assignees: ''

---

# Description
| Related issue | Epic issue |
|---|---|
| Issue number | Issue number|

| Agent tier | Central components support | OS type |
|-|-|-|
| 1/2/3 | Yes/No | New family/Major/Minor |

# Plan

<!-- Uncomment for QA issue
**QA**
- [ ] Add new tests according to the OS's tier.
- [ ] Add proper documentation.
- [ ] Do basic E2E test functionality for all stateful modules according to the OS's tier.
-->

<!-- Uncomment for CPPSERVER issue
**CppServer**
- [ ] **Tier 1 agent**: Make sure that VD works properly according to the OS tier.
- [ ] **Central components**: Add support for the new OS to the GitHub Actions package builder.
- [ ] **Central components**: Smoke test that the package works, including installation, upgrade, and its related functionality.
-->

<!-- Uncomment for INDEXER issue
**Indexer**
- [ ] **Central components**: Add support for the new OS to the GitHub Actions package builder.
- [ ] **Central components**: Smoke test that the package works, including installation and upgrade.
-->

<!-- Uncomment for DEVOPS minor issue
**DevOps**
- [ ] Update the allocator images.
- [ ] Update AMI, OVA, or Docker images if needed.
-->

<!-- Uncomment for DEVOPS major/new family issue
**DevOps**
- [ ] **Central components**: Manually allocate two different accessible machines with the new OS. This is the first step for everything else.
- [ ] **No central components**: Deploy an All In One (in our featured OS, probably Amazon Linux) and allocate an accessible machine with the new OS to test the agent. This is the first step for everything else.
- [ ] **Central components**: Review/test the installation assistant using the new OS.
- [ ] Add support in the allocator.
- [ ] Adapt Puppet.
- [ ] Adapt Ansible.
- [ ] Update AMI, OVA, or Docker images if needed.
-->

<!-- Uncomment for DASHBOARD issue
**Dashboard**
- [ ] **Central components**: Add support for the new OS to the GitHub Actions package builder.
- [ ] **Central components**: Smoke test that the package works, including installation and upgrade.
- [ ] Make sure that the agent-related information in the agent list is correct.
- [ ] Test the deployment one-liner for the new OS.
-->

<!-- Uncomment for THREATINTEL issue
**ThreatIntel**
- [ ] Define a plan to support the new OS, particularly with regard to SCA policies.
-->

<!-- Uncomment for AGENT issue
- [ ] Smoke test that the package works, including installation, upgrade, and its related tier functionality.
- [ ] Add support for the new OS to the GitHub Actions package builder.
**Agent**
Requested testing code:
:white_circle: Requested.
:black_circle: Not requested.
Result code:
:green_circle: Completed: Test finished with success.
:red_circle: Completed with failures.
:yellow_circle: Completed with known issues.
- **Requested checks by tier:**
|| Tier 1 | Tier 2 | Tier 3 | Result |
|-|-|-|-|-|
| **Log collection - System events** | :white_circle: | :white_circle: | :white_circle: | |
| **Log collection - Log files** | :white_circle: | :white_circle: | :white_circle: | |
| **Log collection -Command execution** | :white_circle: | :white_circle: | :white_circle: | |
| **FIM - Scheduled** | :white_circle: | :white_circle: | :white_circle: | |
| **FIM - Realtime** | :white_circle: | :black_circle: | :black_circle: | |
| **FIM - Whodata** | :white_circle: | :black_circle: | :black_circle: | |
| **SCA** | :white_circle: | :white_circle: | :black_circle: | |
| **Inventory** | :white_circle: | :white_circle: | :white_circle: | |
| **Active response** | :white_circle: | :white_circle: | :black_circle: | |
| **Remote upgrade** | :white_circle: | :black_circle: | :black_circle: | |
| **Command monitoring** | :white_circle: | :white_circle: | :black_circle: | |
| **Wodles** | :white_circle: | :black_circle: | :black_circle: | |
-->
54 changes: 54 additions & 0 deletions .github/ISSUE_TEMPLATE/release_manual_tests.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
---
name: Release Candidate - Manual tests
about: Report the results after running manual tests for the specified release.
title: Release [WAZUH VERSION] - Manual tests - [TEST NAME]
labels: release/4.3.0
assignees: ''

---

The following issue aims to run the specified test for the current release candidate, report the results, and open new issues for any encountered errors.

## Test information
| | |
|-------------------------|--------------------------------------------|
| **Test name** | |
| **Category** | |
| **Deployment option** | |
| **Main release issue** | |
| **Release candidate #** | |

## Test description
ADD TEST DESCRIPTION HERE

## Test report procedure

All test results must have one of the following statuses:
| | |
|---------------------------------|--------------------------------------------|
| :green_circle: | All checks passed. |
| :red_circle: | There is at least one failed result. |
| :yellow_circle: | There is at least one expected failure or skipped test and no failures. |

Any failing test must be properly addressed with a new issue, detailing the error and the possible cause.

An extended report of the test results must be attached as a ZIP or TXT file. Please attach any documents, screenshots, or tables to the issue update with the results. This report can be used by the auditors to dig deeper into any possible failures and details.

## Conclusions

All tests have been executed and the results can be found [here]().

| | | | |
|----------------|-------------|---------------------|----------------|
| **Status** | **Test** | **Failure type** | **Notes** |
| | | | |

All tests have passed and the fails have been reported or justified. Therefore, I conclude that this issue is finished and OK for this release candidate.

## Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.

All checks from below must be accepted in order to close this issue.

- [ ] MODULE OWNER
- [ ] EXTRA REVIEWER
29 changes: 29 additions & 0 deletions .github/ISSUE_TEMPLATE/scheduled__support_new_oss.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
name: 'Scheduled: Support new OSs'
about: Regularly check for new OS versions during their prerelease stages of development.
title: 'Week # - Support new OSs'
labels: level/task, request/operational, type/maintenance
assignees: ''

---

|Week|Previous issue|
|---|---|
|21|https://github.com/wazuh/wazuh/issues/23311|

## Description

This issue aims to regularly check for new OS versions during their prerelease stages of development.

Each OS must have one of the following check statuses:

| Check | Description |
|:-:|--------------------------------------------|
| 🟡 | New OS version has been found. |
| ⚫ | No new OS version has been found. |

Check the current table:

| OS family | Version | Release date | Estimated frequency | Links | Check | Support OS issue |
|-|-|-|-|-|:-:|-|
| Ubuntu (**_SAMPLE, DELETE_**) | 24.10 | 05/23/2024 | Semester | [Releases](https://wiki.ubuntu.com/Releases) / [Pre-releases](https://wiki.ubuntu.com/Releases#:~:text=mailing%20list.-,Future,-Version)| 🟡 | https://github.com/wazuh/wazuh/issues/23579 |
80 changes: 80 additions & 0 deletions .github/ISSUE_TEMPLATE/system_tests.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
---
name: Release Candidate - System tests
about: Report the results after running system tests.
title: Release [WAZUH VERSION] - [STAGE] - System tests
labels: level/task, type/test
assignees: ''

---

The following issue aims to run all `system tests` for the current release candidate, report the results, and open new issues for any encountered errors.

## System tests information
| | |
|--------------------------------------|--------------------------------------------|
| **Main release candidate issue** | |
| **Version** | |
| **Release candidate #** | |
| **Tag** | |
| **Previous system tests issue** | |

## Instructions
To run tests in an AWS EC2 virtual environment, the following requirements will need to be met:

| Environment | EC2 |
|------------------------------|-------------------------------------------|
|Basic_cluster |Ubuntu 22.04.2 LTS C5.XLarge 15GB SSD |
|Big_cluster_40_agents |Ubuntu 22.04.2 LTS T3.Large 60GB SSD |
|Agentless_cluster |Ubuntu 22.04.2 LTS C5a.XLarge 30GB SSD |
|Four_manager_disconnected_node|Ubuntu 22.04.2 LTS T3.Large 30GB SSD |
|One_manager_agent |Ubuntu 22.04.2 LTS T3.Large 30GB SSD |
|Manager_agent |Ubuntu 22.04.2 LTS T3.Large 30GB SSD |
|Enrollment_cluster |Ubuntu 22.04.2 LTS T3.Large 30GB SSD |
|Basic_environment |Ubuntu 22.04.2 LTS T3.Large 30GB SSD |


These requirements should be requested to the @wazuh/devel-devops team via https://github.com/wazuh/internal-devel-requests.

For further information, check https://github.com/wazuh/wazuh-qa/tree/master/tests/system/README.md

## Test report procedure
All individual test checks must be marked as:
| | |
|---------------------------------|--------------------------------------------|
| Pass | The test ran successfully. |
| Xfail | The test was expected to fail and it failed. It must be properly justified and reported in an issue. |
| Skip | The test was not run. It must be properly justified and reported in an issue. |
| Fail | The test failed. A new issue must be opened to evaluate and address the problem. |

All test results must have one the following statuses:
| | |
|---------------------------------|--------------------------------------------|
| :green_circle: | All checks passed. |
| :red_circle: | There is at least one failed check. |
| :yellow_circle: | There is at least one expected fail or skipped test and no failures. |

Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the `Fixes` section of the current release candidate main issue.

Any expected fail or skipped test must have an issue justifying the reason. All auditors must validate the justification for an expected fail or skipped test.

An extended report of the test results must be attached as a zip or txt. This report can be used by the auditors to dig deeper into any possible failures and details.

## Conclusions

<!--
All tests have been executed and the results can be found [here]().
| | | | |
|----------------|-------------|---------------------|----------------|
| **Status** | **Test** | **Failure type** | **Notes** |
| | | | |
All tests have passed and the fails have been reported or justified. I therefore conclude that this issue is finished and OK for this release candidate.
-->

## Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.

All checks from below must be accepted in order to close this issue.

- [ ] @wazuh/devel-qa-release
Loading

0 comments on commit 3895d9d

Please sign in to comment.