On 7 Dec 2012, at 16:53, Andy Doan andy.doan@linaro.org wrote:
On 12/07/2012 09:26 AM, Dave Pigott wrote:
On 7 Dec 2012, at 11:03, Dave Pigott dave.pigott@linaro.org wrote:
Hi all,
Just so I'm belt and braces on this, I'm working up the dhcpd.conf and dnsmasq.conf files ready for Monday. I'll send these out so that you can all peruse, approve/check my working.
Why both dnsmasq.conf and dhcpd.conf? Is dhcpd.conf a backup plan in case dnsmasq.conf doesn't work for us?
To save connectivity disruption time, dhcpd.conf is for control, so that I can switch all the nodes over to statically served IP addresses based on their MAC addresses before switching over to dnsmasq on gateway. Then, when I switch over go back round and restart networking on all nodes so they get refreshed with the /16 based config. I've fleshed out the BP to try to explain the steps.
My other question (likely me being dense). We have:
dhcp-range=192.168.2.0,192.168.255.254,255.255.0.0,10m dhcp-range=192.168.1.0,192.168.1.255,static,255.255.0.0
Does this mean this dhcp server will just hand out addresses on 192.168.2.x except for nodes specifically listed like:
dhcp-host=68:b5:99:be:54:8c,control,192.168.1.10
This is why I need feedback. :)
According to the documentation I've read, this means that 192.168.2...255.x will be dhcp served, and because of the "static" declaration in the second, this reserves that range for fixed addresses served based on MAC addresses. Which reminds me: I also need to add some steps to the BP for reconfiguring the cloud.
?
And if that assumption is right. I guess that then frees up enough of the 192.168.1.x that OpenStack's IP allocation will *just work*?
With the probable exception of the netmask as configured on the control node. And adding the 192.168.0.x IP pool.
Dave