@reinvtv said in NFS nconnect support:

As far as I understand it, this will give us multiple tcp streams over an LACP link, truely aggregating traffic on multiple interfaces. (Until now, you needed to use iSCSI multipathing for this, which isnt able to thin provision.).

You're neigher right nor wrong: LACP is more complex than just bundling NICs and in many cases it will NOT give you any benefit.
Why? Simple: For that you need to have NFS using multiple ports but stay with same MAC and IP, which means that your LACP balancing algo needs to be set (and support) L4.
Many just go L2 or L3 (means they decide on MAC or IP-Address).
As a quick search didn't answer me: If it even doesn't go that 'passive range' multiple port way: In typical environments it won't help you at all with LACP.

One might correct my post.

Also interesting: https://vastdata.com/blog/meet-your-need-for-speed-with-nfs/

@reinvtv @jedimarcus Checking Netbox feature requests right now 🙂 Would this feature still be important to you?

I'm also wondering: at the moment, there's a button in the pool's advanced tab to manually run a synchronization for that pool. But with multiple instances, how would that work? Would it synchronize the pool with all the configured instances? What if you only ever wanted to sync pool A with instance A and pool B with instance B?

@olivierlambert well, yes, there is definitely room for improvement on that part of the gui ;). although I was able to get any other plugin working 😛 no worries though, the quick fix is to remove the (optional) 😉