[Federated-fs] Conf call 6/5/2008

[Ellard, Daniel]

Did you mean to write "I'm *not* talking about..." instead of "I'm
talking about..."?  If not, then I'm confused about what we talked about
yesterday and I'm not sure what top-of-tree means.
 
Let's work through a concrete example so we can make sure we're using
the same definitions.
 
Imagine that the namespace consists of the following paths and their
prefixes:
 
    /a/B/c/D/e/F/g
    /a/H/i/J/k/L/m
    /a/N/o/P/q
 
Where items whose names are capitalized (B, D, F, H, J, L, N, P) are
junctions, and other items are ordinary directories or files EXCEPT /a/,
which is a special directory that can contain only junctions (or
directories that contain only directories or junctions, recursively...
No ordinary files, links, etc are permitted in the root fileset)
 
So, in my understanding, the top-of-tree junctions are /a/B, /a/H/,
/a/N, and no others.  If I've got this wrong, let's work to normalize
our definitions!
 
-Dan

________________________________

From: LeMahieu, Paul [mailto:LeMahieu_Paul at emc.com] 
Sent: Wednesday, June 11, 2008 1:19 PM
To: Everhart, Craig; Robert Thurlow
Cc: Ellard, Daniel; federated-fs at sdsc.edu
Subject: Re: [Federated-fs] Conf call 6/5/2008


Yes, it's independent of anything with DNS. When I say "top-of-tree",
I'm talking about storing all the configuration of the namespace (tens
of thousands of junction points and their paths in the logical
namespace). For example, if there is /fedfs/home/bob, there is an entry
mapping /fedfs/home/bob to bob's share on some physical file server.
We'd be storing a pseudo file system representing the top-of tree in the
NSDB.

--Paul




	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/federated-fs/attachments/20080611/b146c9e0/attachment.html