MGMT-22968: Add infrastructure-only mode and Landing Zone VM support#1846
MGMT-22968: Add infrastructure-only mode and Landing Zone VM support#1846eliorerz wants to merge 2 commits intoopenshift-metal3:masterfrom
Conversation
This commit adds a new 'infra_only' Makefile target and support for
Landing Zone VMs to dev-scripts. This enables users to create
baremetal-like test infrastructure (VMs, networks, BMC emulation)
without deploying an OpenShift cluster.
Changes:
1. New 'infra_only' Makefile target
- Runs 'requirements' and 'configure' steps only
- Stops before cluster deployment (build_installer, ironic, etc.)
- Useful for testing external deployment tools (GoRI Lab, custom installers)
2. Landing Zone VM support
- Added NUM_LANDINGZONE environment variable (default: 0)
- Added landingzone flavor with configurable specs:
* LANDINGZONE_MEMORY (default: 8192 MB)
* LANDINGZONE_DISK (default: 60 GB)
* LANDINGZONE_VCPU (default: 4)
- Landing Zone VM acts as deployment host with dual network access
3. Network topology fix for Landing Zone use case
- Worker VMs: cluster network only (BMC network removed)
- Landing Zone VM: both BMC and cluster networks
- Ensures proper network isolation for testing scenarios
- Only applies when NUM_LANDINGZONE > 0
4. Documentation updates
- Added "Infrastructure-Only Mode" section to README
- Added "Deploying with Landing Zone VMs" section to README
- Documented network topology and use cases
Use case: Testing external deployment tools that need infrastructure
without cluster deployment, such as GoRI Lab for bare metal OpenShift
installations.
Backward compatibility: All existing targets (default, agent, assisted)
work unchanged. New variables default to 0 (no Landing Zone VMs).
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @eliorerz. Thanks for your PR. I'm waiting for a openshift-metal3 member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
FYI @carbonin |
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
/approve AFAIK what you call "landing zone vm" is called "bastion host" and "landing zone" itself is "everything in my cloud subscription what can possibly interact with each other. But it's just a naming so whatever works for you, works |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mkowalski 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 |
openshift-ci
bot
added
the
approved
|
/retest |
…workManager
When MANAGE_BR_BRIDGE=y and the cluster network is managed by libvirt
(not NetworkManager), the `nmcli con del` command fails because the
connection doesn't exist in NetworkManager.
This causes make infra_only to exit with error, breaking CI pipelines.
Fix: Suppress error if NetworkManager connection doesn't exist:
sudo nmcli con del ${BAREMETAL_NETWORK_NAME} 2>/dev/null || true
This allows the script to continue successfully whether the NetworkManager
connection exists or not.
|
/retest |
|
/retest |
|
/retest |
|
@eliorerz: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
5 participants
This commit adds a new
infra_onlyMakefile target and support for Landing Zone VMs to dev-scripts. This enables users to create baremetal-like test infrastructure (VMs, networks, BMC emulation) without deploying an OpenShift cluster.Changes:
New
infra_onlyMakefile targetLanding Zone VM support
Network topology fix for Landing Zone use case
Documentation updates
Use case: Testing external deployment tools that need infrastructure without cluster deployment, such as GoRI Lab for bare metal OpenShift installations.
Backward compatibility: All existing targets (default, agent, assisted) work unchanged. New variables default to 0 (no Landing Zone VMs).