Oracle Cloud Infrastructure
With the new update, it is now possible to run workloads with your Oracle Cloud Infrastructure (OCI) account. The backend is called `oci` and can be configured as follows:
yaml
projects:
- name: main
backends:
- type: oci
creds:
type: default
The supported credential types include `default` and `client`. In case `default` is used, `dstack` automatically picks the default OCI credentials from `~/.oci/config`.
Just like other backends, `oci` supports dev environments, tasks, and services:
<img src="https://github.com/dstackai/static-assets/blob/main/static-assets/images/oci-vllm-task.gif?raw=true" width="750" />
> [!NOTE]
> Support for spot instances, multi-node tasks, and gateways is coming soon.
Find more documentation on using Oracle Cloud Infrastructure on the [reference page](https://dstack.ai/docs/reference/server/config.yml/#oci_1).
Retry policy
We have reworked how to configure the retry policy and how it is applied to runs. Here's an example:
type: task
commands:
- python train.py
retry:
on_events: [no-capacity]
duration: 2h
Now, if you run such a task, `dstack` will keep trying to find capacity within 2 hours. Once capacity is found, `dstack` will run the task.
The `on_events` property also supports `error` (in case the run fails with an error) and `interruption` (if the run is using a spot instance and it was interrupted).
Previously, `dstack` only allowed retries when spot instances were interrupted.
RunPod
Previously, the `runpod` backend only allowed the use of Docker images with `/bin/bash` or `/bin/sh` as the entrypoint. Thanks to the fix on the RunPod's side, `dstack` now allows the use of any Docker images.
Additionally, the `runpod` backend now also supports spot instances.
GCP
The `gcp` backend now also allows configuring VPCs:
yaml
projects:
- name: main
backends:
- type: gcp
project_id: my-awesome-project
creds:
type: default
vpc_name: my-custom-vpc
The VPC should belong to the same project. If you would like to use a shared VPC from another project, you can also specify `vpc_project_id`.
AWS
Last but not least, for the `aws` backend, it is now possible to configure VPCs for selected regions and use the default VPC in other regions:
projects:
- name: main
backends:
- type: aws
creds:
type: default
vpc_ids:
us-east-1: vpc-0a2b3c4d5e6f7g8h
default_vpcs: true
You just need to set `default_vpcs` to `true`.
Other changes
* Fix reverse server-gateway ssh tunnel by r4victor in https://github.com/dstackai/dstack/pull/1303
* Respect run filters for the `ssh` backend by r4victor in https://github.com/dstackai/dstack/pull/1278
* Support resubmitted runs in `dstack run` attached mode by r4victor in https://github.com/dstackai/dstack/pull/1285
* Do not run jobs on `unreachable` instances by r4victor in https://github.com/dstackai/dstack/pull/1286
* Show job termination reason in `dstack ps -v` by r4victor in https://github.com/dstackai/dstack/pull/1301
* Rename `dstack destroy` to `dstack delete` by r4victor in https://github.com/dstackai/dstack/pull/1275
* Prepare OCI backend for release by jvstme in https://github.com/dstackai/dstack/pull/1308
* [Docs] Improve the documentation of the Pydantic models 1293 by peterschmidt85 in https://github.com/dstackai/dstack/pull/1295
* [Docs] Fix Authorization header by jvstme in https://github.com/dstackai/dstack/pull/1305