You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, when I use RunPod, I never know in advance if the instance I will use will be available in a particular region of my configured volume.
Thus, if I want to persist data, there is almost no convenient way given the fact that I don't know the region in advance.
Solution:
Allow to create volumes in multiple backends and regions, and allow to specify a list of volumes so dstack can automatically use one of them. This is a game changer feature for use cases when multiple regions (or backends) are going to be used.
+1. Would love to see this feature implemented ASAP. I currently have to cancel and retry different GPU + volume configurations to find one that works.
Problem:
For example, when I use RunPod, I never know in advance if the instance I will use will be available in a particular region of my configured volume.
Thus, if I want to persist data, there is almost no convenient way given the fact that I don't know the region in advance.
Solution:
Allow to create volumes in multiple backends and regions, and allow to specify a list of volumes so dstack can automatically use one of them. This is a game changer feature for use cases when multiple regions (or backends) are going to be used.
The text was updated successfully, but these errors were encountered: