forked from ovn-org/ovn-kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 0
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
DMM Test TAP #3
Closed
DMM Test TAP #3
Conversation
This file contains 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
Signed-off-by: Or Shoval <oshoval@redhat.com>
Signed-off-by: Or Shoval <oshoval@redhat.com>
To integrate DHCPv4 and DHCPv6 with secondary networks we should parameterize dns server, router and ipv4 mtu. It also add fqdn DHCPv6 option to reach parity with DHCPv4. Signed-off-by: Enrique Llorente <ellorent@redhat.com>
For primary udn layer2 at kubevirt VMs it will configure dhcpv4 with gateway as router and dns service cluster ip as dns_server and dhcpv6 just with dns_server. Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
After activating dhcpv6_stateful at LRP the agnhost alpine container has two IPv6 default gateways pointing to the same interface and resolving to the same mac (so they work the same). This change ensure the test account for that by deleting all of them in the test require it. Signed-off-by: Enrique Llorente <ellorent@redhat.com>
This change create a virt-launcher pod backed up by a pod running NetworkManager with a working DHCP client to test that ovn-k is answering back the ipv4/ipv6 DHCP/NP messages to configure networking. Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Enrique Llorente <ellorent@redhat.com>
Signed-off-by: Or Shoval <oshoval@redhat.com>
Since hostname is populated now via DHCP, we can always use the vmi name in the console expecter. Signed-off-by: Or Shoval <oshoval@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depends on
ovn-org#4750
ovn-org#4708
ovn-org#4773
Deploys kubevirt with managedTap changes and interface name auto detection
What this PR does and why is it needed
Which issue(s) this PR fixes
Fixes #
Special notes for reviewers
How to verify it
Details to documentation updates
Description for the changelog
Does this PR introduce a user-facing change?