Version 9 (modified by jcnelson, 5 years ago) (diff)



  • Client: The Syndicate FUSE module, which downloads metadata from the filesystem's metadata server to generate the hierarchy locally. It periodically validates its locally-kept metadata against the metadata server, refreshing changed portions as necessary. It uploads new metadata for locally-modified files so other clients will see the changes on the next refresh.
  • Content: Data that can be indexed by metadata servers, cached by the CDN, and read and/or hosted by clients.
  • Content server: A server that hosts content. This can be a client, or any host on the Internet with publicly-accessible data.
  • libsyndicate: Common code between all components
  • Master Copy: A directory hierarchy on the metadata server that resembles the directory hierarchy that will be seen on Syndicate clients. Each file in the Master Copy is a stub that contains the metadata (including the URL) for the file it represents.
  • Owner ID: The filesystem-wide numerical ID that identifies which client (if any) owns a file. It occupies the UID field of a file's metadata.
  • Volume ID: The globally-unique numerical ID that identifies which metadata server provided a file's metadata. It occupies the GID field of a file's metadata.
  • Metadata: The mapping from the path of a file within a Syndicate mountpoint to a collection of information about the file's data. This includes the file's URL, permission bits, owner ID, volume ID, size, last-modified time, and (optionally) SHA-1 hash.
  • Metadata server: The server that hosts a filesystem's metadata. One metadata server defines one Syndicate filesystem. Clients upload metadata changes from local applications and users to be committed to the Master Copy.
  • Metadata Service: The web application that manages metadata servers, content servers, and Syndicate users.