Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
In setups where client configured networks are subset of servers networks, e.g. for multi-tenancy, there is problem with client trying to use NIDs on missing networks, getting them from config files or IR. Patch prevents that in two ways:
- LNet skips peer creation from Lustre calls if network is missing
- Lustre doesn't populate internal connection/NIDs structures with NIDs on missing networks
Both means keep only NIDs on configured networks for further use. This implements effectively NID filtering by networks on client side