Bug 1661235 - [Docs] OSP13 - Add a section on IPv6 in OVN listing the current status of IPv6
Summary: [Docs] OSP13 - Add a section on IPv6 in OVN listing the current status of IPv6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: James Smith
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-20 14:35 UTC by Numan Siddique
Modified: 2022-08-10 16:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-05 21:22:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-6520 0 None None None 2022-08-10 16:15:58 UTC

Description Numan Siddique 2018-12-20 14:35:15 UTC 
Description of problem:

IPv6 support in OVN has few missing features. It would be good to add a section about IPv6 here - https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/networking_with_open_virtual_network/

***
OSP13 with OVN supports creating IPv6 networks. However there are a couple of issues
 
  1. Prefix delegation is not yet supported in OVN. So the user has to create private IPv6 subnets with the appropriate GUA prefixes manually.

  2.  There is no default route added by networking-ovn to route the traffic to gateway IP of the IPv6 public network subnet. Without this, the North-South routing will not work if the VM wants to send a N/S packet with the IPv6 destination IP which doesn't belong to the IPv6 public subnet. - https://bugs.launchpad.net/networking-ovn/+bug/1808753

****


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.