Housing authority and courts share InfiniBand switches and need tenant isolation. What should operators apply as the control plane?
Select an answer to reveal the explanation.
Short Explanation
Switches can be shared; trust cannot. Apply InfiniBand PKeys as the multi-tenancy control plane so housing and courts stay isolated.
Full Explanation
When housing authority and courts share InfiniBand switches and need tenant isolation, InfiniBand PKeys are the multi-tenancy control plane for the civic fabric. PKeys decide which endpoints may communicate on which IB partitions; that is how shared IB metal still enforces agency boundaries without giving every HCA free RDMA to every peer. IPoIB network ACLs applied on hosts as the civic fabric control plane fail by concept: host ACLs do not replace IB partition membership, and ACL-only designs often leave a shared communication domain between housing and courts. Configuring BGP-EVPN VRFs on InfiniBand HCAs for the civic fabric fails because EVPN/VRF constructs are Ethernet/IP multi-tenancy tools, not the InfiniBand HCA partition mechanism operators must configure on IB. Advertising Subnet Manager LID assignments as the civic tenant control plane fails because LIDs address endpoints within the subnet; LID assignments do not by themselves create tenant isolation equivalent to PKey partitions. Exam caveat: do not import IPoIB ACL or BGP-EVPN VRF thinking as substitutes for InfiniBand PKeys on shared civic IB switches. Operational check: implement distinct PKeys for housing and courts, leave defaults unused for tenant data paths, verify cross-tenant RDMA fails while intra-tenant RDMA works, and document PKeys as the tenancy control plane in the shared-switch design package.