Bug 1376026

Summary:	[RFE] Domain assigned to instances is unique for all the OSP infrastructure, each user cannot select its own domain
Product:	Red Hat OpenStack	Reporter:	David Sanz <dsanzmor>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Toni Freger <tfreger>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	amuller, chrisw, ihrachys, molasaga, nyechiel, pablo.iranzo, srevivo
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-18 21:07:26 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:
Bug Depends On:
Bug Blocks:	1381612

Description David Sanz 2016-09-14 13:11:53 UTC

Description of problem:

Domain used to create the FQDN  of the instances in OSP is unique for all the deploy.
It can be changed modifying the parameter dns_domain of the neutron.conf file, but each user (or tenant) cannot select its own domain.

This is a problem when trying to integrate OSP with an External DNS service, because some users wants to assign different domain to each instance, for example, when they are in different tenant, different environment (dev, pre, pro), or any other.

Customer wants to assign domains to the instances, based in a default domain (assigned to the tenant) or a fixed domain for a concrete instance.

Actual results:

The domain assigned to all the instances is the same for all the infrastructure


Expected results:

User want to select a default domain on each tenant, and use it for instances in that tenant if any other domain is not explicitly selected


Additional info:

Comment 3 Ihar Hrachyshka 2017-08-11 18:48:02 UTC

Upstream wise, the implementation lands in Pike. Obviously, it won't be backported to any prior release.