Validate an install-config.yaml file.

Args: config_yaml: The install-config.yaml content as a string

Returns: Validation results with errors and summary

Generate an install-config.yaml for baremetal IPI.

Args: cluster_name: Name of the cluster base_domain: Base domain (e.g., example.com) pull_secret: Pull secret content (JSON string) ssh_key: SSH public key content api_vip: API VIP address ingress_vip: Ingress VIP address hosts: List of baremetal hosts with BMC configuration machine_network_cidr: Machine network CIDR (default: 192.168.1.0/24) cluster_network_cidr: Cluster network CIDR (default: 10.128.0.0/14) service_network_cidr: Service network CIDR (default: 172.30.0.0/16) network_type: Network type (default: OVNKubernetes) control_plane_replicas: Number of master nodes (default: 3) worker_replicas: Number of worker nodes (default: 0)

Returns: Generated install-config as dictionary and YAML string

Get an install-config template.

Args: template_name: Template name (e.g., 'baremetal-ipi-compact', 'baremetal-ipi-ha')

Returns: Template content and metadata

List all available install-config templates.

Returns: List of templates with descriptions

Create a baremetal host entry for install-config.yaml.

Args: name: Host name (e.g., 'master-0') role: Host role ('master' or 'worker') bmc_address: BMC address (e.g., 'redfish://192.168.1.100') bmc_username: BMC username bmc_password: BMC password boot_mac_address: Boot MAC address (e.g., 'aa:bb:cc:dd:ee:ff') root_device_hint: Optional root device hint (e.g., '/dev/sda' or 'wwn')

Returns: Host configuration dictionary ready for install-config.yaml

Test BMC connectivity (Redfish).

Args: bmc_address: BMC address (e.g., 'redfish://192.168.1.100' or 'redfish+https://192.168.1.100') username: BMC username password: BMC password verify_ssl: Whether to verify SSL certificates (default: False)

Returns: Connection test results

Validate BMC addresses for multiple hosts.

Args: hosts: List of host configurations with BMC details Each host should have: name, bmc.address, bmc.username, bmc.password

Returns: Validation results for all hosts

Parse and validate BMC address format.

Args: bmc_address: BMC address (e.g., 'redfish://192.168.1.100:443')

Returns: Parsed BMC address components

Generate a bash script to test BMC connectivity for multiple hosts.

Args: hosts: List of host configurations with BMC details

Returns: Bash script for testing BMC connectivity

Validate CIDR notation.

Args: cidr: CIDR string (e.g., '192.168.1.0/24')

Returns: Validation result

Check if an IP address is within a CIDR range.

Args: ip_address: IP address to check cidr: CIDR range

Returns: Check result

Check if two networks overlap.

Args: cidr1: First CIDR cidr2: Second CIDR

Returns: Overlap check result

Validate VIP (Virtual IP) configuration.

Args: api_vip: API VIP address ingress_vip: Ingress VIP address machine_network_cidr: Machine network CIDR

Returns: Validation results

Generate DNS configuration for the cluster.

Args: cluster_name: Cluster name base_domain: Base domain api_vip: API VIP address ingress_vip: Ingress VIP address hosts: Optional JSON string of hosts list. Each host should have 'name' and 'ip' keys. Example: '[{"name": "master-0", "ip": "10.1.235.25"}, {"name": "master-1", "ip": "10.1.235.26"}]'

Returns: Required DNS records and validation commands including A and PTR records for hosts

Calculate cluster network capacity.

Args: cluster_cidr: Cluster network CIDR (e.g., '10.128.0.0/14') host_prefix: Host prefix - subnet size per node (e.g., 23)

Returns: Capacity calculations (max nodes, IPs per node, etc.)

Generate a network diagram for the cluster.

Args: cluster_cidr: Cluster (pod) network CIDR service_cidr: Service network CIDR machine_cidr: Machine network CIDR api_vip: API VIP ingress_vip: Ingress VIP

Returns: Network diagram

Validate complete network configuration for overlaps and validity.

Args: cluster_cidr: Cluster network CIDR service_cidr: Service network CIDR machine_cidr: Machine network CIDR api_vip: Optional API VIP (required for HA) ingress_vip: Optional Ingress VIP (required for HA)

Returns: Comprehensive validation results

Check if openshift-install binary is available.

Args: install_dir: Optional installation directory to check for local binary

Returns: Binary existence check results

Extract openshift-install binary from a release image.

Args: release_image: OpenShift release image URL (e.g., 'quay.io/openshift-release-dev/ocp-release:4.17.0-x86_64') output_dir: Directory to extract installer to (default: current directory)

Returns: Extraction results and next steps

Create Kubernetes manifests from install-config.yaml.

Args: install_dir: Installation directory containing install-config.yaml installer_path: Path to openshift-install binary (default: 'openshift-install')

Returns: Manifest creation results

Prepare cluster installation command.

This tool doesn't actually start the installation (which can take 30-60 minutes), but provides the command to run.

Args: install_dir: Installation directory installer_path: Path to openshift-install binary (default: 'openshift-install') log_level: Log level (debug, info, warn, error)

Returns: Installation command and information

Prepare cluster destroy command.

This tool provides the command to destroy the cluster. Use with caution - this will delete the entire cluster!

Args: install_dir: Installation directory installer_path: Path to openshift-install binary (default: 'openshift-install')

Returns: Destroy command and information

Get cluster installation status.

Args: install_dir: Installation directory

Returns: Installation status and progress

Get recent installation log entries.

Args: install_dir: Installation directory lines: Number of recent lines to retrieve (default: 50)

Returns: Recent log entries