plugins/hcp/skills/hcp-create-openstack/SKILL.md
Use this skill when you need to deploy HyperShift clusters on OpenStack infrastructure with proper flavor selection and network configuration
npx skillsauth add openshift-eng/ai-helpers hcp-create-openstackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides implementation guidance for creating HyperShift clusters on OpenStack, handling OpenStack-specific requirements including credentials, networking, and flavor selection.
This skill is automatically invoked by the /hcp:generate openstack command to guide the OpenStack provider cluster creation process.
Required Parameters:
OpenStack Credentials
🔹 **OpenStack Credentials**: Path to OpenStack credentials file?
- Usually clouds.yaml format
- Example: /home/user/.config/openstack/clouds.yaml
External Network
🔹 **External Network ID**: OpenStack external network UUID?
- Required for floating IP allocation
- Find with: openstack network list --external
Flavor Selection
🔹 **Node Flavor**: Choose instance flavor:
- m1.large (4 vCPU, 8GB RAM) - Standard workloads
- m1.xlarge (8 vCPU, 16GB RAM) - Performance workloads
- [default: m1.large]
Standard Configuration:
hypershift create cluster openstack \
--name openstack-cluster \
--namespace openstack-cluster-ns \
--openstack-credentials-file /path/to/clouds.yaml \
--openstack-external-network-id <external-network-uuid> \
--openstack-node-flavor m1.large \
--base-domain example.com \
--pull-secret /path/to/pull-secret.json \
--release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi
External network with ID "<uuid>" not found.
List available external networks:
openstack network list --external
Ensure network has proper routing configuration.
Flavor "m1.large" not available in this OpenStack deployment.
List available flavors:
openstack flavor list
Choose appropriate flavor for your workload requirements.
tools
Analyze a JIRA issue and create a pull request to solve it. Use when the user wants to implement a fix or feature described in a Jira issue, push a branch, and open a draft PR.
development
Use when a deeper level of code review is requested. Multi-agent panel code review with specialist reviewers and forced runtime reproducers for all BLOCKING bug findings. Optionally posts to GitHub/GitLab as a PENDING review.
development
Review agentic documentation — verify claims locally against source code first, then use chai-bot for cross-repo and cross-functional verification
development
Use this skill when debugging a failed Prow CI job.