Support bond as management interface on firstboot.

[benjamreis]

Hi all!

I'm trying to solve this issue: basically some LACP switch are blocking if LACP is not already configured on the host. So i'd like to support port bonding at install.

I've modified our installer and xapi to support it, but the firstboot fails in read_management_conf when trying to find the mac address associated with bond0 from xapi doc i think i can take the mac address from a member of the bond, is that correct?

Also, read_management_conf returns among other things an interface_config and a bridge_config and i'm not sure how they should be defined in the bonding case. Could you help me? :)

Thanks

[benjamreis]

Also I don't understand why both xcp-neworkd and xen-api read firstboot.d/data/management.conf? Why not read it in xen-api configure stuff via XAPI and then xcp-networkd have XAPI data?

It seems to me xen-api's network-init script can create networks, VLANS, bonds etc and then xcp-networkd can do the network configuration, but I might be wrong.

[benjamreis]

Hi @robhoes did you have time to look into this?

I've tried to figure it out by myself but I'm really lost. I'm not sure there's a lot to do after creating the bonded interface_config and bridge_config since XAPI will create the bonded pifs etc with network-init script after that.

[benjamreis]

I think that with an example of bonded interface_config and bridge_config I could try to replicate it in the first-boot thing but so far i found nothing ressembling that in xcp-networkd sources.

[benjamreis]

Hi, still trying to figure out how to create interface and bridge configs to allow to install an host with a bonded management interface. Any guidance would be appreciated since I'm really stuck on this issue.