main.yml

---

### Settings for Ansible role

# Which configuration domain(s) to set up.
# NOTE: Do not use cvmfs-config-computecanada anymore unless you know what you are doing!
cvmfs_configuration:
  - "cvmfs-config-default"  # sets up EGI, OSG, CERN, and Compute Canada repositories

# If cvmfs_gid and cvmfs_uid are both defined, then Ansible will ensure that a 'cvmfs' 
# account with those ids is present before CVMFS is installed. You should make sure to do
# this when deploying CVMFS on a cluster, in case an alien cache might be used.
# cvmfs_gid: "8000131"
# cvmfs_uid: "13000004"

# Whether to set up and use autofs to mount CVMFS repositories (recommended for standard deployment scenarios).
# If false, static mounts will be configured instead (may be necessary for some container engines to use CVMFS).
# Switching a client system from autofs to static mode requires some manual operations and is not supported by this Ansible role.
cvmfs_auto_setup: true
# If static mounts are used, these mount options will be applied in /etc/fstab (see https://github.com/cvmfs/cvmfs/issues/3447).
cvmfs_mount_opts: "defaults,_netdev,x-systemd.mount-timeout=6min"

# Use FUSE3
cvmfs_use_fuse3: true

# Set to true (only as a one-time option with -e) to switch from static mode to autofs. Will unmount all repos!
cvmfs_force_unmount: false

# See `man autofs.conf`
#cvmfs_autofs_timeout: 300

# For production use it is strongly recommended to provide a dedicated filesystem for the CVMFS cache,
# to ensure that the space usage of CVMFS and other applications do not interfere with each other.
# By default, a PV/VG/LV and filesystem will be used for the CVMFS cache,
# based on the following settings further described below:
#  cvmfs_client_pv_name
#  cvmfs_client_vg_name
#  cvmfs_client_lv_name
# For a quick and simple setup this can be set to false, and the CVMFS client will just
# write to the cache directory, whatever storage is backing it.
# WARNING: if false, you should ensure that cvmfs_cache_size quota is appropriate for the storage,
# or else the client may fill up the filesystem (which could cause other applications to fail, and potentially freeze the OS).
cvmfs_client_configure_storage: true

# If this block device name is defined, then a volume group, logical volume, and filesystem will be created on it.
# If it is not defined, then a volume group is assumed to already exist and will be used instead.
# In either case, the name of the volume group is given by cvmfs_client_vg_name.
#cvmfs_client_pv_name: "vdb"

# Name of the volume group for the CVMFS local cache filesystem.
cvmfs_client_vg_name: "cvmfsvg"

# Name of the logical volume for the CVMFS local cache filesystem.
cvmfs_client_lv_name: "cvmfs"

### Settings for CVMFS client
# For further details on CVMFS client configuration settings refer to:
#   https://cvmfs.readthedocs.io/en/stable/apx-parameters.html
#   https://cvmfs.readthedocs.io/en/stable/cpt-configure.html

# Size of the local cache filesystem in megabytes. The cache usage quota (CVMFS_QUOTA_LIMIT) will be automatically
# set to ~ 85% of this amount, to allow for momentary usage beyond the quota while cache clean-up is in progress.
cvmfs_cache_size: "50000"

# The list of repositories that you are interested in, e.g. for monitoring purposes.
# Note that if CVMFS_STRICT_MOUNT is enabled this will be an exclusive list, preventing other repositories from being mounted. 
cvmfs_repositories:
  - "soft.computecanada.ca"

# The list of caching proxy servers to use.
# For more info see
#   https://docs.computecanada.ca/wiki/Accessing_CVMFS
#   https://cvmfs.readthedocs.io/en/stable/cpt-configure.html#proxy-lists
cvmfs_http_proxy: "DIRECT"

# This dict allows arbitrary CVMFS client settings to be applied in /etc/cvmfs/default.local .
# Use this to apply any other settings, aside from those already defined by 
# other variables (CVMFS_REPOSITORIES, CVMFS_QUOTA_LIMIT, CVMFS_HTTP_PROXY).
# For example:
# cvmfs_client_conf:
#   CVMFS_INSTRUMENT_FUSE: "true"
cvmfs_client_conf: {}