Originally created by: jonas.ba...@gmail.com
Originally owned by: jonas.ba...@gmail.com
To whom is this feature relevant?
-users, grid admins, storage owners
Please provide a one line description of the feature:
-External storage available through mounts in VGrid dirs
How would the new feature work (appear in use)?
A resource owner adds a storage unit to her resource. In the storage unit
configuration she provides ssh login details just like for execution units
and specifies a base directory to export with a list of VGrids where it
should be made available. Disk size and quota are optional extra fields to
limit access.
Finally she saves the configuration and uses start and stop buttons to
mount and unmount the storage on the specified locations on the MiG server.
How would the new feature be implemented?
We will add a new resource sub configuration like exe units and these units
are then used for specifying all the details necessary to sshfs (and maybe
curlftpfs) mount a location on the storage unit directly on one or more
locations on the server. Ordinary linking to vgrids will then provide users
with partial or full access to the files depending on their vgrid
membership just like for other vgrid files.
The start and stop buttons on the resource page will have to manage a ssh
tunneled sshfs mount to the storage unit.
Please provide any additional information below.
Fail tolerance may be a bit difficult to handle in a user friendly way, but
perhaps a caching fs on top of the sshfs could provide offline access.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jonas.ba...@gmail.com
Please note that this is a kind of spin off of issue #22
Related
Tickets: #22
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jonas.ba...@gmail.com
first version implemented and in the repository. Only supports basic sshfs mount of
resource units with shared_fs as it basically just mounts directly from the front
end. start_command and stop_command can potentially be used to mount or tunnel to a
remote node, but that is left to the resource owner for now.
Mounted storage dirs are symlinked into the member dirs for each subscribed vgrid
using the unique name of the resource as dir name. This linking does not work for
Generic since it has no such member dir.
The feature is tested to actually work on a dev account, but we still need a user
friendly interface in e.g. resource_editor so that resource owners don't have to
manually manage storage units in their configuration.
Fault tolerance and caching is out of the picture for now.
Status: Started
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jonas.ba...@gmail.com
now with support for jump station resource configurations, too.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: jonas.ba...@gmail.com
integrated
Status: Done