0.18.25

Multiple volumes per mount point

It's now possible to specify a list of volumes for a mount point in run configurations:

...
volumes:
  - name: [my-aws-eu-west-1-volume, my-aws-us-east-1-volume]
    path: /volume_data

dstack will choose and mount one volume from the list. This can be used to increase GPU availability by specifying different volumes for different regions, which is desirable for use cases like caching. Previously, it was possible to specify only one volume per mount point, so if there was no compute capacity in the volume's region, provisioning would fail.

DSTACK_NODES_IPS environment variable

A new DSTACK_NODES_IPS environment variable is now available for multi-node tasks. It contains a list of internal IP addresses of all nodes in the cluster, e.g. DSTACK_NODES_IPS="10.128.0.47\n10.128.0.48\n10.128.0.49". This feature enables cluster workloads that require configuring IP addresses of all the nodes.

What's Changed

• Adding an example of NIM by @deep-diver in #1853
• Support specifying multiple volumes per mount point by @r4victor in #1983
• Expose DSTACK_NODES_IPS env var by @r4victor in #1985
• Set minimum paramiko version to 3.2.0 by @un-def in #1984
• Limit azure-mgmt-network>=23.0.0,<28.0.0 by @r4victor in #1988

Full Changelog: 0.18.24...0.18.25