Hello, I''ve read a chapters about lnet module options, and kerberos-related notes in lustre 1.8 manual. Actually, if I define -- options lnet networks=tcp0 -- instead of -- options lnet networks=tcp0(eth0) -- does it mean any client computer available via tcp0 (any physical interface), will be able to mount lustre filesystem ? Regarding documentation, kerberos support seems to be an experimental feature, with 1.8.1 / 1.8.1.1 ? Regards, DT
On 2009-11-05, at 16:34, Piotr Wadas wrote:> I''ve read a chapters about lnet module options, and kerberos-related > notes in lustre 1.8 manual. > > Actually, if I define > > -- > options lnet networks=tcp0 > -- > > instead of > > -- > options lnet networks=tcp0(eth0) > -- > > does it mean any client computer available via tcp0 (any physical > interface), will be able to mount lustre filesystem ?If the interface isn''t specified it will default to tcp0(eth0).> Regarding documentation, kerberos support seems to be an > experimental feature, > with 1.8.1 / 1.8.1.1 ?This is only an experimental feature in the HEAD code base, not in 1.8. At one time HEAD was going to be released as 1.8, but it is now going to be released as 2.0. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc.
On Fri, Nov 06, 2009 at 12:34:34AM +0100, Piotr Wadas wrote:> ...... > -- > options lnet networks=tcp0 > --When an interface name has been omitted, the lnet would iterate over the list of system IP interfaces (by SIOCGIFCONF) and choose the 1st one whose status is "up" (SIOCGIFFLAGS) and has been configured with a valid IP address (SIOCGIFADDR). If that 1st interface happens to be ''eth0'', then it''s equivalent to explicitly setting interface like:> -- > options lnet networks=tcp0(eth0) > --Apparently, in the 1st configuration, ''eth0'' is not always the interface picked by lnet - ''eth0'' could not have been configured an IP address, and there could be other IP interfaces (e.g. IPoIB) that come ahead of it. Thanks, Isaac