Ludus Deployment

Ludus is the preferred professional range path because it is built for reusable cyber ranges on Proxmox and already uses automation concepts that match AIT's needs.

Profiles

R2 ships three Ludus configs:

• lab/range/ludus/profiles/compact.yml
• lab/range/ludus/profiles/standard.yml
• lab/range/ludus/profiles/full-split.yml

standard is the default and is mirrored by lab/range/ludus/range-config.example.yml.

Workflow

1. Install Ludus and build the Linux templates required by your environment.
2. Choose a profile config.
3. Adjust template names, VLANs, and role collection names for your Ludus host.
4. Set the range config.
5. Deploy the range.
6. Connect with WireGuard and run the operator script from the operator VM.

lab/range/scripts/check_range.sh --profile standard
lab/range/scripts/deploy_ludus.sh --profile standard
ludus range logs -f
ludus range status

Expected Result

• Ludus creates the VM topology.
• Ansible roles install AIT components and deterministic services.
• The operator VM can run the same ait demo and ait workbench flows used by Docker L6.
• The cockpit shows VM-specific flows and the same transcript/graph/proof artifacts.

Notes

R2 provides profile configs, matching Ansible inventories, and operator scripts. The role tasks remain intentionally small and idempotent while the lab services continue to mature; they establish the deployable range shape without hiding the infrastructure choices.