Comment 6 for bug 1650678

Yes, you got it. We need the ability to have VMs with different, user-specified dns_domains all on the same provider network.

Conrad Kimball
Associate Technical Fellow
Chief Architect, Enterprise Cloud Services
Application Infrastructure Services / Global IT Infrastructure / Information Technology & Data Analytics
<email address hidden>
P.O. Box 3707, Mail Code 7M-TE
Seattle, WA  98124-2207
Bellevue 33-11 bldg, office 3A6-3.9
Mobile:  425-591-7802

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Akihiro Motoki
Sent: Thursday, March 30, 2017 12:43 PM
To: Kimball, Conrad <email address hidden>
Subject: [Bug 1650678] Re: [RFE] Allow specifying dns_domain when creating a port

I am not sure the bug just suggests that dns_domain is used for tagging purpose.

In a provider network deployment scenarios, all VMs belong to a single network. There may be a case where some set of VMs belong to service A with foo.example.net and other set of VMs belong to service B with bar.example.net. In such case, dns_domain per port might be needed. I think it is a valid use case.

We already allows users to assign both dns_domain and dns_name for a specific floating IP, so I am not sure there is a reason we do not allow dns_domain per port.

Note that if the self-service network model is used, you can define neutron network per service (i.e. business unit in the bug description) and assign dns-domain for individual neutron network.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1650678

Title:
  [RFE] Allow specifying dns_domain when creating a port

Status in neutron:
  Triaged

Bug description:
  When creating a port, allow specifying a dns_domain instead of
  inheriting dns_domain from the network.

  In our enterprise we do not tie DNS domains to networks - we use the
  DNS domain of a VM port to indicate the business unit or the
  infrastructure function of a VM. Thus our data center networks
  routinely have VM ports with a variety of DNS domains, with the choice
  of DNS domain left to the person deploying the VM instance.

  To carry this practice into OpenStack, we will extend our data center
  network into OpenStack using a provider network, and we need the
  ability to create ports on that network with various dns_names
  furnished by the VM creator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1650678/+subscriptions