From: "Eric Barton" <[EMAIL PROTECTED]>
Date: Wed, 24 Jan 2007 13:49:11 -0000
If a server only has one NID there is no ambiguity.
Ok. So as long as I can arrange for everybody with a presence on the local
lnd to have a different NID than all the external ones, everything should just
work. That should be easy to arrange.
Otherwise, lustre
chooses a NID by asking LNET what the network "distance" to
all the server's NIDs are, and picks the "best" one as follows...
1. Compare hop counts. The NID that is reached by traversing fewer routers
wins.
Presumably that means lnet routers, not IP ones or anything else, correct?
2. Compare rank. Find the local network that you must send on to reach the
given NID and compare the order in which the these
networks appear in the "networks" or "ip2nets" module parameter. The local
network listed first wins.
Ah. I guess I didn't realize that it had that much awareness of topology, but
I suppose it needs to, doesn't it? I guess I should go read up on those
module parms.
At startup time, is it as simple as making sure all the right modules are
loaded, and that the NID name in the mount command gets correctly parsed? So
for instance, if I've got some external hosts accessable over socklnd as
# mount -t lustre my-server:/lustrefs /mnt/external-lustre
and some internal nodes as well, can I just say something like
# mount -t lustre SC!123:/lustrefs /mnt/internal-lustre
as long as my custom lnd will turn "SC!123" into an internal NID?
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
