Comment 27 for bug 1109283

@Nobuto,

Thanks for your input, but as described in the wikipage (which no longer exists) it was *a* way of configuring a DHCP server, not *the* prime way of configuring one. Either way, MAAS itself is *NOT* aware if there's a DHCP server configured or not.

@Scott,

Yes, changes won't be lost, but they would/could still be used.

So, Cobbler-MAAS is *not* aware of it having a DHCP server. Since cobbler "manages" it, MAAS doesn't really know whether the DHCP server has been configured or not. So in reality, this service is external from MAAS. In this case, if we were to upgrade to the SRU package, the DHCP should continue to work and should continue to tell MAAS nodes were they should be booting from because this still remains as a service external to MAAS.

Now, since the SRU version of MAAS can be DNS/DHCP aware, and if the user wants MAAS to manage this, then the user will have to manually migrate from using the "external" dnsmasq to using a MAAS managed DNS/DHCP service, which is what I believe Julian was trying to say.

Hope this helps.