From 97371f1486bda858dcca08cdd2be6178942da903 Mon Sep 17 00:00:00 2001 From: Martin Cech Date: Fri, 19 Apr 2024 12:37:25 -0700 Subject: [PATCH 01/23] add relocation docs to the object store samples --- .../config/sample/object_store_conf.sample.yml | 12 +++++++++--- .../config/sample/object_store_conf.xml.sample | 11 ++++++++--- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/lib/galaxy/config/sample/object_store_conf.sample.yml b/lib/galaxy/config/sample/object_store_conf.sample.yml index 5db8d6ffa08a..b1b2cb34afec 100644 --- a/lib/galaxy/config/sample/object_store_conf.sample.yml +++ b/lib/galaxy/config/sample/object_store_conf.sample.yml @@ -61,7 +61,7 @@ backends: # Sample Distributed Object Store with disk backends configuration # -# In the distributed object store, existing dataests will be located by the `object_store_id` column in the `dataset` +# In the distributed object store, existing datasets will be located by the `object_store_id` column in the `dataset` # table of the Galaxy database, which corresponds to the `id` option on the backend. New datasets are created based on # the `weight` option: a backend with weight "2" has twice the chance of being (randomly) selected for new datasets as a # backend with weight "1". A weight of "0" will still allow datasets in that backend to be read, but no new datasets @@ -299,20 +299,25 @@ extra_dirs: # The admin is responsible for routinely cleaning that storage using Galaxy's admin scripts - this object store # configuration just allows the user selection and communicates expectations to the user. Training related to Galaxy # cleanup scripts can be found in the Galaxy Training Network: -# +# # Slides: https://gxy.io/GTN:S00103 # Tutorial: https://gxy.io/GTN:T00324 # # In this example, the scratch storage is marked as user-private by setting the `private` option to "true" on the -# backend definition. This means it cannot be used in public datasets, shared between users, etc.. This is more example +# backend definition. This means it cannot be used in public datasets, shared between users, etc.. This is for example # purposes - you may very well not want scratch storage to be defined as private as it prevents a lot of regular # functionality and Galaxy handles regularly cleaned datasets fairly gracefully when the appropriate admin scripts are # used. +# +# It is safe to just relabel the object store that a dataset belongs to if the underlying paths mapped to by the object +# stores are the same and the dataset has not been copied. To enable users to relocate datasets this way set the +# backends' `device` property to the same value. type: distributed backends: - id: default type: disk + device: device1 weight: 1 allow_selection: true name: Default Galaxy Storage @@ -329,6 +334,7 @@ backends: found on our [Archive Tier Storage](https://www.msi.umn.edu/content/archive-tier-storage) page. - id: scratch type: disk + device: device2 weight: 0 allow_selection: true private: true diff --git a/lib/galaxy/config/sample/object_store_conf.xml.sample b/lib/galaxy/config/sample/object_store_conf.xml.sample index 2d726077a164..5b81dc3d4cd5 100644 --- a/lib/galaxy/config/sample/object_store_conf.xml.sample +++ b/lib/galaxy/config/sample/object_store_conf.xml.sample @@ -62,7 +62,7 @@