You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks the integration testing of WAVE_04 for range42/range42-playbooks. Companion umbrellas exist on range42/range42, range42/range42-ansible_roles-debug-devkit, and range42/range42-catalog.
Workflow
range42 uses a wave-based release train workflow :
internal fix or contributor PR -> land on dev -> integration test -> PR dev to main -> release
WAVE_04 spans range42/range42-playbooks, range42/range42, range42/range42-ansible_roles-debug-devkit, and range42/range42-catalog.
Cycle A - 2026-06-05 (open) - 5 sub-issues opened (4 landed on dev + 1 tracking in progress)
Scope on this repo : 3 new training-oriented scenarios drafted on dev (misp_lab, dev_deployer_ui_lab, kunai_lab), plus a status table chore on the playbooks README to mark them as in progress. Each scenario is a first draft built on top of the demo_lab mechanism (pre-flight, wait-for-SSH, Docker baseline, vmbr142 IP allocation) and will be refined iteratively as the training catalogue takes shape. The training-doc pipeline tracking issue is opened only and the actual work (credentials JSON schema + Quarto-based renderer role) will be scheduled for upcoming cycles of WAVE_04.
Status : 4 sub-issues definitively landed on dev (#70, #71, #72, #75), 1 tracking sub-issue in progress (#66), all awaiting integration testing on a real Proxmox.
Cycle B - 2026-06-14 (2 sub-issues + 1 chore landed on feat-scenario-bundles-refactor)
Scope this cycle : shared bundles framework PoC on the feat-scenario-bundles-refactor branch. Three bundles created and validated end-to-end on demo_lab_bundles against hv-bw (PLAY RECAP failed=0 across the deployed VMs : admin stack + Wazuh server + Wazuh agents on clients + vuln-box family).
The bundles ship under bundles/ and mirror the catalog convention (admin/software.install.<name>, core/proxmox/configure/<topic>). All are imported by the isolated test scenario scenarios/demo_lab_bundles/ so existing scenarios (demo_lab, bs2, bs4, bs6) are untouched.
Status : 2 sub-issues + 2 cleanup commits landed on feat-scenario-bundles-refactor. End-to-end validation green on demo_lab_bundles against hv-bw. Awaiting decision on the next refactor direction (host-baseline bundle / install/* wire-in / demo_lab migration) before opening a PR to dev.
Closure
Closed once the dev to main release PR for range42-playbooks is merged. PR body should include Closes for any companion sub-issues opened during the wave.
Merge order across WAVE_04 : TBD - will be decided once the cohort scope is firmed up.
tracking: WAVE_04 integration testing in
devThis issue tracks the integration testing of WAVE_04 for
range42/range42-playbooks. Companion umbrellas exist onrange42/range42,range42/range42-ansible_roles-debug-devkit, andrange42/range42-catalog.Workflow
range42 uses a wave-based release train workflow :
WAVE_04 spans range42/range42-playbooks, range42/range42, range42/range42-ansible_roles-debug-devkit, and range42/range42-catalog.
Cycle A - 2026-06-05 (open) - 5 sub-issues opened (4 landed on dev + 1 tracking in progress)
Scope on this repo : 3 new training-oriented scenarios drafted on
dev(misp_lab,dev_deployer_ui_lab,kunai_lab), plus a status table chore on the playbooks README to mark them as in progress. Each scenario is a first draft built on top of the demo_lab mechanism (pre-flight, wait-for-SSH, Docker baseline, vmbr142 IP allocation) and will be refined iteratively as the training catalogue takes shape. The training-doc pipeline tracking issue is opened only and the actual work (credentials JSON schema + Quarto-based renderer role) will be scheduled for upcoming cycles of WAVE_04.Sub-issues :
devyet, work scheduled for upcoming cycles)Status : 4 sub-issues definitively landed on
dev(#70, #71, #72, #75), 1 tracking sub-issue in progress (#66), all awaiting integration testing on a real Proxmox.Cycle B - 2026-06-14 (2 sub-issues + 1 chore landed on feat-scenario-bundles-refactor)
Scope this cycle : shared bundles framework PoC on the
feat-scenario-bundles-refactorbranch. Three bundles created and validated end-to-end ondemo_lab_bundlesagainsthv-bw(PLAY RECAPfailed=0across the deployed VMs : admin stack + Wazuh server + Wazuh agents on clients + vuln-box family).The bundles ship under
bundles/and mirror the catalog convention (admin/software.install.<name>,core/proxmox/configure/<topic>). All are imported by the isolated test scenarioscenarios/demo_lab_bundles/so existing scenarios (demo_lab,bs2,bs4,bs6) are untouched.Sub-issues :
bundles/admin/software.install.wazuh(Wazuh server stack, 7 plays)bundles/admin/software.install.wazuh-agent(Wazuh agent install, 1 play, split from server to mirror the catalog umbrella role convention)bundles/core/proxmox/configure/templates/ubuntu_noble(12 Ubuntu Noble templates : nano / micro / small / medium / large) with the bs2-grade idempotence layer (per-templateqm config | grep template:probe, lock-wait,delegate_to: -cli) and the apt-update + finalize pipelinebundles/core/proxmox/configure/vm-bootstrap(single shared playbook for the 5-step clone + lock-wait + tag + cloudinit + start + post-boot wait pattern)global_*varsglobal_vm_ci_dns_ips,global_vm_ci_netmask,global_vm_ci_ip_gw,global_vm_net_virtio_bridge)Cleanup commits (no new sub-issue, follow-up to #89 + #100) :
Status : 2 sub-issues + 2 cleanup commits landed on
feat-scenario-bundles-refactor. End-to-end validation green ondemo_lab_bundlesagainsthv-bw. Awaiting decision on the next refactor direction (host-baseline bundle / install/* wire-in / demo_lab migration) before opening a PR todev.Closure
Closed once the
dev to mainrelease PR forrange42-playbooksis merged. PR body should includeClosesfor any companion sub-issues opened during the wave.Merge order across WAVE_04 : TBD - will be decided once the cohort scope is firmed up.
Failure list