|
In training class, it came up that we have machines with multiple network interfaces (multiple GigE, plus multiple QDR or FDR IB). We would like for Lustre to "not be stupid" about mixing traffic. We would like to be able to prioritize traffic, as well as control how traffic is shaped.
More specifically, Lustre should never take network packets from the microsecond IB system and drop them onto the multiple-millisecond Ethernet system. When possible, it should upgrade Ethernet traffic to IB traffic. Having shaping rules and prioritization rules and some way to describe topology to get priority sorted out would be very useful.
Related is to allow users to choose which network to use for heartbeat/liveness to ensure clients and disks are still operating. Since heartbeat is not interesting, in a multi-network environment, we would like to force heartbeat to always use (for example) Ethernet unless the Ethernet has failed.
In a related concept, "bonding" of interfaces should be specifiable in forms. "Bond for perf/bandwidth interfaces A, B, C into virtual interface V1"; "bond interfaces Q, R into V2"; then "bond for failover V1 then V2".
|