You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ansible/roles/cvmfs_server/README.md
+15-18Lines changed: 15 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,27 +14,24 @@ This feature is enabled by adding a node to the `cvmfs_server` group. The
14
14
defaults provided are sufficent to implement the above configuration.
15
15
16
16
This role wraps the [EESSI ansible-cvmfs](https://github.com/EESSI/ansible-cvmfs)
17
-
role which provides additional functionality. Because of the intended use of
18
-
this role by default it:
19
-
- Uses https URLs for both dnf repositories and for the EESSI repository replication.
20
-
- Uses the `aws-eu-west-s1-sync` EESSI server (which is the only one providing
17
+
role, which provides additional functionality. The defaults here:
18
+
- Use https URLs for both dnf repositories and for the EESSI repository replication.
19
+
- Use the `aws-eu-west-s1-sync` EESSI server (which is the only one providing
21
20
https replication).
22
-
-Does not configure a squid proxy in front of the Stratum 1 server.
23
-
-Does not configure a firewall (OpenStack security groups are expected to be
21
+
-Do not configure a squid proxy in front of the Stratum 1 server.
22
+
-Do not configure a firewall (OpenStack security groups are expected to be
24
23
sufficent).
25
-
-Does not configure the Geo API service.
24
+
-Do not configure the Geo API service.
26
25
27
26
Guidance on configuring a private Stratum 1 server for EESSI is provided [here](https://www.eessi.io/docs/filesystem_layer/stratum1/#requirements-for-a-stratum-1).
28
27
29
28
**NB**: The initial replication will take a considerable amount of time. If
30
29
this fails due to e.g. a network glitch you can recover it by sshing to the
31
-
server node and running:
30
+
`cvmfs_server` node and running:
32
31
33
32
sudo cvmfs_server snapshot software.eessi.io
34
33
35
-
# Requirements
36
-
37
-
See also the example configuration below.
34
+
## Requirements
38
35
39
36
1. See the [EESSI Stratum 1 requirements](https://www.eessi.io/docs/filesystem_layer/stratum1/#requirements-for-a-stratum-1)
40
37
for the server specification.
@@ -51,14 +48,14 @@ See also the example configuration below.
51
48
Note the former will also require setting `dnf_repos_allow_insecure_creds: true`
52
49
to allow Ark credentials to be templated into repofiles - this also requires 3.
53
50
to avoid exposing these to cluster users.
54
-
51
+
52
+
See also the example configuration below.
53
+
55
54
## Role variables
56
55
57
56
Any variables from the [EESSI ansible-cvmfs role](https://github.com/EESSI/ansible-cvmfs)
58
-
may be used. Due to wrapping that role, this role's defaults are mostly in
59
-
`environments/common/inventory/group_vars/all/cvmfs_server.yml`. The only
60
-
override likely to be be needed is to set `cvmfs_srv_device` if CVMFS data
61
-
should be be stored on a specific block device (e.g. a mounted volume).
57
+
may set. Generally only `cvmfs_srv_device` is likely to be required, if CVMFS
58
+
data should be be stored on a specific block device (e.g. a mounted volume).
62
59
63
60
## Example configuration
64
61
@@ -94,8 +91,8 @@ Configure the role to use the volume for CVMFS data:
94
91
cvmfs_srv_device: /dev/vdb
95
92
```
96
93
97
-
**NB:** Hardcoding the path is only safe if a single volume is attached, else
98
-
the ordering of devices is not guaranteed after reboots etc.
94
+
**NB:** Hardcoding the device path is only safe if a single volume is attached,
95
+
else the ordering of devices is not guaranteed after reboots etc.
99
96
100
97
Note Ark credentials or a local Pulp server must also be configured as referenced
0 commit comments