Bug 1434435
| Summary: | [RFE] support IPv6 for address type in subnets(el7.6 guest OSs) | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-provider-ovn | Reporter: | Mor <mkalfon> |
| Component: | provider | Assignee: | Miguel Duarte Barroso <mduarted> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> |
| Severity: | medium | Docs Contact: | Rolfe Dlugy-Hegwer <rdlugyhe> |
| Priority: | medium | ||
| Version: | 1.2.7 | CC: | bugs, danken, mburman, mduarted, msheena, myakove, nusiddiq, rdlugyhe, reliezer, tcarlin |
| Target Milestone: | ovirt-4.3.1 | Keywords: | FutureFeature |
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.3+
mburman: testing_plan_complete+ ylavi: planning_ack+ danken: devel_ack+ mburman: testing_ack+ |
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-provider-ovn-1.2.20 | Doc Type: | If docs needed, set a value |
| Doc Text: |
This feature provides IPv6 address type support for OpenStack Networking API subnets.
IPv6 support was implemented using OVN's native DHCPv6, and cannot be configured from router advertisements.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-13 16:39:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1080725 | ||
|
Description
Mor
2017-03-21 13:49:55 UTC
I suggest to close, the engine should not care for subnets. The provider should support or not support it. The RFE was - and still is - opened on ovirt-provider-ovn. (In reply to Dan Kenigsberg from comment #2) > The RFE was - and still is - opened on ovirt-provider-ovn. Does OVN not support IPv6 or is it the provider? OVN supports it since 2.6. We have never tested this ourselves. This RFE is about consuming this OVN feature by ovirt. Please note there are certain important features like router advertisement (Ra) which are missing from OVN. I am working on supporting RA feature. Main bit https://github.com/openvswitch/ovs/commit/7cc0741ea275977dddf0c80b57a1673d86908656 would be available only in ovs-2.8. UI adjustment was requested in BZ 1670715 Not blocking ovirt-4.3.0 on this, moving to 4.3.1 As per the IPv6 unicast address RFC - [0] - "all subnets using Globally Unique Addresses and ULAs always have the same prefix length of 64 bits". The above impacts the dhcpv6 design protocol in a way that the network prefixes are not sent in the dhcpv6 reply messages, only the IP address in that /64 network prefix. In order to send network prefixes, IPv6 relies on Router Advertisements, which, the chosen solution - as per the feature page, [1] - does not implement. This RFE is thus limited to work if the client's ip addresses belong to a /64 subnets. Since on el8, the default is for dhclient to assign ipv6 host addresses (/128 subnets), this RFE is thus limited to el7 guest OSs. A new RFE will be created to address network prefix configuration through router advertisements. [0] - https://tools.ietf.org/html/rfc5375#section-3 [1] - https://ovirt.org/develop/release-management/features/network/ipv6_subnets.html#ipam-types Verified on - ovirt-provider-ovn-1.2.20-1.el7ev.noarch with rhvm-4.3.2-0.1.el7.noarch vdsm-4.30.10-1.el7ev.x86_64 VMs/guests: rhel7.6 server kernel 3.10.0-957.el7.x86_64 Test flow: 1. Create network with IPv6 subnet via REST API - https://<ovn-provider-fqdn>:9696/v2.0/subnets/ - POST with "ip_version": 6, and ipv6 CIDR 2. Import the ovn network to RHV 4.3.1 - PASS 3. Create 2 VMs with rhel7.6 OS 4. Add vNIC with the ovn network profile to each VM 5. Start both VMs 6. run dhclient -6 <iface> on both VMs - PASS 7. Ping between VMs via the IPv6 subnet addresses - PASS Note, that this RFE is limited to work if the client's ip addresses belong to a /64 subnets. limited to el7 guest OSs. New RFE was requested to address network prefix configuration through router advertisements for rhel8 guests, see BZ 1685983 This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |