Bugzilla – Bug 7066
Allow VMs to use site DHCP server
Last modified: 2010-07-01 16:29:50
You need to log in before you can comment on or make changes to this bug.
In some installations, it is simpler (and less scary) to use a central DHCP server instead of installing one on each node. This simplifies the install process. This can be achieved by adjusting ebtables rules on the VMM to let DHCP go out to LAN. We must also provide an easy way of letting admin configure the appropriate MAC->IP mappings in their dhcpd.conf.
Fixed in master: http://github.com/nimbusproject/nimbus/compare/785e35ecfe...f0065ba1 and http://github.com/nimbusproject/nimbus/compare/41a3b6a0b7...667ad078 ws-control has a new option "localdhcp" (networks.conf). When false (the default), DHCP traffic will travel out to the default bridge. When true, you must have a local DHCP server on the VMM as before. The nimbus service now writes out several files to $NIMBUS_HOME/services/var/nimbus/. Highlights include: dhcpd.entries - a list of DHCP entries which can be included into your main config. ip_mac.txt - direct IP -> MAC mappings which can be machine parsed and used to generate/update more complicated DHCPD systems (or non-ISC compliant servers).
