-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1796930: [release-4.3] baremetal: make provisioning networks more configurable #3034
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
Conversation
This change adds 4 new options to the baremetal platform:
- ProvisioningNetworkInterface
- ProvisioningNetworkCIDR
- ProvisioningDHCPExternal
- ProvisioningDHCPRange
This makes the provisioning network more configurable, by allowing users
to specify a specific network interface, which network, and settings for
whether the cluster should provide DHCP services on the provisioning
network, or if it will be managed externally. If we will provide DHCP
services on the network, the user may further customize which range to
use.
This change is a prerequisite to a number of additional high-priority
work items for the baremetal IPI platform, including single-stack IPv6
provisioning, external DHCP support, and end-to-end seamless deployment
without a manually created config map.
Co-authored-by: Ian Main <[email protected]>
Co-authored-by: Stephen Benjamin <[email protected]>
|
/hold Need to verify what's in the 4.3 ironic containers first |
|
@stbenjam: This pull request references Bugzilla bug 1796930, which is invalid:
Comment DetailsIn response to this:
Instructions 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. |
|
/close Not required in 4.3. |
|
@stbenjam: Closed this PR. DetailsIn response to this:
Instructions 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. |
|
/reopen |
|
@stbenjam: Reopened this PR. DetailsIn response to this:
Instructions 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. |
|
@stbenjam: This pull request references Bugzilla bug 1796930, which is invalid:
Comment DetailsIn response to this:
Instructions 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. |
|
/bugzilla refresh |
|
@stbenjam: This pull request references Bugzilla bug 1796930, which is invalid:
Comment DetailsIn response to this:
Instructions 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. |
|
/bugzilla refresh |
|
@stbenjam: This pull request references Bugzilla bug 1796930, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions 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. |
|
/hold cancel |
|
/hold Actually still need to check ironic containers in 4.3 |
|
Can you link to the corresponding master PR(s)? |
|
@stbenjam: This pull request references Bugzilla bug 1796930, which is valid. DetailsIn response to this:
Instructions 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. |
|
@stbenjam: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson 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 |
|
@stbenjam still held so not currently being considered for cherry pick approval |
|
@stbenjam looks like we need to cherry-pick openshift/ironic-image#45 to unblock this? |
|
Since we are about to get iPXE images for ironic-image, I was going to get that in ironic-image and backport all the IPv6 things together. |
|
skipping this one for approval this week anyway due to the number of other changes already accepted. |
|
@stbenjam Are we moving forward with this PR? |
|
No - this was tightly coupled to the IPv6 work in the ironic-image, and we're not going to split this out. Only in 4.4+ will provisioning networks be configurable. /close |
|
@stbenjam: Closed this PR. DetailsIn response to this:
Instructions 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. |
Backport of #2895
This change adds 4 new options to the baremetal platform:
This makes the provisioning network more configurable, by allowing users
to specify a specific network interface, which network, and settings for
whether the cluster should provide DHCP services on the provisioning
network, or if it will be managed externally. If we will provide DHCP
services on the network, the user may further customize which range to
use.
This change is a prerequisite to a number of additional high-priority
work items for the baremetal IPI platform, including single-stack IPv6
provisioning, external DHCP support, and end-to-end seamless deployment
without a manually created config map.
Co-authored-by: Ian Main [email protected]
Co-authored-by: Stephen Benjamin [email protected]