If you are a Ceph developer, you should familiarize yourself with this
core infrastructure service [1]. Included are instructions for
mounting these CephFS file systems on your development machines.
https://wiki.sepia.ceph.com/doku.php?id=services:cephfs
--
Patrick Donnelly, Ph.D.
He / Him / His
Red Hat Partner Engineer
IBM, Inc.
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
The teuthology file system is where results are stored from QA runs.
You don't _have_ to login to the teuthology VM to access these test
artifacts. In fact, you can mount this file system from your laptop
with sepia VPN access or a dev machine (like vossi [1] or senta [2]).
For example:
pdonnell@vossi04 $ grep teuthology < /etc/fstab
172.21.2.201,172.21.2.202,172.21.6.108:/teuthology-archive /teuthology
ceph name=teuthology-ro,secret=<redacted>,mds_namespace=teuthology,_netdev
0 2
This client.teuthology-ro credential can only read the file system. To
get the secret, login to vossi04.front.sepia.ceph.com to read the
unredacted /etc/fstab or email me directly.
You may ask why? Because it's usually much faster to access the file
system on another machine. The teuthology VM is often under heavy load
and memory pressure so the file system cache is cold. Looking at
multi-GB test artifacts also uses up significant memory that's
primarily earmarked for running the teuthology workers.
[1] https://wiki.sepia.ceph.com/doku.php?id=hardware:vossi
[2] https://wiki.sepia.ceph.com/doku.php?id=hardware:senta
--
Patrick Donnelly, Ph.D.
He / Him / His
Red Hat Partner Engineer
IBM, Inc.
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D