#73 Job fuse mount

[Anonymous]

Originally created by: martin.r...@gmail.com
Originally owned by: martin.r...@gmail.com

1) Add sshfs keyword to mRSL:

::SSHFSMOUNT::
path_to_mig_home_dir job_mount_path

2) Use sessionid as entry point for sshfs on the MiG server like https file access
2.1) This ensures that the mount point is only valid as long as the job is valid

3) Use the sessionid as login/password to paramiko
3.1) Paramiko checks sessionid dir for 'sessionid' link when a job sshfs connection is requested. If the sessionid dir exists the job sshfs session is established, if not rejected

4) When ::SSHFSMOUNT:: is set in the mRSL job description file, then the job script on the resource mounts the requested directory as a part of the job initialization process and unmounts it as part of the cleanup process

This to consider:
1) Make sure that the MiG paramiko server actually use the sessionid as entry point for the sshfs mount and not the translated home-dir, this is important to prevent access to user MiG homes from resources with zombi MiG jobs

2) Consider a model where storage resources are mounted directly from job resources to ensure scalability

[Anonymous]

Originally posted by: jonas.ba...@gmail.com

Martin implemented the mount mentioned in (1) with the new ::MOUNT:: keyword. It is documented on the wiki:
https://code.google.com/p/migrid/wiki/UsingJobFiles#Mounting_of_MiG_home_during_job_execution

The 'consider' points of the ticket are still open issues.

Status: Started