Sharing information between the Linux VDI and Atos HPC

Just use the shared $HOME or $PERM filesystems. See HPC2020: Filesystems for more information on the filesystem layout of the platform.

Sharing information between the Linux VDI and your end-user-device (eg Windows or Mac laptop)

Native file sharing with Vmware Horizon Client

If you are using the native VMware horizon client installed on your Windows, Mac or Linux Computer, you may make use of its file sharing capabilites. You will be able to see your local directories under ~/tsclient within the VDI Linux and use that to transfer files on both directions. By default, your local HOME on your computer will be shared, but you may set up additional folders if needed. You can configure this going to the VMware client settings, under Drive Sharing.

rsync and other ssh-based tools

From the command line, rsync which will transfer the files over an ssh connection. For that, you will need to have Teleport configured with the apropriate settings in your ssh config file.

Any file transfer tool that supports SSH and the ProxyJump feature should also work, such as the command line tools sftp or scp. You should always initiate the transfer from your computer.

user@yourlaptop:~> rsync -avz mydataset <vdi-host>:/home/user/

Variable host names

 Do keep in mind that, as stated in Missing features and known issues - Linux Virtual Desktop VDI, the host name of your Linux VDI may change after system upgrades, so you may need to edit your $HOME/.ssh/config file to adapt it to host name changes

To copy information from your current Reading-based $HOME and $PERM into the new corresponding filesystems

"Legacy" filesystems will be available for some time, so you should be able to just "cp" those files. See How can I access legacy filesystems - Linux Virtual Desktop VDI FAQ for more details. However, be aware that legacy systems will be switched off at some point during the migration process so please ensure that you copy any required information as soon as possible. 

However, you may still want to use rsync as a convenient way of copying only changed files. Eg

$ rsync -av /originfilesystem /destinationfilesystem

Either the origin or the destination of rsync can be remote, but not both.