checking CernVM-FS configuration

[boegel]

• option to only check specific things (default: ALL)
• EESSI repository available?
  • If so, via CernVM-FS client, or through some other way? (Can we detect how then?)
  • list of EESSI versions
  • number of modules per EESSI versions?
• CernVM-FS
  • CernVM-FS version check
    • vs Stratum-1 mirrors (doesn't actually matter much)
    • vs latest CernVM-FS release (see GitHub)
  • CernVM-FS commands: run + check output
• CernVM-FS configuration for EESSI repository
  • mirror servers being used (is list complete/up-to-date?)
    • source of truth? GitHub? hidden file in EESSI repo?
    • latency test: download small file directly from mirror server, see how long it takes
      • indicate how decent it is based on fixed thresholds: OK, warning, bad
    • bandwidth test: download a couple large files directly from mirror server (chunks)
      • indicate how decent it is based on fixed thresholds: OK, warning, bad
    • public vs private mirror(s)?
  • proxy servers
    • latency + bandwidth test
    • should be at least two?
  • client cache size
  • autofs vs static mount
  • repository revision
    • gap with what Stratum-1 is version (based on manifest & date)
• global checks (--global option)
  • status of Stratum-1 mirrors (public + private)
    • online?
    • serving latest revision?
• rootless cvmfs_config chksetup (coming soon says @vvolkl)

[vvolkl]

Cross-reference for rootless cvmfs_config chksetup: cvmfs/cvmfs#4077

[boegel]

First steps taken in:

• initial implementation of eessi check #10
  I'll update the list in the description of this issue when the PR is merged...