File Server Setup Considerations Shared » History » Revision 13
Revision 12 (Anchi Cheng, 09/25/2017 05:28 PM) → Revision 13/14 (Anchi Cheng, 08/15/2018 11:41 AM)
h1. File Server Setup Considerations A specific file tree structure has been assumed in Appion/Leginon. Here is a description of it: h2. Head path Leginon and Appion are saved under the same head directory, and it is assumed to have one. For example */your_file_server_mount_point/whatever* is the head directory. You can have is shorter such as */whatever*, but not just / h2. User not identified in the path # Leginon default image path is defined in [[Configure leginoncfg|leginon.cfg]]. The acceptable form is */your_file_server_mount_point/whatever/leginon*. The images are saved by sessionname under subdirectory of this directory in a form such as */your_file_server_mount_point/whatever/leginon/sessionname/rawdata/*. # Leginon DD movie frames path is defined relative to the Leginon image path once it is set for the session. In the case of the above example, the resulting path is */your_file_server_mount_point/whatever/frames/sessionname/rawdata/*. # Appion processing is default under appion directory parrallel to leginon directory, i.e., /your_file_server_mount_point/whatever/appion. This relationship is hard-coded until v2.2 release. In later releases, the parent directory can be set differently in the webserver myamiweb config.php. The processing are divided by sessionname and then processingtype and then runname of the process. Therefore, your processing results are saved in the following default appion path: */your_file_server_mount_point/whatever/appion/sessionname/processing_type/runname/* h2. User identified in the path in a subdirectory of leginon It is possible to add one more layer below leginon directory to identify users by their username or groupname. In this case; # Leginon default image path can be made to be */your_file_server_mount_point/whatever/leginon/username/sessionname/rawdata*. # frame directory is then */your_file_server_mount_point/whatever/frames/username/sessionname/rawdata*. # In webserver myamiweb/config.php. *APPION_PARENT_ADDITION* should be set to 1. This will preserve username subdivision and give default appion path of */your_file_server_mount_point/whatever/appion/username/sessionname/processing_type/runname/* h2. User identified in the path in a parent directory of leginon It is possible to add one more layer above leginon directory to identify users by their username or groupname. In this case; # Leginon default image path can be made to be */your_file_server_mount_point/whatever/username/leginon/sessionname/rawdata*. # frame directory is then */your_file_server_mount_point/whatever/username/frames/username/sessionname/rawdata*. # In webserver myamiweb/config.php. *APPION_PARENT_REPLACEMENT* should be set to -1. This will preserve username parent division and give default appion path of */your_file_server_mount_point/whatever/username/appion/sessionname/processing_type/runname/* h2. Permission The following permission rule is required for multi-unix-user usage of Leginon/Appion: For Leginon: # The web server redux running apache user need to have read permission to all images in the rawdata directories in order to display them in the viewer. # all users need to have permission to create directory at the level of sessionname. For standard structure, this means */your_file_server_mount_point/whatever/leginon*. in */your_file_server_mount_point/whatever/leginon* # If DD frames are saved and managed by Leginon, the user running the frame rawtransfer.py (typically root) need to have permission to create directory in */your_file_server_mount_point/whatever/frames* # all users need to have read permission in a leginon rawdata directory that contains reference images. You can specify this through leginon.cfg as <pre> [References] path: /common_path/leginon_references </pre> # Users need to have write permission to the session they created, of course. For Appion: # Images uploaded to Appion is considered as a Leginon session. See above for its file tree structure. # The web server apache user need to have read permission to processing directories to display the results. # All users need to have permission to create directory in */your_file_server_mount_point/whatever/appion* # If more than one user will be processing data in the same session, they all need write permission to the session directory */your_file_server_mount_point/whatever/appion/sessionname/*