-
Notifications
You must be signed in to change notification settings - Fork 1.5k
baremetal: make provisioning network optional #3929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
baremetal: make provisioning network optional #3929
Conversation
|
Skipping CI for Draft Pull Request. |
|
/cc @hardys Interested in getting some early feedback on this. There's some unresolved issues, but control plane deploys most of the way. More notes in openshift-metal3/dev-scripts#1069 about using this. |
data/data/bootstrap/baremetal/files/usr/local/bin/startironic.sh.template
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
openshift/machine-api-operator#632 adds this
04d0b99 to
892e098
Compare
|
Small nit noticed but otherwise lgtm |
a1e18c8 to
629a519
Compare
|
/lgtm |
data/data/bootstrap/baremetal/files/usr/local/bin/startironic.sh.template
Outdated
Show resolved
Hide resolved
docs/user/metal/install_ipi.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personaly i think Unmanaged mode should have been names TFTPOnly instead because Umanaged imples tftp and no dhcp is very apparent.
Since the enhancement is already merged and seems like other APIs are also merged I do not know if we can back it out now but I would have liked more clearer names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unmanaged is clear to me, but I think the naming ship has sailed, with a merged enhancement and various changes already done.
629a519 to
b056cff
Compare
8a5d1fb to
ef1bf05
Compare
|
/lgtm |
abhinavdahiya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya 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 |
|
/test e2e-metal-ipi |
1 similar comment
|
/test e2e-metal-ipi |
|
/retest |
|
e2e-metal-ipi passed and openshift/machine-api-operator#632 landed so I think this is good to go - I checked the prow history for the failing jobs and they seem to be unstable atm, e.g there were issues with openstack after the latest RHCOS bump etc. /hold cancel |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/hold |
ef1bf05 to
fe2803e
Compare
|
/lgtm |
fe2803e to
3bc7b9f
Compare
This implements the enhancement request that makes the provisioning network optional. It introduces a new platform configuration called "provisioningNetwork" that takes 3 possible values: managed, unmanaged, and disabled. The "unmanaged" option replaces the external DHCP flag that was previously used. When the network is set to "disabled," it is expected that users use virtualmedia configuration. We will deploy no DHCP/TFTP provisioning services for a user to use.
3bc7b9f to
25bc23e
Compare
|
Wait, let's make sure e2e-metal-ipi passes. /hold |
|
/lgtm |
|
@stbenjam: 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/test-infra repository. I understand the commands that are listed here. |
|
/hold cancel |
This implements the enhancement request that makes the provisioning
network optional. It introduces a new platform configuration called
"provisioningNetwork" that takes 3 possible values: managed, unmanaged,
and disabled. The "unmanaged" option replaces the external DHCP flag
that was previously used.
When the network is set to "disabled," it is expected that users use
virtualmedia configuration. We will deploy no DHCP/TFTP provisioning
services for a user to use.