cc_staff
178
edits
No edit summary |
m (reword) |
||
Line 6: | Line 6: | ||
== Introduction == <!--T:2--> | == Introduction == <!--T:2--> | ||
CVMFS is a distributed read-only content distribution system, implemented as a POSIX filesystem in user space (FUSE) using HTTP transport. It was originally developed for the LHC (Large Hadron Collider) experiments at CERN to deliver software to virtual machines and to replace diverse shared software installation areas and package management systems at numerous computing sites. Designed to deliver software in a fast, scalable and reliable fashion, | CVMFS is a distributed read-only content distribution system, implemented as a POSIX filesystem in user space (FUSE) using HTTP transport. It was originally developed for the LHC (Large Hadron Collider) experiments at CERN to deliver software to virtual machines and to replace diverse shared software installation areas and package management systems at numerous computing sites. Designed to deliver software in a fast, scalable and reliable fashion, it is now also used to distribute data, and the scale of usage across dozens of projects involves ~10<sup>10</sup> files and directories, ~10<sup>2</sup> compute sites, and ~10<sup>5</sup> clients around the world. The [http://cernvm-monitor.cern.ch/cvmfs-monitor/ CernVM Monitor] shows many research groups which use CVMFS and the stratum sites which replicate their repositories. | ||
=== Features === <!--T:3--> | === Features === <!--T:3--> | ||
Line 20: | Line 20: | ||
** The stratum 0 holds the master copy of the repository; | ** The stratum 0 holds the master copy of the repository; | ||
** Multiple stratum 1 servers replicate the repository contents from the stratum 0; | ** Multiple stratum 1 servers replicate the repository contents from the stratum 0; | ||
** HTTP proxy servers cache | ** HTTP proxy servers cache requests from clients to stratum 1 servers; | ||
** The CVMFS client downloads files on demand into the local client cache(s). | ** The CVMFS client downloads files on demand into the local client cache(s). | ||
*** Two tiers of local cache can be used, e.g. a fast SSD cache and a large HDD cache. A cluster filesystem can also be used as a shared cache for all nodes in a cluster. | *** Two tiers of local cache can be used, e.g. a fast SSD cache and a large HDD cache. A cluster filesystem can also be used as a shared cache for all nodes in a cluster. |