Open olivierlambert opened 4 years ago
What's the advantage of doing it in the installer rather than post install?
@Fohdeesha will explain to you why it's a burden to think about the order to do so, I don't remember exactly.
Other distro installer are supporting that, the same way you can install updates during ISO installer too.
More than a few times now either my own remote equipment or customer's equipment is connected to switches configured for LACP - in this case the switch will not unblock the ports unless it sees a valid LACP handshake - this completely blocks networking during the install phase, so the network installer won't work.
And likewise, if you do get it to install with the full installer, you won't be able to access your new xcp-ng install to configure LACP, because the networking gear on the other side still has the ports blocked waiting for a LACP handshake. The "workaround" is to tell the customer to find a network admin to disable LACP, run through the install, configure a LACP bond, then have their network admin re-enable LACP. It's a lot of extra steps/headache stemming from not being able to enable LACP in the installer
This will allow to use all nics on a server in a single bond for load balancing and not have to reserve a single interface for management.
@dkjkj it's not the point: LACP is already working, but not directly from the install.
We need someone to take a look at this.
This support is implemented in the following PR: