Skip to content

Commit 621668a

Browse files
committed
fixup! [tutorial] introduce the reader to how files reach the user
1 parent 21ddf68 commit 621668a

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

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

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -50,20 +50,23 @@ 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

5252
## 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).
53+
Files in CernVM-FS are organized in repositories, in the form of content addressable storage.
54+
For every repository, there is a dedicated server [( Stratum 0 )](../appendix/terminology.md#stratum0) that is its single authoritative source, responsible for publishing modifications of its contents.
55+
Information on how to create a new repository can be found in the [CernVM-FS documentation](https://cvmfs.readthedocs.io/en/stable/cpt-repo.html).
5656

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).
57+
Repository administrators should discourage users from accessing Stratum 0 directly, but use a network of public mirror servers instead.
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 private Stratum 1 servers](../access/stratum1.md).
6060

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.
61+
On top of Stratum 1, site administrators are encouraged to [install a series of forward proxies](https://cvmfs.readthedocs.io/en/stable/cpt-replica.html#squid-configuration) that works as yet another caching layer.
62+
This will improve the cold cache performance (especially on sites with clusters of nodes) on the client side (see [performance analysis](../performance.md)), but also reduce the load of the Stratum 1 servers.
6263

6364
<div align="center">
6465
<img src="../img/cvmfs_topo.png" alt="CernVM-FS Topology" width="100%"/></br>
6566
</div>
6667

68+
To access a repository, the user (here the CernVM-FS client) specifies the proxy that will forward its requests, and a list of Stratum 1 servers.
69+
Stratum 1 servers will be sorted automatically based on their geographic proximity (see [relevant documentation](https://cvmfs.readthedocs.io/en/stable/cpt-configure.html#sct-geoapi)).
6770
## Features
6871

6972
### On-demand downloading of files and metadata { #features-ondemand }

0 commit comments

Comments
 (0)