Bug 1042476

Summary:	[RFE][neutron]: Allow multiple subnets on gateway port for router
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ofer Blaut <oblaut>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	chrisw, markmc, nyechiel, yeylon
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port
Whiteboard:	upstream_milestone_next upstream_status_slow-progress upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 11:06:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 22:23:55 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/allow-multiple-subnets-on-gateway-port.

Description:

Currently, only a single subnet can be assigned to a router's gateway port (really, all ports whether an internal port or gateway port). This blueprint intends to provide a means of supporting a dual-stack arrangement on a router's gateway port by allowing both an IPv6- and an IPv4-based subnet to be associated with a router. We will disallow more that two subnets, and exclude allowing 2 IPv4 or 2 IPv6 subnets.

A parallel Blueprint is to be provided that allows SLAAC generated IPv6 addresses on a gateway port for RA sent from upstream routers.

Specification URL (additional information):

None

Comment 3 Nir Yechiel 2014-02-26 11:51:39 UTC

Upstream milestone was changed to 'next'. No longer targeted to Icehouse

Comment 4 Nir Yechiel 2015-03-19 11:06:36 UTC

This RFE was automatically opened to track status of upstream development. At this point we see no reason to keep track of this in Red Hat bugzilla, thus closing it.