adoptium / adoptium/infrastructure
Ansible request for OpenJDK container detection tests (Linux x86_64)
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
It would be very useful to have specific test machines for testing the OpenJDK container detection code. See https://github.com/adoptium/aqa-tests/pull/4147 and https://github.com/adoptium/aqa-tests/issues/4143
Delete as appropriate from this list:
- Request for new playbook addition
Details:
Container tests in OpenJDK require the following setup (in addition to the usual setup for aqavit test machines on Linux):
- Installed container engine (`docker` or `podman`) with SELinux or similar turned off
- cgroups v1 with swap accounting turned on (`swapaccount=1` kernel command line).
- cgroups v2 setup based on [this ansible playbook](https://github.com/jerboaa/openjdk-cgroupv2-setup) which sets up cgroups v2 suitable for testing. For example RHEL 9 machines would come with cg v2 by default.
Ideally, there'd be both, test machines with cg v1 and cg v2 so that testing can be run on both systems. Suggested labels would be `openjdk.dev.container.cg1` and `openjdk.dev.container.cg2`.
Contributor guide
Research direction
Start with the linked openjdk-cgroupv2-setup playbook and the related aqа-tests pull request and issue, then inspect the repository's usual Linux aqavit machine setup. Done means suitable x86_64 test machines exist for both cgroups v1 and v2, with a container engine, the required kernel settings, and the proposed labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, docker, linux
- Domain
- devops, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100