MAAS only supports one "managed" (DNS/DHCP) interface per cluster controller.

Bug #1052339 reported by Raphaël Badin
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Jeroen T. Vermeulen

Bug Description

Right now, a cluster controller (i.e. a NodeGroup in db terms) can only have (at most) one "managed" interface. See all the code relying on NodeGroup.get_managed_interface(). This needs to be changed so that the DHCP and the DNS code can deal with many "managed" interfaces per NodeGroup.

Tags: provisioning

Related branches

tags: added: provisioning
Raphaël Badin (rvb)
description: updated
Changed in maas:
milestone: none → 14.04
Revision history for this message
Ante Karamatić (ivoks) wrote :

In a case of bonded interface, current behavior of MAAS is really problematic. Bonded interfaces can change hardware address on reboots and of course when NIC fail.

I came up with a 'concept'/workaround that links a node (and all its NICs) with an IP. So, after commissioning, I run this script, which collects IP addresses and creates a entries for dhcp template. It's not ideal, I know, but it might provide an angle to resolve this problem. If MAAS could inform maas-dhcp about the changes and generate dhcpd.conf on the fly, that would be awesome. 'maas.json' file is output of 'maas-cli maas nodes list'. Ideally, script would pull directly from MAAS, instead of reading the file (I was kind of short on time).

I think this could easily be transformed to a setup where specific NICs would be linked to specific Network or whatever is the idea in the end.

Changed in maas:
assignee: nobody → Jeroen T. Vermeulen (jtv)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.