Improve 'grep' in 'test_mount.py' about testingframework HOT 3 CLOSED

There are several cases to take into account.
I describe them according to the output of the mount -l command.
fs_spec on fs_mntpoint type fs_type (fs_options) where

• <fs_spec> describes the remote filesystem to be mounted;
• <fs_mntpoint> describes the mountpoint for the filesystem;
• <fs_type> describes the type of the filesystem;
• <fs_options> lists the mount options for the filesystem.

This is what I have found by grepping for 'eos' in different contexts where we will the testing framework. 1-2-3 are production cases, 4-5 are for ScienceBox deployments.

1. eos+<instance-name> on /eos/<instance-name> type fuse
   Example: eosuser on /eos/user type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

• <instance-name> can be whatever. Typically a string of letters+digits

2. home-<letter> on /eos/home-<letter> type fuse:
   Example: home-x on /eos/home-x type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

• <letter> is a letter in [a-z], lowercase

3. project-<letter> on /eos/project-<letter> type fuse:
   Same as above, just with project instead of home.
   Example: project-x on /eos/project-x type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

4. eosdocker on /eos/<whatever> type fuse:
   Example: eosdocker on /eos/up2u type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)

5. eosdocker on /tmp/sciencebox/eos_mount/docker type fuse:
   Example: eosdocker on /tmp/sciencebox/eos_mount/docker type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
   This is currently hard-coded in the setup script of ScienceBox.

from testingframework.

Grepping for 'eos', it might also appear a configuration line for automount // autofs:
/etc/auto.eos on /eos type autofs (rw,relatime,fd=17,pgrp=11698,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=77838)

This should not be taken into account for the sanity of eos mounts.
I would suggest discarding lines with "autofs" in the type field.

from testingframework.

All in all, my suggestion is to issue the mount -l command and then parse the output properly in python.
eos+<instance-name> // home-<letter> // project-<letter> should be relatively easy to spot with regular expressions.
One could also foresee to pass some args to the function to specify <fs_spec> or <fs_mntpoint> if results with regexps are not reliable

from testingframework.