Skip to content

Commit 21ddf68

Browse files
committed
[tutorial] introduce the reader to how files reach the user
1 parent 09a8cc0 commit 21ddf68

File tree

2 files changed

+14
-0
lines changed

2 files changed

+14
-0
lines changed

docs/tutorial/cvmfs/what-is-cvmfs.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,20 @@ triggered when search paths are examined.
4949
In certain cases, the CernVM-FS has also been used to
5050
[distribute large *data* repositories](https://cvmfs.readthedocs.io/en/stable/cpt-large-scale.html).
5151

52+
## How do files become available to the user?
53+
Files in CVMFS are organized in repositories, in the form of content addressable storage.
54+
A [Stratum 0 server](../appendix/terminology.md#stratum0) is the single authoritative source of a repository, responsible for publishing modifications of its contents.
55+
Information on how to create a new repository can be found in the [CVMFS documentation](https://cvmfs.readthedocs.io/en/stable/cpt-repo.html).
56+
57+
Repository administrators should discourage users from accessing Stratum 0 directly, but via a network of public mirror servers.
58+
[Stratum 1](../appendix/terminology.md#stratum1) is a public replica server, containing repositories in their entireties, configured to automatically remain consistent with the stratum 0.
59+
In cases where users do not have access on the public servers, site administrators can [create a private Stratum 1](../access/stratum1.md).
60+
61+
On top of Stratum 1, site administrators are encouraged to [install a reverse proxy](https://cvmfs.readthedocs.io/en/stable/cpt-replica.html#squid-configuration) that works as yet another caching layer.
62+
63+
<div align="center">
64+
<img src="../img/cvmfs_topo.png" alt="CernVM-FS Topology" width="100%"/></br>
65+
</div>
5266

5367
## Features
5468

docs/tutorial/img/cvmfs_topo.png

57.4 KB
Loading

0 commit comments

Comments
 (0)