[pve-devel] internal dhcp server, where to put dhcp configuration ?

[Alexandre DERUMIER]

>>Compute the ranges should not be a problem (looks simple to me). 

We also need to keep in mind that bridge ip (dhcp server ip) must be in the same network than vms ip, to be able to work.

(so maybe don't allow netmask on vmconfig, and use the netmask from dhcp server)



>>We already had a solution for cluster wide lease in May? Although, we only 
>>have static IP assignment (from VM config), so I am not sure if we really need 
>>that? 
We had talked about dhcp-script=.. option, which allow to run custom script to manage lease.
But indeed, if we use only static ip, I don't think we need it.


----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: "pve.proxmox.com" <pve-devel at pve.proxmox.com> 
Envoyé: Samedi 24 Août 2013 17:13:35 
Objet: RE: [pve-devel] internal dhcp server, where to put dhcp configuration ? 

> only routed mode ? I would like also have dhcp on bridged and nat network. 

Understand now (after reading the conversation from may). 

> I agreed to have nic ip configuration in vm, but when you launch dnsmasq, 
> you need to specify the network range for the bridge. 
> (Or we need to compute the ranges from the vms configurations) 

Compute the ranges should not be a problem (looks simple to me). 

> Currently libvirt define the dhcp range on each bridge 
> 
> http://libvirt.org/formatnetwork.html 
> 
> >>Running a full featured dhcp server on a bridge is something different 
> >>for me. Please can you clarify what usage scenario do you think about 
> >>exactly? 
> 
> What I have in mind is at least basic ip auto-configuration of network card in 
> any case (bridge,routed,nat). 
> including gateway,dns-server (option domain-name-servers), domain 
> (option domain-name ). 
> 
> 
> with for bridge+nat, dhcp leases across nodes to keep the ip configuration 
> between live migration 

We already had a solution for cluster wide lease in May? Although, we only 
have static IP assignment (from VM config), so I am not sure if we really need 
that?