HyperShift OpenStack Provider
About
This skill enables developers to deploy HyperShift clusters on OpenStack infrastructure by handling OpenStack-specific requirements. It provides implementation guidance for proper flavor selection, network configuration, and credential management. Use this skill when creating OpenStack provider clusters through the `/hcp:generate openstack` command.
Quick Install
Claude Code
Recommended/plugin add https://github.com/openshift-eng/ai-helpersgit clone https://github.com/openshift-eng/ai-helpers.git ~/.claude/skills/HyperShift OpenStack ProviderCopy and paste this command in Claude Code to install this skill
Documentation
HyperShift OpenStack Provider
This skill provides implementation guidance for creating HyperShift clusters on OpenStack, handling OpenStack-specific requirements including credentials, networking, and flavor selection.
When to Use This Skill
This skill is automatically invoked by the /hcp:generate openstack command to guide the OpenStack provider cluster creation process.
Prerequisites
- OpenStack CLI configured with appropriate credentials
- OpenStack project with sufficient quotas
- External network configured for floating IPs
- HyperShift operator installed and configured
OpenStack Provider Overview
OpenStack Provider Peculiarities
- Requires OpenStack credentials: Must have valid clouds.yaml or environment variables
- Floating IP networks needed: External network access for cluster API
- Flavor selection critical: Instance flavors affect performance and cost
- Custom images may be required: RHCOS images for worker nodes
- Network topology affects routing: Proper network configuration essential
Implementation Steps
Step 1: Interactive Parameter Collection
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]
Step 2: Generate Command
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
Error Handling
External Network Not Found
External network with ID "<uuid>" not found.
List available external networks:
openstack network list --external
Ensure network has proper routing configuration.
Flavor Not Available
Flavor "m1.large" not available in this OpenStack deployment.
List available flavors:
openstack flavor list
Choose appropriate flavor for your workload requirements.
See Also
GitHub Repository
Related Skills
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
