Closed bgruening closed 2 months ago
BTW: I created an issue in the upstream related to the object store https://github.com/galaxyproject/galaxy/issues/18500
We either have to wait a bit or proceed with the rollout without the object stores and deploy object stores later.
Things to set in the galaxy config for the object store:
object_store_cache_path
: We need a Universal path for all user object stores (I guess we need to get a dedicated NFS share or create a dedicated user_object_store_cache
dir in one of the JWDs. I don't know how big this should be and how well this feature is going to be used by our users).object_store_cache_size
: Set this to the max size of the object_store_cache_path
NFS share.BTW: I have added version: 0
to all the templates part of this PR, so the templates in this PR are the same as the ones in my PR here
ping @bgruening.
We can disable this feature for the time being.
A new NFS is ordered and we will use that when we advertise this feature broadly.
So lets disable this feature then.
I have now disabled copying the object store and file source template catalogs.
I think the PR is ready for review. Please check.
Good for me. I'm I allowed to do the update this evening or better tomorrow evening?
So any last comments before I deploy it this evening?
I have added a new commit that:
compare
for these templates.file_source_templates
andobject_store_templates
undergalaxy_mutable_config_dir.
Also, copies the file source and object store templates along with the catalog files to the respective locations on the server.I deployed the same in the ESG instance, and the object store and file source options are now available for the users in the user preferences.