settingsLogin | Registersettings

[Openstack-operators] DNS searchdomains for your instances?

0 votes

Hello all,

Wondering how you guys are handling the dns searchdomains for your instances in your internal cloud. Currently we are updating the network metadata template, on each compute node, to include the dns-search-domains options. We (Josh Harlow) is working on implement the new network template that nova created (in liberty) and are trying to get this added. Currently nova/neutron doesn't support any option to specify this metadata/information anywhere. I see some work on the neutron side to allow setting of extra dhcp-opts network wide (currently only allowed on a port) [1] [2]. But once that gets merged, then changes need to be made on the nova side to pull that extra data into the network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
asked Jun 20, 2016 in openstack-operators by Kris_G._Lindgren (7,740 points)   1 5 10

3 Responses

0 votes

Each tenant in our neutron network has their own subnet and each subnet
sets its own dns rules (see pic).

https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0

On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren klindgren@godaddy.com
wrote:

Hello all,

Wondering how you guys are handling the dns searchdomains for your
instances in your internal cloud. Currently we are updating the network
metadata template, on each compute node, to include the dns-search-domains
options. We (Josh Harlow) is working on implement the new network template
that nova created (in liberty) and are trying to get this added. Currently
nova/neutron doesn't support any option to specify this
metadata/information anywhere. I see some work on the neutron side to
allow setting of extra dhcp-opts network wide (currently only allowed on a
port) [1] [2]. But once that gets merged, then changes need to be made on
the nova side to pull that extra data into the network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 20, 2016 by David_Medberry (8,000 points)   1 4 5
0 votes

and of course that was the WRONG picture....

https://www.dropbox.com/s/wxe9e9nu5cqgx9m/Screenshot%202016-06-20%2013.17.02.png?dl=0

On Mon, Jun 20, 2016 at 1:18 PM, David Medberry openstack@medberry.net
wrote:

Each tenant in our neutron network has their own subnet and each subnet
sets its own dns rules (see pic).

https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0

On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren klindgren@godaddy.com
wrote:

Hello all,

Wondering how you guys are handling the dns searchdomains for your
instances in your internal cloud. Currently we are updating the network
metadata template, on each compute node, to include the dns-search-domains
options. We (Josh Harlow) is working on implement the new network template
that nova created (in liberty) and are trying to get this added. Currently
nova/neutron doesn't support any option to specify this
metadata/information anywhere. I see some work on the neutron side to
allow setting of extra dhcp-opts network wide (currently only allowed on a
port) [1] [2]. But once that gets merged, then changes need to be made on
the nova side to pull that extra data into the network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 20, 2016 by David_Medberry (8,000 points)   1 4 5
0 votes

Yea we set the DNS servers per network as well. I am actually asking about the search domain, IE what FQDN's should be appended to non-fqdn queries, to a lookup the ip of a short name.

IE: if searching for the shortname of: somevm. If you had a search domain of domain1.com, domain2.net, and domain3.org – it would try each of those domain names in order until it found: somevm..
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: medberry@gmail.com on behalf of David Medberry openstack@medberry.net
Date: Monday, June 20, 2016 at 1:19 PM
To: "Kris G. Lindgren" klindgren@godaddy.com
Cc: "openstack-oper." openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] DNS searchdomains for your instances?

and of course that was the WRONG picture....

https://www.dropbox.com/s/wxe9e9nu5cqgx9m/Screenshot%202016-06-20%2013.17.02.png?dl=0

On Mon, Jun 20, 2016 at 1:18 PM, David Medberry openstack@medberry.net wrote:
Each tenant in our neutron network has their own subnet and each subnet sets its own dns rules (see pic).

https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0

On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren klindgren@godaddy.com wrote:
Hello all,

Wondering how you guys are handling the dns searchdomains for your instances in your internal cloud. Currently we are updating the network metadata template, on each compute node, to include the dns-search-domains options. We (Josh Harlow) is working on implement the new network template that nova created (in liberty) and are trying to get this added. Currently nova/neutron doesn't support any option to specify this metadata/information anywhere. I see some work on the neutron side to allow setting of extra dhcp-opts network wide (currently only allowed on a port) [1] [2]. But once that gets merged, then changes need to be made on the nova side to pull that extra data into the network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Jun 20, 2016 by Kris_G._Lindgren (7,740 points)   1 5 10
...