Add Docker-based compatibility test kit for external validation

Introduces a containerized test kit that enables external teams to
easily validate xcp-ng compatibility on their own hardware without
complex setup requirements.
The compat_kit module provides a straightforward, self-contained
environment for running compatibility tests, lowering the barrier to
entry for third-party validation.

Signed-off-by: Gaëtan Lehmann <gaetan.lehmann@vates.tech>

Author: glehmann

.dockerignore

@@ -0,0 +1,5 @@
+.venv
+.git
+.jj
+.*cache
+__pycache__

.gitignore

@@ -4,3 +4,5 @@ data.py
 vm_data.py
 /scripts/guests/windows/id_rsa.pub
 .envrc
+*.egg-info
+*.log

README.md

@@ -128,6 +128,10 @@ This command installs the dependency locally and update the `uv.lock` file.
 The lock file allows `uv` to install the dependencies at the exact same versions
 on all the environments.
 
+## Server Compatibility Testing Kit
+
+For automated testing of XCP-ng on new hardware, see the **Compatibility Test Kit** at [compat_kit/README.md](compat_kit/README.md).
+
 ## Other requirements
 * XCP-ng hosts that you can ssh to using an SSH key, non-interactively
 * VM images suited to what the tests want. Some tests want a linux VM with SSH, available to import as an OVA over HTTP, for example.

compat_kit/Dockerfile

@@ -0,0 +1,17 @@
+FROM fedora:43
+RUN dnf install -y --setopt=install_weak_deps=False \
+    curl \
+    git \
+    iputils \
+    netcat \
+    openssh-clients \
+    sshpass \
+    uv && \
+    dnf clean all
+WORKDIR /app
+COPY pyproject.toml uv.lock .python-version /app/
+RUN uv sync --no-dev --frozen
+COPY ./ /app/
+ENV PATH="/app/.venv/bin:$PATH"
+ENTRYPOINT ["uv", "run", "--no-dev", "./compat_kit/entrypoint.py"]
+

compat_kit/README.md

@@ -0,0 +1,97 @@
+# XCP-ng Server Compatibility Test Kit v1
+
+## Preamble
+
+This is version 1 of a server compatibility test kit for XCP-ng.
+
+It is a work in progress, based on existing test suites in the XCP-ng project, and will evolve over
+time towards a comprehensive automated test kit.
+
+Version 1 introduces **Docker containerization** of the test runner, automating much of the manual
+setup previously required. The entire workflow—from SSH key generation and VM image download to
+multi-phase test execution and cleanup—is now orchestrated within a container.
+
+## Requirements
+
+- **Docker** installed on your machine (or Docker Desktop for macOS/Windows)
+- **Hosts to test:**
+  - At least one x86_64 server with XCP-ng installed (the release you want to test),
+    [updated with the latest updates](https://xcp-ng.org/docs/updates.html)
+  - A disk for the system, and a separate, empty disk for testing
+  - Ideally, a second identical host joined to the first as a pool of two hosts (for storage
+    migration and live migration tests)
+  - Network connectivity for management interface
+  - SSH access available (root user; password-based authentication will be used to install a
+    temporary testing key)
+
+## Security Notes
+
+- The container runs as a **non-root user** (nobody) for security
+- SSH keys are generated in a temporary directory inside the container and are automatically
+  cleaned up on exit
+- The SSH root password is never stored; it's only used to install the temporary public key
+- Temporary SSH keys are removed from remote hosts on exit (unless `--skip-cleanup` is used)
+
+## Quick Start
+
+Interactive mode (recommended):
+
+```bash
+docker run -it --rm -v ${PWD}:/app/logs ghcr.io/xcp-ng/xcp-ng-tests/compat-kit
+```
+
+You will be prompted for:
+
+- IP/hostname of the pool master
+- IP/hostname of a second host (optional; press Enter to skip)
+- SSH root password (used only for initial key installation, never stored)
+
+Alternatively, provide arguments on the command line:
+
+```bash
+docker run -it --rm \
+  -v ${PWD}:/app/logs \
+  ghcr.io/xcp-ng/xcp-ng-tests/compat-kit \
+  --master-host 192.168.1.10 \
+  --second-host 192.168.1.11
+```
+
+After the container completes (or exits), test log files will be in the current directory:
+
+- `test_kit_1.log` — Single-host tests
+- `test_kit_2.log` — Two-host pool tests — only if a second host was provided
+- `test_kit_3.log` — Xen-level tests
+
+Open these files locally with your text editor or log viewer.
+
+## Command-line options
+
+```text
+--master-host MASTER_HOST
+                      IP or hostname of the pool master
+--second-host SECOND_HOST
+                      IP or hostname of the second host (optional, for pool tests)
+--password PASSWORD   SSH root password (if not provided, will be prompted)
+--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}
+                      Logging level (default: INFO)
+--vm-image-url VM_IMAGE_URL
+                      URL to the VM image to download (default: TODO)
+--skip-cleanup        Don't remove SSH keys from hosts on exit
+--dry-run             Print what would be done without making any changes
+--non-interactive     Don't prompt for missing parameters; fail if required arguments are missing
+--mgmt-network MGMT_NETWORK
+                      MGMT network description (will be set in data.py NETWORKS)
+```
+
+## Development
+
+### Building the Docker image
+
+From the xcp-ng-tests repository root:
+
+```bash
+docker build -t ghcr.io/xcp-ng/xcp-ng-tests/compat-kit -f compat_kit/Dockerfile .
+```
+
+This creates an image with all dependencies pre-installed, including the xcp-ng-tests suite and
+test runner tools.

compat_kit/__init__.py

@@ -0,0 +1 @@
+"""XCP-ng Compatibility Test Kit."""