settingsLogin | Registersettings

[openstack-dev] Changes to DNS integration behavior?

0 votes

We are in the early phases of a project to deploy OpenStack and we face the question of DNS integration when launching a VM instance.

We have found the DNS Integration documentation at http://docs.openstack.org/mitaka/networking-guide/config-dns-int.html, but to our understanding it doesn't do what we want to do.

Where is the best forum for discussing possible changes in this behavior?


Specifically, we do not tie DNS domains to networks - any particular network may have VM ports with a variety of DNS domains, with the choice of DNS domain left to the person deploying the VM instance (we use DNS domains to indicate business unit association, infrastructure function, and so forth).

So we would want the DNS integration to allow specifying both a dnsname and a dnsdomain when creating a port. The documentation link above says this is allowed for floating IPs, but not for ports - ports can specify only a dnsname and always inherit the dnsdomain from the network.

Conrad Kimball
Associate Technical Fellow
Chief Architect, Enterprise Cloud Services
Engineering, Operations & Technology / Information Technology / Core Infrastructure Engineering
conrad.kimball@boeing.comconrad.kimball@boeing.com
P.O. Box 3707, Mail Code 7M-TE
Seattle, WA 98124-2207
Bellevue 33-11 bldg, office 3A6-3.9
Mobile: 425-591-7802


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Dec 12, 2016 in openstack-dev by Kimball,_Conrad (180 points)   1 1 2
retagged Jan 26, 2017 by admin

2 Responses

0 votes

On 12/12/2016 19:52, Kimball, Conrad wrote:
We are in the early phases of a project to deploy OpenStack and we face
the question of DNS integration when launching a VM instance.

We have found the DNS Integration documentation at
http://docs.openstack.org/mitaka/networking-guide/config-dns-int.html,
but to our understanding it doesn’t do what we want to do.

Where is the best forum for discussing possible changes in this behavior?

This would be a change to neutron, so it would their bugs / RFE
process [0]

I added [neutron] to the subject to grab their attention.

0 - http://docs.openstack.org/developer/neutron/policies/blueprints.html


Specifically, we do not tie DNS domains to networks – any particular
network may have VM ports with a variety of DNS domains, with the choice
of DNS domain left to the person deploying the VM instance (we use DNS
domains to indicate business unit association, infrastructure function,
and so forth).

So we would want the DNS integration to allow specifying both a dnsname
and a dns
domain when creating a port. The documentation link above
says this is allowed for floating IPs, but not for ports – ports can
specify only a dnsname and always inherit the dnsdomain from the network.

/Conrad Kimball/

Associate Technical Fellow

Chief Architect, Enterprise Cloud Services

Engineering, Operations & Technology / Information Technology / Core
Infrastructure Engineering

conrad.kimball@boeing.com conrad.kimball@boeing.com

P.O. Box 3707, Mail Code 7M-TE

Seattle, WA 98124-2207

Bellevue 33-11 bldg, office 3A6-3.9

Mobile: 425-591-7802


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Dec 12, 2016 by graham.hayes_at_hpe. (6,780 points)   1 2 2
0 votes

Hi Conrad,

You are correct in your reading of the Neutron DNS integration
documentation. Ports 'inherit' their dns_domain from their network. I
encourage you to submit a RFE (Request for Enhacement) here:
https://bugs.launchpad.net/neutron. Once you file it, I'll track it down
and will make sure it is properly tagged so it gets discussed by the
Neutron drivers team

Best regards

Miguel

On Mon, Dec 12, 2016 at 1:49 PM, Kimball, Conrad conrad.kimball@boeing.com
wrote:

We are in the early phases of a project to deploy OpenStack and we face
the question of DNS integration when launching a VM instance.

We have found the DNS Integration documentation at
http://docs.openstack.org/mitaka/networking-guide/config-dns-int.html,
but to our understanding it doesn’t do what we want to do.

Where is the best forum for discussing possible changes in this behavior?


Specifically, we do not tie DNS domains to networks – any particular
network may have VM ports with a variety of DNS domains, with the choice of
DNS domain left to the person deploying the VM instance (we use DNS domains
to indicate business unit association, infrastructure function, and so
forth).

So we would want the DNS integration to allow specifying both a dnsname
and a dns
domain when creating a port. The documentation link above says
this is allowed for floating IPs, but not for ports – ports can specify
only a dnsname and always inherit the dnsdomain from the network.

Conrad Kimball

Associate Technical Fellow

Chief Architect, Enterprise Cloud Services

Engineering, Operations & Technology / Information Technology / Core
Infrastructure Engineering

conrad.kimball@boeing.com

P.O. Box 3707, Mail Code 7M-TE

Seattle, WA 98124-2207

Bellevue 33-11 bldg, office 3A6-3.9

Mobile: 425-591-7802 <(425)%20591-7802>


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Dec 14, 2016 by Miguel_Lavalle (2,460 points)   1 4
...