Add deployment script for QUADS self-scheduling hw

[mcornea]

Add an interactive deployment script that combines QUADS self-service lab assignment with jetlag OCP deployment by integrating ansible-quads-ssm playbook with jetlag repo.

Features:

• Makefile-driven workflow with phased targets (repos, assignment, inventory, bastion, cluster)
• Interactive configuration prompts for QUADS credentials, OCP version, cluster type (MNO/SNO), and network stack (IPv4/IPv6/dual)
• Automatic r630 server detection to enable iDRAC reset when needed
• Assignment state tracking for resuming failed deployments

jetlag self-sched-deploy - Interactive OCP Deployment

Usage: make [target]

Main targets:
  all, deploy    Full deployment pipeline (prompts for all config upfront)
  configure      Prompt for all configuration parameters

Individual phases (prompt for phase-specific config):
  bootstrap          Setup jetlag Python virtual environment
  repos              Clone/update ansible-quads-ssm repository
  create-assignment  QUADS assignment (prompts for QUADS config)
  inventory          Generate jetlag inventory (prompts for OCP config)
  bastion            Setup bastion node
  cluster            Deploy OCP cluster

Utility targets:
  status               Show current deployment status
  terminate-assignment Terminate QUADS assignment
  clean                Remove generated config and state files
  clean-all            Remove config, state, and cloned repository
  help                 Show this help message

Examples:
  make                     # Full interactive deployment
  make create-assignment   # Run only QUADS assignment
  make inventory           # Run only inventory generation
  make bastion             # Run only bastion setup
  make cluster             # Run only cluster deployment

[josecastillolema]

cc @akrzos @sadsfae @grafuls

[sadsfae]

This is a really great initiative @mcornea only really a minor comment about var usage with internal hostnames. Nice job, this will be super useful!

[sadsfae]

I love that you're consuming this playbook and if it helps we can make a special branch for you that any changes pushed to latest will only be merged if they could not potentially break any usage here (we'd ask for your review), though we do not anticipate any real changes to it at this time - it's mostly feature-complete from its intention of being simple but having most features people need. Perhaps this isn't needed at all but just a suggestion we could entertain if you wanted. Ideally you could just send PR and everyone benefits should usage scope increase overall.

[sadsfae]

Great work @mcornea

[vishnuchalla]

Excited about using this 🚀

[akrzos]

2 small requests on my first attempt running.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: grafuls, sadsfae
Once this PR has been reviewed and has the lgtm label, please ask for approval from akrzos. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment