Bug 1044272

Summary:	[RFE][neutron]: Support IPv6 DHCPv6 Stateless mode in dnsmasq
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:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	chrisw, ihrachys, lpeer, markmc, mlopes, nyechiel, oblaut, tfreger, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateless
Whiteboard:	upstream_milestone_juno-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-neutron-2014.2-7.el7ost	Doc Type:	Enhancement
Doc Text:	With this enhancement, Tenant networks can now be created that use the 'dnsmasq' process inside the DHCP agent to serve additional configuration to IPv6 DHCP clients, including support for IPv6 stateless subnets.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 15:00:16 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

Description RHOS Integration 2013-12-18 02:25:06 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateless.

Description:

The intent of this blueprint is to allow dnsmasq to work in DHCPv6 Stateless mode, i.e. sending out RA to tenant network with ALO bits set to 1 and M bit set to 0. As the result, VM will rely on RA for IPv6 address assignment and use dnsmasq as DHCPv6 server for optional information. At the same time, VM will continue to rely on RA for default route.

Specification URL (additional information):

None

Comment 3 Nir Yechiel 2014-03-24 09:01:53 UTC

Updating based on BP milestone.

Comment 10 errata-xmlrpc 2015-02-09 15:00:16 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