ERDA

ERDA is a file system provided by the University of Copenhagen.

It can be accessed through your webbrowser at http://erda.ku.dk/.
It is very easy to create an account using your KU credentials (Swedish number plate).

The full documentation for ERDA is currently located here.

Mount ERDA in Dolphin on the astro cluster

You can mount your ERDA home folder in Dolphin (The default file manager on the cluster).

To add ERDA to Dolphin you should:

Enable the Places panel in Dolphin
To enable the Places panel you either hit F9 or go to the dropdown menu View > Panels and check the Places option.
Add entry
Once the Places panels is enabled right-click anywhere inside the panel and select Add entry
Add entry dialog box
In the dialog box enter the following path into the Location
field: davs://io.erda.dk:443 and optionally enter a name for the entry in the Description field. Click OK
Enter credentials and establish connection
Once you click on your ERDA entry in the Places panel a dialog box will appear.
In the Username field enter your ERDA username (usually the same as your KUnet mail).
In the Password field you must enter your WebDAVS password.
You can choose this password under Settings > WebDAVS on the ERDA website

Import/Export files and folders between astro cluster and ERDA

Import/Export from the astro cluster to ERDA

To setup an import request, log on to http://erda.ku.dk/.

From the Files tab select the Manage data transfer icon in the top right

We recommend setting up a transfer key, but one can also use a password instead.

To set up a transfer key, switch to the Manage transfer keys tab.

First choose a name for the key
Click generate key
Copy the key to the host from which you wish to authorize transfer (could be your workstation or the cluster).
Copy the key to ./ssh/authorized_keys on the desired transfer target host.

Once the key is setup switch to the Manage data transfers tab to setup a transfer.

Select Import or Export.
Choose an optional transfer name.
Choose a transfer protocal. In the following we use SFTP.
Enter the host address. For the cluster this could be astro06.hpc.ku.dk. The port should be 22, which should be default
Choose login with key and select the key created earlier.
Choose the source file or directory. In my experience it only works with the complete path, e.g /lustre/astro/XXXX/XXXX
Enter the destination folder on the ERDA drive.
Optionally enter email for notification of completion.

You can restart/redo a previous transfer request (fx for backup purposes) by clicking on the far-right icon of a previous transfer
request in the list on the Manage data transfer site.

Mount ERDA with SSHFS

NOTE: This option now works on the cluster with the upgrade to CentOS7.

One can use SSHFS to mount ERDA as an local partition
which can be accessed through both terminal and graphical file managers.

To use SSHFS you need to install FUSE.
For Linux you can install fuse and for Mac there is osxfuse

We recommend adding the ERDA host to your ssh config. To do this add the following information to your ssh config file, usually located in ~/.ssh/config:

Host io.erda.dk
Hostname io.erda.dk
User username@nbi.ku.dk
Port 22

Where username is your primary KU mail alias that is associated with your ERDA account.

For authentication two options exist. You can either specify a password or use a SSH key with RSA encryption.
To do this go to the ERDA website and go to Settings > SFTP.
Here you can either add your SSH key to the list of authorized keys or enter the password you wish to use.
To learn how to create an SSH key look in the FAQ section.

Once this is done we can move on.

You need to create an empty folder as mount point on your local laptop/computer, e.g.

mkdir ~/erda

In the following commands we assume that you choose the folder name erda.

Once the empty folder is created you mount with the following command:

sshfs io.erda.dk: erda -o idmap=user -o big_writes -o reconnect

You can unmount the filesystem with

umount ~/erda

On the cluster umount does not work. As a quick and dirty solution, instead kill processes referencing erda in the name to close the mount -- beware that this may have side consequences if you happen to have another process with erda in the name.

pkill erda