Create gs-baremetal Agent-Based Install workflow#76365
Draft
sg-rh wants to merge 1 commit intoopenshift:mainfrom
Draft
Create gs-baremetal Agent-Based Install workflow#76365sg-rh wants to merge 1 commit intoopenshift:mainfrom
sg-rh wants to merge 1 commit intoopenshift:mainfrom
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sg-rh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Agent-Based Installation (ABI) workflow for bare metal (metal-redhat-gs)
Adds step-registry support for Agent-Based Installation on bare metal using the metal-redhat-gs cluster profile, without a bastion. Day 0/1/2 behavior is driven by YAML script blocks supplied via job env vars (or secrets), not hardcoded in the step registry.
Changes
Each step loads BuildCustomScriptsFromYAML.sh from OpenShift-LP-QE--Tools and executes the script blocks defined in the corresponding env var. Script URL can be overridden with OCP_ABI_TOOLS_SCRIPT_URL. Base image: baremetal-qe-base.
Documentation
gs-baremetal/README.md – Describes the workflow, the three script env vars, YAML Scripts: format, optional env vars, Day 0 example, hosts.yaml expectations, and conventions (install-status.txt, host-id.txt, virtual_media_mount_failure). Removed the Chisel LP CP/DP section (relay setup stays in job/secret).
How to use
Set OCP__ABI__DAY0_SCRIPTS_YAML, OCP__ABI__DAY1_SCRIPTS_YAML, and OCP__ABI__DAY2_SCRIPTS_YAML in the job (or via secret). Each value is YAML with a top-level Scripts: key (array or map of script blocks). See the Day 0 example in gs-baremetal/README.md and the step ref docs for details.