Galaxy as a very sophisticated support for this called ObjectStore.
Please have a look at the API and the Wiki (the wiki can be improved so
much on this).
I can also send you our configuration using a hierarchical object store.
> Dear all,
> We are in the middle of setting up a local Galaxy instance on CentOS,
> but we have a problem with disk space. In particular, we do not have
> a single large disk partition but, instead, many medium sized ext4
> partitions. Thus, we were wondering if it would be possible for
> Galaxy to use multiple disk partitions instead of a single one for
> data and intermediate files.
> Ideally, it would be great if we could allocate users to various
> groups, which in turn are allocated separate disk partitions.
> Less ideal, but still something we could work with, is to ask users to
> copy/move to/from the other partitions while one remains the "working
> one" for Galaxy.
> Another idea which I think wouldn't work since it would interfere with
> Galaxy is to move files (i.e., via a cron job) to another partition
> when a job is complete and then add a symbolic link to it from the
> "working" partition.
> Are there any suggestions on how I can get around this? Or are we
> stuck with either a single partition or somehow reformatting it and
> merging the partitions (using an xfs file system, etc.)
> Thank you!
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: