HPCE/gitea-pages
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Activity

Update

Browse Source
This commit is contained in:
caubet_m
2024-12-18 17:11:12 +01:00
parent f24a644c8e
commit 08c999f97a
4 changed files with 218 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
pages/merlin7/02-How-To-Use-Merlin/transfer-data.md
View File

@ -15,15 +15,16 @@ initiate the transfer from either merlin or the other system, depending on the n
visibility.
- Merlin login nodes are visible from the PSI network, so direct data transfer
(rsync/WinSCP) is generally preferable. This can be initiated from either endpoint.
- Merlin login nodes can access the internet using a limited set of protocols
- SSH-based protocols using port 22 (rsync-over-ssh, sftp, WinSCP, etc)
(rsync/WinSCP/sftp) is generally preferable.
- Protocols from Merlin7 to PSI may require special firewall rules.
- Merlin login nodes can access the internet using a limited set of protocols:
- HTTP-based protocols using ports 80 or 445 (https, WebDav, etc)
- Protocols using other ports require admin configuration and may only work with
specific hosts (ftp, rsync daemons, etc)
specific hosts, and may require new firewall rules (ssh, ftp, rsync daemons, etc).
- Systems on the internet can access the [PSI Data Transfer](https://www.psi.ch/en/photon-science-data-services/data-transfer) service
`datatransfer.psi.ch`, using ssh-based protocols and [Globus](https://www.globus.org/)
SSH-based protocols using port 22 to most PSI servers and (rsync-over-ssh, sftp, WinSCP, etc.), are in general, not permitted
## Direct transfer via Merlin7 login nodes