Bug 1042550

Summary:	[RFE][neutron]: Provider Networking - upstream SLAAC support
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED ERRATA	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	low	Docs Contact:
Priority:	high
Version:	unspecified	CC:	chrisw, ihrachys, lpeer, markmc, mlopes, nyechiel, oblaut, tfreger, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac
Whiteboard:	upstream_milestone_juno-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-neutron-2014.2-7.el7ost	Doc Type:	Release Note
Doc Text:	This update enables OpenStack Networking (neutron) to create a Provider Network that uses an upstream device with Router Advertisement multicasts. As a result, instances are able to use Stateless Address Autoconfiguration (SLAAC) to configure their IPv6 networking.	Story Points:	---
Clone Of:
Clones:	1171969 (view as bug list)		Environment:
Last Closed:	2015-02-09 15:00:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1083891, 1171969

Description RHOS Integration 2013-12-13 00:19:57 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac.

Description:

It should be possible to create a Provider Network in Neutron, that uses an upstream switch or router that advertises RA's - so that instances can use SLAAC to configure their IPv6 networking, while still utilizing the Neutron APIs for security group rules.

Specification URL (additional information):

None

Comment 3 Nir Yechiel 2014-03-09 09:31:36 UTC

Updating based on upstream milestone

Comment 4 Nir Yechiel 2014-07-15 12:30:18 UTC

Spec is approved. The code is implemented in J2.

Comment 11 errata-xmlrpc 2015-02-09 15:00:11 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0148.html