When using FlatDHCPManager the ips are not recycled

On current trunk ips should be recycled after 10 minutes. Flat_dhcp doesn't use the dns command from the database. Dnsmasq functions as a dns server and it uses whatever is set on the network host. If you would like dnsmasq to use a different dns server you can use the following flag in nova-network:
--dns_server=<dns_server>

Vish

On Feb 24, 2011, at 8:44 AM, arturo lorenzo wrote:

> New question #146727 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/146727
>
> DHCP is not reassigning (back to first ip) after last ip was used when FlatDHCPManager as shown on dnsmasq.
> Both dnsmasq programs show: --dhcp-range=192.168.1.96,static,120s when I have specified --fixed_range=192.168.1.96/28 and --network_size=16 and --fixed_ip_disassociate_timeout=60
> I think the --dhcp-range should be: 192.168.1.96,192.168.1.111.
> Also the --flat_network_dns parameter is ignored, I have to enter the dns via mysql cmd.
> Thanks for the help
>
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

So that means that the dnsmasq for Flat_dhcp does not provide DHCP server services? it means that I have to provide a DHCP server on that network?

Dnsmasq supplies dhcp server services as well.

On Feb 28, 2011, at 7:55 AM, arturo lorenzo wrote:

> Question #146727 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/146727
>
> Status: Answered => Open
>
> arturo lorenzo is still having a problem:
> So that means that the dnsmasq for Flat_dhcp does not provide DHCP
> server services? it means that I have to provide a DHCP server on that
> network?
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Thanks Vish, that fixed the problem.