← ClaudeAtlas

ocpvirt-setuplisted

Phase 0 of the sales.demos OpenShift Virtualization demo — take a bare RHDP environment to demo-ready in one command: install OpenShift Virtualization, apply the AAP configuration, then prove it by building and timing a real VM. Checks prerequisites, confirms the cluster is reachable, then runs playbooks/setup.yml. TRIGGER when: the user has a new or rebuilt RHDP environment, asks to set one up or prepare it for the ocpvirt demo, says OpenShift Virtualization or KubeVirt is missing, hits a missing kubevirt.io API, or asks to install CNV. SKIP: if the environment is already set up and the user wants to create demo VMs — that is ocpvirt-provision — or only wants to re-check readiness, which is ocpvirt-new-env.
ericcames/sales.demos · ★ 1 · DevOps & Infrastructure · score 67
Install: claude install-skill ericcames/sales.demos
# ocpvirt-setup ## Most of this runs from AAP now (#330) `Cluster Day 0` is a workflow: install OpenShift Virtualization, link the RHEL 9 CIS L1 golden image, then verify the environment really works. Use it once `config.yml` has run for the environment. **`config.yml` is still the one laptop command**, and it has to be: it creates the job templates, so it cannot be one of them. Run it first, then everything else is buttons — which is also the point, since work in a terminal is invisible to a customer and work in AAP is the demo. `setup.yml` stays as the single-command laptop path. This is additive. Phase 0. Takes a bare RHDP "Ansible Product Demo" environment to demo-ready in **one command**. This skill contains **no logic**. All the work is in [`playbooks/setup.yml`](../../../playbooks/setup.yml), which imports three playbooks in order. The same playbooks run from AAP job templates with survey answers mapped to the same variable names. See `CLAUDE.md` → *Skills and playbooks*. ## What it does **1. Install OpenShift Virtualization** (`install_cnv.yml`) 1. Creates the `openshift-cnv` namespace and its OperatorGroup. 2. Subscribes to `kubevirt-hyperconverged` on the `stable` channel from the `redhat-operators` catalog. 3. Waits for the operator ClusterServiceVersion to reach `Succeeded`. 4. Creates the `HyperConverged` CR, pointing CDI scratch space at the cluster's default StorageClass (discovered at run time). 5. Waits for `HyperConverged` to report `Available