Skip to content

Add support for self schedule preferred models#793

Merged
openshift-merge-bot[bot] merged 3 commits intoredhat-performance:mainfrom
mcornea:self_sched_script
Apr 9, 2026
Merged

Add support for self schedule preferred models#793
openshift-merge-bot[bot] merged 3 commits intoredhat-performance:mainfrom
mcornea:self_sched_script

Conversation

@mcornea
Copy link
Copy Markdown
Collaborator

@mcornea mcornea commented Apr 8, 2026

No description provided.

@openshift-ci openshift-ci bot requested review from jtaleric and rsevilla87 April 8, 2026 07:15
@mcornea mcornea force-pushed the self_sched_script branch 3 times, most recently from ca75009 to dfb7027 Compare April 8, 2026 14:01
WIPE_VALUE="false"; \
else \
WIPE_VALUE="true"; \
fi; \
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I am understanding this correctly, we have to pass a WIPE_VALUE to the make command in order to override hardware wiping for the workshop?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's an option in the make prompt and it defaults to false to avoid the wipe for a quick release of the nodes.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see what happened while testing, I actually pulled the PR before that prompt was added. Maybe post workshop we should default wipe to true because the workshop is only leveraging pre-wiped hardware and afterwards folks will need to remember to wipe there hardware for the best possible result.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm still testing with wipe set to false as I'm seeing some issue with the generated inventory.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I increased the retries to wait for the inventory to be ready: https://github.com/redhat-performance/jetlag/pull/793/changes#diff-7acd08e373d2f171069baaaf232424cc24bd9371f81d30fa062f461137206736R47

but it makes it more difficult to test before the workshop since the machines allocated with wipe false are not reachable.

Signed-off-by: Marius Cornea <mcornea@redhat.com>
@mcornea mcornea force-pushed the self_sched_script branch from dfb7027 to 9ad2c84 Compare April 8, 2026 15:08
Copy link
Copy Markdown
Member

@akrzos akrzos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ran the same scenario, by reusing the same hardware after releasing a cloud. Works great!

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akrzos

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved label Apr 9, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit d604286 into redhat-performance:main Apr 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants