-
Notifications
You must be signed in to change notification settings - Fork 200
Add ability to inject static ips into install-config #1297
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
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Requires metal3-io/metal3-dev-env#820 Same comment applies here. We could plumb this with a new vm_setup_vars.yaml that sets up a static IP configuration for the network. That may be a better approach. Let me know. |
|
/retest |
| # Note we only do this in the case where METAL3_DEV_ENV is | ||
| # unset, to enable developer testing of local checkouts | ||
| git reset ee1b2fec44e22700c8d250d5e0e371e3fd0aba17 --hard | ||
| #git reset 67afcb3315b44e2c68121493a819819966e588a2 --hard |
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.
This needs to be removed - note you can use METAL3_DEV_ENV to reference a local source checkout for testing with latest metal3-dev-env :)
| fi | ||
|
|
||
| if [[ "$PROVISIONING_NETWORK_PROFILE" == "Disabled" ]]; then | ||
| if [[ "$PROVISIONING_NETWORK_PROFILE" == "Disabled" || -n "$STATIC_IPS" ]]; then |
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.
I think we should support both virtualmedia and PXE paths now?
| bridge: "{{ provisioning_network_name }}" | ||
| forward_mode: bridge | ||
|
|
||
| virsh_dhcp_enabled: "{{ lookup('env', 'DHCP_ENABLED')|default('', true) }}" |
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.
I don't think we need this, since the environment variable is already respected in the defaults ref metal3-io/metal3-dev-env#879 ?
| config: | ||
| - destination: 0.0.0.0/0 | ||
| next-hop-address: ${PROVISIONING_HOST_EXTERNAL_IP} | ||
| next-hop-interface: ${PROVISIONING_NETWORK_INTERFACE} |
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.
We normally would have the default route on the External network, is the change to the provisioning network intentional?
|
@imain any updates on this? It'd be useful to get this done so we can attempt reproduces for bugs (for example https://bugzilla.redhat.com/show_bug.cgi?id=2036677) - I think other than the comments already added, we'll also need to inject static configuration for the bootstrap VM? It'd be great to either create a new periodic CI job too based on this work, or switch the config of one of the existing ones to provide coverage. |
|
Note there are also a couple of comments on metal3-io/metal3-dev-env#879 which need resolving, then we can merge that and update the dev-scripts pin |
| netmask_v4: "{{ baremetal_network_cidr_v4|ipaddr('netmask') }}" | ||
| address_v6: "{{ baremetal_network_cidr_v6|nthhost(1)|default('', true) }}" | ||
| prefix_v6: "{{ baremetal_network_cidr_v6|ipaddr('prefix') }}" | ||
| dhcp_enabled: "{{ virsh_dhcp_enabled|bool }}" |
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.
Another option is we conditionally define dhcp_range* - then we won't need the new metal3-dev-env flag since the <dhcp stanza is already skipped when the range is omitted
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.
I pushed metal3-io/metal3-dev-env#902 which means we can just set the dhcp_range variables to an empty list, which avoids the need for a new variable
|
I pushed #1336 which handles the bootstrap VM ip configuration, which we'll need for this |
Set up a STATIC_IPS configuration flag that configures dev-scripts to use static IPs (v4 and/or v6) for the baremetal network. Co-Authored-By: Caleb Boylan <[email protected]>
|
@imain: PR needs rebase. 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. |
|
@imain: 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. |
|
Closing as this has been handled by #1418 |
Set up a STATIC_IPS configuration flag that configures dev-scripts
to use static IPs (v4 and/or v6) for the baremetal network.
Co-Authored-By: Caleb Boylan [email protected]