Bug 1322086

Summary: [Docs] [Director] IPv6 is not supported for tenant network tunnel endpoints
Product: Red Hat OpenStack Reporter: Ian Pilcher <ipilcher>
Component: documentationAssignee: Martin Lopes <mlopes>
Status: CLOSED CURRENTRELEASE QA Contact: Radek Bíba <rbiba>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: adahms, ipilcher, yeylon
Target Milestone: gaKeywords: Documentation
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-13 04:56:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ian Pilcher 2016-03-29 18:51:14 UTC
Section 2.4.1 of the IPv6 Networking for the Overcloud shows IPv6 addresses for the tenant network tunnel endpoints:

  TenantNetworkVlanID: 202
  TenantNetCidr: 'fd00:fd00:fd00:3000::/64'
  TenantAllocationPools: [{'start': '2001:db8:fd00:3000::10', 'end': '2001:db8:fd00:3000:ffff:ffff:ffff:fffe'}]

This will not work, as the version of Open vSwitch in RHEL does not support this.  TenantNetCidr and TenantAllocationPools should still use IPv4.

Comment 2 Ian Pilcher 2016-03-29 20:12:33 UTC
Also, the subnets/allocation pools have some issues:

* ExternalAllocationPools isn't actually within the ExternalNetCidr (remember
  that 2001:db8::/64 effectively means 2001:0db8:0000:0000::/64)

* InternalApiNetCidr (and its associated allocation pool) should be within the 
  locally unique namespace, not globally unique.

* Storage and storage management allocation pools are not within their
  associated subnets

Comment 3 Andrew Dahms 2016-03-30 04:53:38 UTC
Assigning to Martin for review.

Comment 4 Martin Lopes 2016-03-30 05:25:31 UTC
Reviewing...

Comment 11 Andrew Dahms 2016-04-13 04:56:11 UTC
This content is now live on the Customer Portal.

Closing.