You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

The Core Filesystem (/asap3/<facility|research group>/gpfs) is accessible via several protocols.
Accessing the Core filesystem is only possible from within the DESY network and always requires a valid DESY account.

As of August 2019, new NFS and SMB servers are available replacing the old servers. The new setup offers an highly available setup.

Access Methods

Native GPFS - via Maxwell

The Core filesystem is mounted on the Maxwell Analysis cluster. This is the fastest available solution for accessing the Core filesystem.
For more information, see Maxwell for Photon Science

SMB - For Windows, macOS and Linux users

For Windows, macOS and Linux users from Office networks, SMB is the recommended way to access the Core filesystem.

Linux desktop users should also access the Core filesystem via SMB, as it does not require any root permissions or configuration on the clients.
This is currently the only way to mount the Core filesystem on a DESY green desktop installation.

Each individual facility or research group has its own share:

FacilityPath on GPFSSMB Share Name

PETRA III

/asap3/petra3/gpfs

\\asap3.desy.de\petra3-core

FLASH

/asap3/flash/gpfs\\asap3.desy.de\flash-core
Special Instruments/asap3/spec.instruments/gpfs\\asap3.desy.de\spec.instruments-core
Research Group
FS-FLASH-O/asap3/fs-flash-o/gpfs\\asap3.desy.de\fs-flash-o-core

See below for a manual on how to access the SMB share by mapping a network drive:

 Windows 10 - Mapping a network drive
  1. Right-click on Computer

  2. Click on Map Network Drive

  3. Select drive U: and enter the SMB share name you want to access
 macOS 10.13 and newer - Mapping a network drive

1. Start Finder and click on Go and select Connect to Server in the menu bar

2. In the next window, specify the SMB share name you want to access. You might need to replace backslashes with a forward slash.

3. Confirm that you want to connect to this SMB server

4. You will be prompted to authenticate, choose Connect As: Registered User and enter your DESY account and password and click connect

5. A new tab will open in the finder and you can now access the data from the Core filesystem. To unmount the filesystem, click on the eject button

 Ubuntu 16.04 and newer - Mapping a network drive
  1. Open the Files or Nautilus application and click on Other Location
  2. Enter the SMB share prefixed with smb://, backslashes have to be converted to forward slashes
  3. Enter your DESY Account name and password
  4. The share has now been mapped and data can be accessed. To unmap the share, click on the eject button
  5. If you need to access the share from the CLI, look into /run/user/<numeric UID>/gvfs/<share name>

NFSv4 - For Linux users

While SMB is still the recommended way to access the Core filesystem, certain use-cases require an NFS mount.

For this purpose, an NFSv4 export with and without Kerberos is available.

FacilityPath on GPFSNFS Export

PETRA III

/asap3/petra3/gpfs

asap3.desy.de:/asap3/petra3/gpfs

FLASH

/asap3/flash/gpfsasap3.desy.de:/asap3/flash/gpfs
Special Instruments/asap3/spec.instruments/gpfsasap3.desy.de:/asap3/spec.instruments/gpfs
Research Group
FS-FLASH-O/asap3/fs-flash-o/gpfsasap3.desy.de:/asap3/fs-flash-o/gpfs

Restricted Mount Access

Access to the NFSv4 exports are either restricted by IP subnet or netgroups from LDAP.

For PETRA III, the following subnets are allowed to mount the Core filesystem with kerberos:

 Click to show subnet list
  • 131.169.38.0/24
  • 131.169.39.0/24
  • 131.169.45.0/24
  • 131.169.66.0/24
  • 131.169.221.0/24
  • 131.169.225.0/24
  • 131.169.232.0/24
  • 131.169.33.0/24
  • 192.168.138.0/24
  • 131.169.65.0/24
  • 192.168.132.0/22
  • 192.168.37.0/24
  • 192.168.56.0/22

For FLASH, hosts in the LDAP netgroup a3-flash-core-krb5-hosts are allowed to mount the core filesystem.
To display the hosts, you can use ldapsearch on pal.desy.de: ldapsearch -x cn=a3-flash-core-krb5-hosts

Mounting via NFSv4 with Kerberos

Mounting the Core filesystem via Kerberos requires root privileges on the client machine.

mount with krb5

mount -o nfsvers=4.0,sec=krb5,hard <NFS Export> <local mountpoint>

Example

mount -o nfsvers=4.0,sec=krb5,hard asap3.desy.de:/asap3/flash/gpfs /asap3/flash/gpfs

Additional configuration and a kerberos keytab is required on the client machine, the setup for this is out of scope for this documentation.

Mounting via NFSv4 without Kerberos

Mounting the Core filesystem without Kerberos requires root privileges. Due to the security implications for this type of mount, this must be explicitly requested, as the host will be included in a whitelist.
Please contact FS-EC (fs-ec@desy.de) in order to be included in the whitelist.

mount without krb5

mount -o nfsvers=4.0,sec=sys,hard <NFS Export> <local mountpoint>

Example

mount -o nfsvers=4.0,sec=sys,hard asap3.desy.de:/asap3/flash/gpfs /asap3/flash/gpfs

Additional configuration is required on the client machine, the setup for this is out of scope for this documentation.

  • No labels