Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Allow to attach multiple volumes based on backend and region #1949

Closed
Tracked by #1782
peterschmidt85 opened this issue Nov 3, 2024 · 1 comment · Fixed by #1983
Closed
Tracked by #1782

[Feature] Allow to attach multiple volumes based on backend and region #1949

peterschmidt85 opened this issue Nov 3, 2024 · 1 comment · Fixed by #1983
Assignees
Labels

Comments

@peterschmidt85
Copy link
Contributor

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.

volumes:
  - name: [my-aws-eu-west-1-volume, my-aws-us-east-1-volume]
    path: /volume_data
@playerzer0x
Copy link

+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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants