Uh oh!
There was an error while loading. Please reload this page.
Add local VM sandbox for testing IPA image changes - #17
Merged
Conversation
Adds a self-contained workflow to validate that changes baked into the IPA ramdisk show up on a booted node, using metal3-dev-env + sushy-tools + libvirt VMs as fake bare-metal hosts — no physical hardware or prod clusters. - ipa-dev/testing-ipa-with-vm-sandbox.md: end-to-end guide (provision a KVM host, stand up metal3-dev-env, build a custom IPA, inject it, boot a node, verify the bake-in) with the gotchas we hit. - ipa-dev/testing-ipa-with-vm.sh: launches a KVM-capable AWS c5.metal host (handles accounts with no default VPC), records created resources. - ipa-dev/cleanup-sandbox.sh: tears down the AWS resources it created. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Phased end-to-end validation plan for the qual flow (clean-wait hold -> install -> enroll -> terminal states -> orchestration -> soak) plus a reproducible walkthrough for building/booting the qual-agent IPA in the metal3 VM sandbox, with the gotchas hit along the way. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
A self-contained workflow to prove that what you bake into the IPA ramdisk
shows up on a booted node, using `metal3-dev-env` + sushy-tools + libvirt VMs
as fake bare-metal hosts — no physical hardware, no real BMCs, no prod clusters.
Why
Validating IPA changes on real hardware is slow and entangled with prod. This
gives a fast, isolated local loop: build a custom IPA from this repo → inject it
→ PXE-boot a VM node → SSH in and confirm the change is present.
Contents (`ipa-dev/`)
stand up metal3-dev-env, build a custom IPA, inject it, boot a node, verify),
including the gotchas hit along the way.
accounts with no default VPC; records created resources for cleanup).
Validated end-to-end: built a marker IPA, injected it into the sandbox's Ironic,
booted a metal3-dev-env node, and confirmed the baked-in file on the running
ramdisk.
🤖 Generated with Claude Code