i.e. many object stores such as “files33” and “files30” along with my main (user defined) “backblaze_b2” object storage.
When I try and select a Preferred Galaxy Storage", I only see only 4 storages, which is consistent to what I get back from “/api/object_stores?selectable=true”. I’m not sure how to map what I am seeing on the “Storage overview by location” to the object stores listed in Preferred Galaxy Storage?
(BTW the list of what I have in Preferred Galaxy Storage is, not counting the one hidden item is:
“s3_scratch_netapp01” - “Short term storage for e.g. method development”
“s3_private_netapp01” - “Unshareable storage with additional safeguards”
“user_objects://d887b951-c076-4442-a8ec-b0e3d32447d0” - “backblaze_b2”
“user_objects://4b98815d-b7eb-4de8-903e-be1ff7ce39cb” - “nagalo_b2”
)
I am not sure if this is a bug or simply that I expect something that is not offered as a feature.
I think we will need @davelopez help for this one too. My storage appears to be organized the same way even in a test account with no user defined storage (at EU specifically).
The filesNN: NN.N GB notations appear to be histories sizes to me and the view link goes back into dataset sizes filtered by that grouping (history?). In the context of my test account, that notation would be associated with the sharable storage hosted by the server.
I am guessing that could be true for you as well. If true, then I see three storage areas in your screenshot. Of those, all named filesNN* are in the “Short term storage” group (sharable) and one more “unsharable storage” likely in your list if you scroll (or, it will be if you use it).
Let’s have the EU team confirm this interpretation is correct. Thanks!
This is simply how Galaxy displays the object store configuration file. Galaxy uses the concept of storage locations to store datasets (among other things). If you’d like to learn more about object stores, you can have a look here or at the Galaxy documentation.
What you’re seeing is which disk / mount point / file your data is stored on. As a user, this doesn’t really matter, since Galaxy takes care of locating your files automatically. Over the years, the physical mount points eventually filled up, requiring us to add new ones. All filesXX entries are part of the Long-Term storage, which is not listed through the API endpoint, since it is not a selectable storage location. This is a known Galaxy limitation that our devs are currently working to resolve.
Yes, as Gabriel already mentioned, this is due to how .eu organizes the “Default storage”. It is not a “single selectable storage” but a distributed one. We are working on making this more streamlined now that we have more features to support different ways to organize the storage. But it will take some time.
