Re: [openstack-dev] [TripleO] dns for overcloud nodes

2014-08-07 Thread Giulio Fidente

On 08/07/2014 01:32 PM, Jan Provaznik wrote:

Hi,
by default we don't set nameserver when setting up neutron subnet used
by overcloud nodes, then nameserver points to the machine where
undercloud's dnsmasq is running.

I wonder if we should not change *default* devtest setup to allow dns
resolving not only for local network but for internet? Proper DNS
resolving is handy e.g. for package update scenario.

This would mean:

a) set explicitly nameserver when configuring neutron subnet (as it's
done for network in overcloud [1])


I'd +1 this one

We allow for customization of the OC gateway [1] so it seems reasonable 
to me to just add the config bits for customization of the OC dns servers


1. 
https://github.com/openstack/tripleo-incubator/blob/master/scripts/devtest_undercloud.sh#L325

--
Giulio Fidente
GPG KEY: 08D733BA

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


[openstack-dev] [TripleO] dns for overcloud nodes

2014-08-07 Thread Jan Provaznik

Hi,
by default we don't set nameserver when setting up neutron subnet used 
by overcloud nodes, then nameserver points to the machine where 
undercloud's dnsmasq is running.


I wonder if we should not change *default* devtest setup to allow dns 
resolving not only for local network but for internet? Proper DNS 
resolving is handy e.g. for package update scenario.


This would mean:

a) set explicitly nameserver when configuring neutron subnet (as it's 
done for network in overcloud [1])


or

b) set forwarding dns server for dnsmasq [2]

Any thoughts?

Thanks, Jan


[1]: 
https://github.com/openstack/tripleo-incubator/blob/master/scripts/setup-neutron#L53

[2]: https://github.com/openstack/neutron/blob/master/etc/dhcp_agent.ini#L67

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