ocpvirt-demolisted

Re-run the demo content on Linux or Windows VMs that ALREADY EXIST: register or patch them, install and configure the web server, rescan for CIS compliance, and turn the demo URL from a 503 into a real page. Launches the Linux Day 1 - Repair or Windows Day 1 - Repair job template in AAP, whichever the VM is. TRIGGER when: the user asks to re-run, repair or reconfigure the demo content, says the demo URL returns 503 or does not load, wants a page tweak applied, or is recovering from a failed step on a VM that is still up. SKIP: if no VMs exist yet — a build from nothing is the Linux Day 1 - 0 Workflow or Windows Day 1 - 0 Workflow, reached through ocpvirt-provision — or if the environment itself has never been set up, which is ocpvirt-setup.
ericcames/sales.demos · ★ 1 · DevOps & Infrastructure · score 67

Install: claude install-skill ericcames/sales.demos

# ocpvirt-demo Takes demo VMs that exist and makes them a demo again — Linux or Windows. `terraform/ocpvirt` gives every demo VM a Service and a Route (#29 for Linux, #340 for Windows), so a public URL exists from the moment it is provisioned — and returns **503**, because nothing is serving on port 80. This is the other half of that story. ## First: which OS? **Ask, or look, before doing anything else.** The two chains share a shape and share nothing else — different group, different credential, different job template, different reason the middle step exists. | | Linux | Windows | |---|---|---| | AAP inventory group | `linuxweb` | `windemo` | | Job template | `Linux Day 1 - Repair` | `Windows Day 1 - Repair` | | Machine credential | `Sales Demos - Linux Machine` | `Sales Demos - Windows Machine` | | Reached over | SSH, port 22 | WinRM/HTTPS, port 5986 | | Step 1 | Register to the Red Hat CDN | Patch from Windows Update | | Web server | httpd | IIS | | Compliance | OpenSCAP scan | Configuration verification | If it is not obvious which exists, ask the cluster rather than guessing: ``` mcp__openshift-<env>__resources_list kubevirt.io/v1 VirtualMachine ``` VMs are named `{role}-{os}-{index}` since #389: `*-lnx-*` is Linux, `*-win-*` is Windows, and the leading word is the workload role (`web`, `db`, `app`). `web-lnx-1` and `web-win-1` can exist at once — they have separate Terraform state since #301 — and so can several members of one farm, and several roles, each with