Comment 11 for bug 1650678

Please go ahead, Miguel, Reedip, or any others that are interested.

I simply submitted the enhancement request; I'm not in a position to recommend or decide how the work gets done.

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 Miguel Lavalle
Sent: Thursday, April 06, 2017 4:30 PM
To: Kimball, Conrad <email address hidden>
Subject: [Bug 1650678] Re: [RFE] Allow specifying dns_domain when creating a port

@Conrad,

I know the relevant code very well. If you don't find a resource to implement, I can do it. Alternatively, if you find a resource, I can guide that person. Let me know how you want to proceed

--
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