Skip to content
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
wants to merge 13 commits into from
Closed

DMM Test TAP #3

wants to merge 13 commits into from

Conversation

oshoval
Copy link
Owner

@oshoval oshoval commented Oct 10, 2024

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?


Signed-off-by: Or Shoval <oshoval@redhat.com>
oshoval and others added 10 commits October 14, 2024 14:45
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants