Whamcloud - gitweb
LU-7845 obd: add 'network' client mount option 92/19792/24
authorSebastien Buisson <sbuisson@ddn.com>
Tue, 26 Apr 2016 09:01:00 +0000 (11:01 +0200)
committerOleg Drokin <oleg.drokin@intel.com>
Sat, 17 Dec 2016 05:40:14 +0000 (05:40 +0000)
commit1cf11e1cf9a55fa71c873a5f485be4b63e3a5e39
treed1a2f94a285b0058d08ae24e2367144b9133b74e
parentd70da50ac9401f96a90cf1d7b9ba96bdc77b82f8
LU-7845 obd: add 'network' client mount option

Add a 'network' mount option on client side. All connections made by
the client must be on the LNet network specified in the 'network'
option.

This option can be useful in case of several Lustre client mount
points on the same node, with each mount point using a different
network. It is also interesting when running Lustre clients from
containers, by restricting each container to a specific network.

This new option is added by tampering with two config commands:
- setup: add a fourth parameter, which is the net to restrict
  connections to. This parameter will be passed down to
  ptlrpc_uuid_to_peer() so that client only connects to peers on the
  restricted network.
- add_conn: skip this command if uuid to connect to is not on
  restricted network.

Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: Ica7ab6ebe7c2c9e7b0409b615e90d9271c31e92f
Reviewed-on: https://review.whamcloud.com/19792
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Doug Oucharek <doug.s.oucharek@intel.com>
Reviewed-by: Li Xi <lixi@ddn.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/doc/mount.lustre.8
lustre/include/lustre_disk.h
lustre/include/lustre_net.h
lustre/ldlm/ldlm_lib.c
lustre/obdclass/obd_config.c
lustre/obdclass/obd_mount.c
lustre/ptlrpc/client.c
lustre/ptlrpc/events.c