Bug 1376026 - [RFE] Domain assigned to instances is unique for all the OSP infrastructure, each user cannot select its own domain
Summary: [RFE] Domain assigned to instances is unique for all the OSP infrastructure, ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks: 1381612
TreeView+ depends on / blocked
 
Reported: 2016-09-14 13:11 UTC by David Sanz
Modified: 2021-03-11 14:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-18 21:07:26 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1650678 0 None None None 2017-08-11 18:45:32 UTC
Red Hat Knowledge Base (Solution) 2623481 0 None None None 2016-09-14 15:45:36 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.