© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Mike,
Thanks for following up. The issue with not supporting non-MAAS DHCP services is that it makes it more difficult (although not impossible) to mix MAAS and non-MAAS devices on the same segment, which is probably moderately common for enterprise MANLAN setups. e.g., I have a Ruckus wireless access point (which uses DHCP and needs to PXE boot from its local non-x86 wireless LAN controller) on the same network as my amd64 MAAS client.
From memory, this bug was found in my home test lab, and so is not important from that perspective. I'm happy to leave it as Won't Fix, although it is worth noting that making it more difficult to integrate with legacy networks will limit MAAS' penetration into such environments. It would be great if there was a clearly documented method for installing MAAS into such environments - this may exist, but I couldn't find it at the time of logging this bug.
Regards,
Paul