[Feature]: Availability zones in configurations

[un-def]

Problem

Currently, it's not possible to create a resource in a specific AZ. Given that some backends require the instances and volumes to belong not only to the same region, but also the same AZ, it can be a problem. For example, with AWS backend I cannot reliably create such a volume that would work with the existing fleet instance.

Solution

• Add availability_zones: array[string] property to the fleet configuration
• Add availability_zone: string property to the volume configuration
• Display AZ in dstack fleet (or dstack fleet -v) output
• Display AZ in dstack volume (or dstack volume -v) output

Workaround

No response

Would you like to help us implement this feature by sending a PR?

No