Feature Request - bonding on MAAS provisioned nodes

Bug #1254755 reported by Eduardo Damato on 2013-11-25
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
MAAS
Wishlist
Unassigned

Bug Description

This is a feature request to request the implementation of provisioning of bonding interfaces on MAAS provisioned systems.

There should be a way of informing MAAS what MAC addresses constitute a bonded interface or what interfaces should be part of a bonded interface, which can (or not) the be same interface used for provisioning the node.

Bonding type should also be available for choice. In the case of LACP bonding for instance the interfaces will not be the same as the provisioning interface since interfaces configured as LACP can not PXE (unless special switch configuration is used for this)

In addition to this the MAC address of the bonded interface will be the MAC of the first interface enslaved into the bond, so it may vary, which would need extra config, or it can be fixed with the hwadddress stanza in /etc/network/interfaces

Julian Edwards (julian-edwards) wrote :

MAAS won't be able to do a lot on its own here but there is a feature coming soon that will enable networking customisations using the Curtin installer. The basic idea is that when a node is started up, the api client will pass through partition info, network info, etc.

I'll add more info here when work starts.

Changed in maas:
status: New → Triaged
importance: Undecided → Wishlist
Changed in maas:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers