We are unable to implement this, sorry. Wish we could, but we are OpenStack newbies without the skills to do so, and we have corporate hurdles to contributing to open source :-(
I will feed this to the company we are getting our commercially supported distribution from, if that helps.
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 5:34 PM
To: Kimball, Conrad <email address hidden>
Subject: [Bug 1650678] Re: [RFE] Allow specifying dns_domain when creating a port
This is approved in the driver meeting.
@Conrad, do you plan to implement it, or do we need any volunteer?
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.
Good news - thank you.
We are unable to implement this, sorry. Wish we could, but we are OpenStack newbies without the skills to do so, and we have corporate hurdles to contributing to open source :-(
I will feed this to the company we are getting our commercially supported distribution from, if that helps.
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 5:34 PM
To: Kimball, Conrad <email address hidden>
Subject: [Bug 1650678] Re: [RFE] Allow specifying dns_domain when creating a port
This is approved in the driver meeting.
@Conrad, do you plan to implement it, or do we need any volunteer?
http:// eavesdrop. openstack. org/meetings/ neutron_ drivers/ 2017/neutron_ drivers. 2017-03- 30-22.01. log.html# l-144
** Tags removed: rfe
** Tags added: rfe-approved
-- /bugs.launchpad .net/bugs/ 1650678
You received this bug notification because you are subscribed to the bug report.
https:/
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: /bugs.launchpad .net/neutron/ +bug/1650678/ +subscriptions
https:/