Bug 2102749

Summary:	[RFE] Support DNS domains at a network level in ML2/OVN
Product:	Red Hat OpenStack	Reporter:	Elvira <egarciar>
Component:	openstack-neutron	Assignee:	Elvira <egarciar>
Status:	ASSIGNED ---	QA Contact:	Eran Kuris <ekuris>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	18.0 (Zed)	CC:	astupnik, chrisw, scohen
Target Milestone:	---	Keywords:	FutureFeature, Triaged
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:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Elvira 2022-06-30 14:36:05 UTC

Right now, we set a single domain name per deployment, stated in the neutron
configuration file. However, there are use cases where it is useful to provide
more granularity to DNS, like at a network or port level where the dns_domain
attribute exists. The goal of this RFE is to support DNS domains at a network
level just in the ML2/OVN driver by adding a new extension.
This is a feature that has been requested by customers.

There are several use cases for this:
* In a multitenant environment, different users working on different projects
  use common hostnames for their VMs, which leads to a FQDN conflict. Users
  don’t have to know the hostnames other VMs have, so they could generate an
  unexpected FQDN clash.
* In a multitenant environment, users working in an application with different
  stages might want to re-use hostnames and make a distinction on the domain.
  Example: app001.uat.example.com (for UAT) vs app001.prd.example.com (for
  Production) both have the same hostname.

Additional info upstream:
https://review.opendev.org/c/openstack/neutron-specs/+/832658
https://bugs.launchpad.net/neutron/+bug/1960850