dstack is a lightweight, open-source alternative to Kubernetes & Slurm, simplifying AI container orchestration with multi-cloud & on-prem support. It natively supports NVIDIA, AMD, & TPU.
As SSH fleets/fleet instances may be located in different data centers (that is, in different local networks), it would be useful to distinguish them. The region(s) property, which is already supported for cloud providers, seems as a perfect candidate for this. For example, one NFS volume (that is not yet supported) may be available to some SSH instances, but not to the others, in this case, it would be useful to mark both the fleet and the NFS volume as belonging to the same "region" (e.g., datacenter).
Solution
Add an optional region property to the fleet configuration.
regions and region are mutually exclusive; for on-prem fleets, regions is not allowed, and region is optional, with none as the default value; for cloud fleets, region: foo is an alias for regions: [foo].
Workaround
No response
Would you like to help us implement this feature by sending a PR?
Problem
As SSH fleets/fleet instances may be located in different data centers (that is, in different local networks), it would be useful to distinguish them. The
region(s)
property, which is already supported for cloud providers, seems as a perfect candidate for this. For example, one NFS volume (that is not yet supported) may be available to some SSH instances, but not to the others, in this case, it would be useful to mark both the fleet and the NFS volume as belonging to the same "region" (e.g., datacenter).Solution
region
property to the fleet configuration.regions
andregion
are mutually exclusive; for on-prem fleets,regions
is not allowed, andregion
is optional, withnone
as the default value; for cloud fleets,region: foo
is an alias forregions: [foo]
.Workaround
No response
Would you like to help us implement this feature by sending a PR?
No