diff --git a/docs/assets/images/crusoe-logo.svg b/docs/assets/images/crusoe-logo.svg new file mode 100644 index 0000000000..f973485ed7 --- /dev/null +++ b/docs/assets/images/crusoe-logo.svg @@ -0,0 +1,3 @@ + + + diff --git a/docs/docs/concepts/backends.md b/docs/docs/concepts/backends.md index 5446cef160..bf731823fa 100644 --- a/docs/docs/concepts/backends.md +++ b/docs/docs/concepts/backends.md @@ -745,9 +745,10 @@ projects: Nebius is only supported if `dstack server` is running on Python 3.10 or higher. -### Vultr +### Crusoe -Log into your [Vultr](https://www.vultr.com/) account, click `Account` in the sidebar, select `API`, find the `Personal Access Token` panel and click the `Enable API` button. In the `Access Control` panel, allow API requests from all addresses or from the subnet where your `dstack` server is deployed. +Log into your [Crusoe](https://console.crusoecloud.com/) console and create an API key +under your account settings. Note your project ID from the project settings page. Then, go ahead and configure the backend: @@ -755,89 +756,22 @@ Then, go ahead and configure the backend: ```yaml projects: - - name: main - backends: - - type: vultr - creds: - type: api_key - api_key: B57487240a466624b48de22865589 +- name: main + backends: + - type: crusoe + project_id: your-project-id + creds: + type: access_key + access_key: your-access-key + secret_key: your-secret-key + regions: + - us-east1-a + - us-southcentral1-a ``` -### OCI - -There are two ways to configure OCI: using client credentials or using the default credentials. - -=== "Default credentials" - If you have default credentials set up in `~/.oci/config`, configure the backend like this: - -
- - ```yaml - projects: - - name: main - backends: - - type: oci - creds: - type: default - ``` - -
- -=== "Client credentials" - - Log into the [OCI Console](https://cloud.oracle.com), go to `My profile`, - select `API keys`, and click `Add API key`. - - Once you add a key, you'll see the configuration file. Copy its values to configure the backend as follows: - -
- - ```yaml - projects: - - name: main - backends: - - type: oci - creds: - type: client - user: ocid1.user.oc1..g5vlaeqfu47akmaafq665xsgmyaqjktyfxtacfxc4ftjxuca7aohnd2ev66m - tenancy: ocid1.tenancy.oc1..ajqsftvk4qarcfaak3ha4ycdsaahxmaita5frdwg3tqo2bcokpd3n7oizwai - region: eu-frankfurt-1 - fingerprint: 77:32:77:00:49:7c:cb:56:84:75:8e:77:96:7d:53:17 - key_file: ~/.oci/private_key.pem - ``` - -
- - Make sure to include either the path to your private key via `key_file` or the contents of the key via `key_content`. - -??? info "Required permissions" - - This is an example of a restrictive policy for a group of `dstack` users: - - ``` - Allow group to read compartments in tenancy where target.compartment.name = '' - Allow group to read marketplace-community-listings in compartment - Allow group to manage app-catalog-listing in compartment - Allow group to manage instances in compartment - Allow group to manage compute-capacity-reports in compartment - Allow group to manage volumes in compartment - Allow group to manage volume-attachments in compartment - Allow group to manage virtual-network-family in compartment - ``` - - To use this policy, create a compartment for `dstack` and specify it in `~/.dstack/server/config.yml`. - - ```yaml - projects: - - name: main - backends: - - type: oci - creds: - type: default - compartment_id: ocid1.compartment.oc1..aaaaaaaa - ``` +`regions` is optional. If not specified, all available Crusoe regions are used. @@ -929,34 +863,6 @@ projects: * `sizes` - read * `ssh_key` - create, read, update,delete -### Crusoe Cloud - -Log into your [Crusoe Cloud](https://console.crusoecloud.com/) console and create an API key -under your account settings. Note your project ID from the project settings page. - -Then, go ahead and configure the backend: - -
- -```yaml -projects: -- name: main - backends: - - type: crusoe - project_id: your-project-id - creds: - type: access_key - access_key: your-access-key - secret_key: your-secret-key - regions: - - us-east1-a - - us-southcentral1-a -``` - -
- -`regions` is optional. If not specified, all available Crusoe regions are used. - ### Hot Aisle Log in to the SSH TUI as described in the [Hot Aisle Quick Start](https://hotaisle.xyz/quick-start/). @@ -1008,6 +914,106 @@ projects: +### Vultr + +Log into your [Vultr](https://www.vultr.com/) account, click `Account` in the sidebar, select `API`, find the `Personal Access Token` panel and click the `Enable API` button. In the `Access Control` panel, allow API requests from all addresses or from the subnet where your `dstack` server is deployed. + +Then, go ahead and configure the backend: + +
+ +```yaml +projects: + - name: main + backends: + - type: vultr + creds: + type: api_key + api_key: B57487240a466624b48de22865589 +``` + +
+ +### OCI + +There are two ways to configure OCI: using client credentials or using the default credentials. + +=== "Default credentials" + If you have default credentials set up in `~/.oci/config`, configure the backend like this: + +
+ + ```yaml + projects: + - name: main + backends: + - type: oci + creds: + type: default + ``` + +
+ +=== "Client credentials" + + Log into the [OCI Console](https://cloud.oracle.com), go to `My profile`, + select `API keys`, and click `Add API key`. + + Once you add a key, you'll see the configuration file. Copy its values to configure the backend as follows: + +
+ + ```yaml + projects: + - name: main + backends: + - type: oci + creds: + type: client + user: ocid1.user.oc1..g5vlaeqfu47akmaafq665xsgmyaqjktyfxtacfxc4ftjxuca7aohnd2ev66m + tenancy: ocid1.tenancy.oc1..ajqsftvk4qarcfaak3ha4ycdsaahxmaita5frdwg3tqo2bcokpd3n7oizwai + region: eu-frankfurt-1 + fingerprint: 77:32:77:00:49:7c:cb:56:84:75:8e:77:96:7d:53:17 + key_file: ~/.oci/private_key.pem + ``` + +
+ + Make sure to include either the path to your private key via `key_file` or the contents of the key via `key_content`. + +??? info "Required permissions" + + This is an example of a restrictive policy for a group of `dstack` users: + + ``` + Allow group to read compartments in tenancy where target.compartment.name = '' + Allow group to read marketplace-community-listings in compartment + Allow group to manage app-catalog-listing in compartment + Allow group to manage instances in compartment + Allow group to manage compute-capacity-reports in compartment + Allow group to manage volumes in compartment + Allow group to manage volume-attachments in compartment + Allow group to manage virtual-network-family in compartment + ``` + + To use this policy, create a compartment for `dstack` and specify it in `~/.dstack/server/config.yml`. + + ```yaml + projects: + - name: main + backends: + - type: oci + creds: + type: default + compartment_id: ocid1.compartment.oc1..aaaaaaaa + ``` + +SSH fleets support the same features as [VM-based](#vm-based) backends. + +!!! info "What's next" + 1. See the [`~/.dstack/server/config.yml`](../reference/server/config.yml.md) reference + 2. Check [Projects](../concepts/projects.md) + ## Container-based Container-based backends allow `dstack` to orchestrate container-based runs either directly on cloud providers that support containers or on Kubernetes. @@ -1206,9 +1212,3 @@ projects: Also, the `vastai` backend supports on-demand instances only. Spot instance support coming soon. - -SSH fleets support the same features as [VM-based](#vm-based) backends. - -!!! info "What's next" - 1. See the [`~/.dstack/server/config.yml`](../reference/server/config.yml.md) reference - 2. Check [Projects](../concepts/projects.md) diff --git a/docs/docs/concepts/fleets.md b/docs/docs/concepts/fleets.md index 02308a649a..027ea14ed0 100644 --- a/docs/docs/concepts/fleets.md +++ b/docs/docs/concepts/fleets.md @@ -160,7 +160,7 @@ This property ensures that instances are interconnected. This is required for ru #### Backends - Fast interconnect is supported on the `aws`, `gcp`, `nebius`, `kubernetes`, and `runpod` backends. Some backends may require additional configuration. + Fast interconnect is supported on the `aws`, `gcp`, `nebius`, `crusoe`, and `kubernetes` backends. Some backends may require additional configuration. === "AWS" On AWS, `dstack` requires `public_ips` to be set to `false` in the backend configuration. @@ -173,15 +173,18 @@ This property ensures that instances are interconnected. This is required for ru === "Nebius" On [Nebius](https://docs.nebius.com/compute/clusters/gpu), `dstack` automatically configures InfiniBand networking if it is supported by the selected instance type. + === "Crusoe" + On [Crusoe](https://docs.crusoecloud.com/networking/infiniband/managing-infiniband-networks), `dstack` automatically configures InfiniBand networking if it is supported by the selected instance type. + Refer to the [Crusoe](../../examples/clusters/crusoe/index.md#vms) example for more details. + === "Kubernetes" If the Kubernetes cluster has interconnect configured, `dstack` can use it without additional setup. See the [Lambda](../../examples/clusters/lambda/index.md#kubernetes) or [Crusoe](../../examples/clusters/crusoe/index.md#kubernetes) examples. - === "Runpod" - On [Runpod](https://docs.runpod.io/instant-clusters), `dstack` automatically configures InfiniBand networking if it is supported by the selected instance type. - > See the [Clusters](../../examples.md#clusters) examples. + + === "SSH fleets" If the hosts in the SSH fleet have interconnect configured, you only need to set `placement` to `cluster`. diff --git a/docs/overrides/home.html b/docs/overrides/home.html index 05f5468198..a9aec887ad 100644 --- a/docs/overrides/home.html +++ b/docs/overrides/home.html @@ -135,32 +135,32 @@

A unified control plane for GPU orchestration

- - + + - - + + - - + + - - + + - - + + - - + + diff --git a/docs/partners.md b/docs/partners.md deleted file mode 100644 index 44295691a8..0000000000 --- a/docs/partners.md +++ /dev/null @@ -1,139 +0,0 @@ ---- -#template: backends.html -hide: - - navigation -# - toc - - footer ---- - - - -> Here are the cloud GPU providers that `dstack` integrates with and collaborates with. - -## NVIDIA - -
- - -

- Amazon Web Services -

- - - - -

- Microsoft Azure -

- - - - -

- Google Cloud Platform -

- - - - -

- Lambda -

- - - - -

- Nebius -

- - - - -

- Vultr -

- - - - -

- RunPod -

- - - - -

- Oracle Cloud Infrastructure -

- - - - -

- Vast.ai -

- - - - -

- Verda -

- -
- -## AMD - -
- - -

- Vultr -

- - - - -

- Hot Aisle -

- - - - -

- TensorWave -

- -
- -[//]: # (## Google TPU) - - - -## Join the ecosystem - -Are you interested in integrating and collaborating with us to become part of the ecosystem? - - - Contribute -   - Talk to an expert - diff --git a/examples/clusters/crusoe/README.md b/examples/clusters/crusoe/README.md index 50ec88e461..ed416ae3e7 100644 --- a/examples/clusters/crusoe/README.md +++ b/examples/clusters/crusoe/README.md @@ -1,15 +1,76 @@ --- title: Crusoe -description: Using Crusoe clusters with InfiniBand support via Kubernetes or VMs +description: Using Crusoe clusters with InfiniBand support via VMs or Kubernetes --- # Crusoe `dstack` allows using Crusoe clusters with fast interconnect via two ways: +* [VMs](#vms) – If you configure a `crusoe` backend in `dstack` by providing your Crusoe credentials, `dstack` lets you fully provision and use clusters through `dstack`. * [Kubernetes](#kubernetes) – If you create a Kubernetes cluster on Crusoe and configure a `kubernetes` backend and create a backend fleet in `dstack`, `dstack` lets you fully use this cluster through `dstack`. -* [VMs](#vms) – If you create a VM cluster on Crusoe and create an SSH fleet in `dstack`, `dstack` lets you fully use this cluster through `dstack`. - + +## VMs + +Since `dstack` offers a VM-based backend that natively integrates with Crusoe, you only need to provide your Crusoe credentials to `dstack`, and it will allow you to fully provision and use clusters on Crusoe through `dstack`. + +### Configure a backend + +Log into your [Crusoe](https://console.crusoecloud.com/) console, create an API key under your account settings, and note your project ID. + +
+ +```yaml +projects: +- name: main + backends: + - type: crusoe + project_id: your-project-id + creds: + type: access_key + access_key: your-access-key + secret_key: your-secret-key +``` + +
+ +### Create a fleet + +Once the backend is configured, you can create a fleet: + +
+ +```yaml +type: fleet +name: crusoe-fleet + +nodes: 2 +placement: cluster + +backends: [crusoe] + +resources: + gpu: A100:80GB:8 +``` + +
+ +Pass the fleet configuration to `dstack apply`: + +
+ +```shell +$ dstack apply -f crusoe-fleet.dstack.yml +``` + +
+ +This will automatically create an IB partition and provision instances with InfiniBand networking. + +Once the fleet is created, you can run [dev environments](https://dstack.ai/docs/concepts/dev-environments), [tasks](https://dstack.ai/docs/concepts/tasks), and [services](https://dstack.ai/docs/concepts/services). + +> If you want instances to be provisioned on demand, you can set `nodes` to `0..2`. In this case, `dstack` will create instances only when you run workloads. + ## Kubernetes ### Create a cluster @@ -74,56 +135,68 @@ $ dstack apply -f crusoe-fleet.dstack.yml Once the fleet is created, you can run [dev environments](https://dstack.ai/docs/concepts/dev-environments), [tasks](https://dstack.ai/docs/concepts/tasks), and [services](https://dstack.ai/docs/concepts/services). -## VMs - -Another way to work with Crusoe clusters is through VMs. While `dstack` typically supports VM-based compute providers via [dedicated backends](https://dstack.ai/docs/concepts/backends#vm-based) that automate provisioning, Crusoe does not yet have [such a backend](https://github.com/dstackai/dstack/issues/3378). As a result, to use a VM-based Crusoe cluster with `dstack`, you should use [SSH fleets](https://dstack.ai/docs/concepts/fleets#ssh-fleets). - -### Create instances - -1. Go to `Compute`, then `Instances`, and click `Create Instance`. Make sure to select the right instance type and VM image (that [support interconnect](https://docs.crusoecloud.com/networking/infiniband/managing-infiniband-networks/index.html)). Make sure to create as many instances as needed. +## NCCL tests -### Create a `dstack` fleet +Use a [distributed task](https://dstack.ai/docs/concepts/tasks#distributed-tasks) that runs NCCL tests to validate cluster network bandwidth. -Follow the standard instructions for setting up an [SSH fleet](https://dstack.ai/docs/concepts/fleets/#ssh-fleets): +=== "VMs" -
- -```yaml -type: fleet -name: crusoe-fleet + With the Crusoe backend, HPC-X and NCCL topology files are pre-installed on the host VM image. Mount them into the container via [instance volumes](https://dstack.ai/docs/concepts/volumes#instance-volumes). -placement: cluster +
-# SSH credentials for the on-prem servers -ssh_config: - user: ubuntu - identity_file: ~/.ssh/id_rsa - hosts: - - 3.255.177.51 - - 3.255.177.52 -``` - -
+ ```yaml + type: task + name: nccl-tests -Pass the fleet configuration to `dstack apply`: + nodes: 2 + startup_order: workers-first + stop_criteria: master-done -
+ volumes: + - /opt/hpcx:/opt/hpcx + - /etc/crusoe/nccl_topo:/etc/crusoe/nccl_topo -```shell -$ dstack apply -f crusoe-fleet.dstack.yml -``` + commands: + - . /opt/hpcx/hpcx-init.sh + - hpcx_load + - | + if [ $DSTACK_NODE_RANK -eq 0 ]; then + mpirun \ + --allow-run-as-root \ + --hostfile $DSTACK_MPI_HOSTFILE \ + -n $DSTACK_GPUS_NUM \ + -N $DSTACK_GPUS_PER_NODE \ + --bind-to none \ + -mca btl tcp,self \ + -mca coll_hcoll_enable 0 \ + -x PATH \ + -x LD_LIBRARY_PATH \ + -x CUDA_DEVICE_ORDER=PCI_BUS_ID \ + -x NCCL_SOCKET_NTHREADS=4 \ + -x NCCL_NSOCKS_PERTHREAD=8 \ + -x NCCL_TOPO_FILE=/etc/crusoe/nccl_topo/a100-80gb-sxm-ib-cloud-hypervisor.xml \ + -x NCCL_IB_MERGE_VFS=0 \ + -x NCCL_IB_HCA=^mlx5_0:1 \ + /opt/nccl-tests/build/all_reduce_perf -b 8 -e 2G -f 2 -t 1 -g 1 -c 1 -n 100 + else + sleep infinity + fi -
+ backends: [crusoe] -Once the fleet is created, you can run [dev environments](https://dstack.ai/docs/concepts/dev-environments), [tasks](https://dstack.ai/docs/concepts/tasks), and [services](https://dstack.ai/docs/concepts/services). + resources: + gpu: A100:80GB:8 + shm_size: 16GB + ``` -## NCCL tests +
-Use a [distributed task](https://dstack.ai/docs/concepts/tasks#distributed-tasks) that runs NCCL tests to validate cluster network bandwidth. + > Update `NCCL_TOPO_FILE` to match your instance type. Topology files for all supported types are available at `/etc/crusoe/nccl_topo/` on the host. -=== "Crusoe Managed Kubernetes" +=== "Kubernetes" - If you’re running on Crusoe Managed Kubernetes, make sure to install HPC-X and provide an up-to-date topology file. + If you're running on Crusoe Managed Kubernetes, make sure to install HPC-X and provide an up-to-date topology file.
@@ -190,105 +263,12 @@ Use a [distributed task](https://dstack.ai/docs/concepts/tasks#distributed-tasks ??? info "Privileged" When running on Crusoe Managed Kubernetes, set `privileged` to `true` to ensure access to InfiniBand. -=== "VMs" - -With Crusoe VMs, HPC-X and up-to-date topology files are already available on the hosts. When using SSH fleets, simply mount them via [instance volumes](https://dstack.ai/docs/concepts/volumes#instance-volumes). - -```yaml -type: task -name: nccl-tests - -nodes: 2 -startup_order: workers-first -stop_criteria: master-done - -volumes: - - /opt/hpcx:/opt/hpcx - - /etc/crusoe/nccl_topo:/etc/crusoe/nccl_topo - -commands: - - . /opt/hpcx/hpcx-init.sh - - hpcx_load - # Run NCCL Tests - - | - if [ $DSTACK_NODE_RANK -eq 0 ]; then - mpirun \ - --allow-run-as-root \ - --hostfile $DSTACK_MPI_HOSTFILE \ - -n $DSTACK_GPUS_NUM \ - -N $DSTACK_GPUS_PER_NODE \ - --bind-to none \ - -mca btl tcp,self \ - -mca coll_hcoll_enable 0 \ - -x PATH \ - -x LD_LIBRARY_PATH \ - -x CUDA_DEVICE_ORDER=PCI_BUS_ID \ - -x NCCL_SOCKET_NTHREADS=4 \ - -x NCCL_NSOCKS_PERTHREAD=8 \ - -x NCCL_TOPO_FILE=/etc/crusoe/nccl_topo/a100-80gb-sxm-ib-cloud-hypervisor.xml \ - -x NCCL_IB_MERGE_VFS=0 \ - -x NCCL_IB_AR_THRESHOLD=0 \ - -x NCCL_IB_PCI_RELAXED_ORDERING=1 \ - -x NCCL_IB_SPLIT_DATA_ON_QPS=0 \ - -x NCCL_IB_QPS_PER_CONNECTION=2 \ - -x NCCL_IB_HCA=mlx5_1:1,mlx5_2:1,mlx5_3:1,mlx5_4:1,mlx5_5:1,mlx5_6:1,mlx5_7:1,mlx5_8:1 \ - -x UCX_NET_DEVICES=mlx5_1:1,mlx5_2:1,mlx5_3:1,mlx5_4:1,mlx5_5:1,mlx5_6:1,mlx5_7:1,mlx5_8:1 \ - /opt/nccl-tests/build/all_reduce_perf -b 8 -e 2G -f 2 -t 1 -g 1 -c 1 -n 100 - else - sleep infinity - fi - -resources: - gpu: A100:8 - shm_size: 16GB -``` - Pass the configuration to `dstack apply`:
```shell $ dstack apply -f crusoe-nccl-tests.dstack.yml - -Provisioning... ----> 100% - -nccl-tests provisioning completed (running) - -out-of-place in-place - size count type redop root time algbw busbw #wrong time algbw busbw #wrong - (B) (elements) (us) (GB/s) (GB/s) (us) (GB/s) (GB/s) - 8 2 float sum -1 27.70 0.00 0.00 0 29.82 0.00 0.00 0 - 16 4 float sum -1 28.78 0.00 0.00 0 28.99 0.00 0.00 0 - 32 8 float sum -1 28.49 0.00 0.00 0 28.16 0.00 0.00 0 - 64 16 float sum -1 28.41 0.00 0.00 0 28.69 0.00 0.00 0 - 128 32 float sum -1 28.94 0.00 0.01 0 28.58 0.00 0.01 0 - 256 64 float sum -1 29.46 0.01 0.02 0 29.45 0.01 0.02 0 - 512 128 float sum -1 30.23 0.02 0.03 0 29.85 0.02 0.03 0 - 1024 256 float sum -1 30.79 0.03 0.06 0 34.03 0.03 0.06 0 - 2048 512 float sum -1 37.90 0.05 0.10 0 33.22 0.06 0.12 0 - 4096 1024 float sum -1 35.91 0.11 0.21 0 35.30 0.12 0.22 0 - 8192 2048 float sum -1 36.84 0.22 0.42 0 38.30 0.21 0.40 0 - 16384 4096 float sum -1 47.08 0.35 0.65 0 37.26 0.44 0.82 0 - 32768 8192 float sum -1 45.20 0.72 1.36 0 48.70 0.67 1.26 0 - 65536 16384 float sum -1 49.43 1.33 2.49 0 50.97 1.29 2.41 0 - 131072 32768 float sum -1 51.08 2.57 4.81 0 50.17 2.61 4.90 0 - 262144 65536 float sum -1 192.78 1.36 2.55 0 100.00 2.62 4.92 0 - 524288 131072 float sum -1 68.02 7.71 14.45 0 69.40 7.55 14.16 0 - 1048576 262144 float sum -1 81.71 12.83 24.06 0 88.58 11.84 22.20 0 - 2097152 524288 float sum -1 113.03 18.55 34.79 0 102.21 20.52 38.47 0 - 4194304 1048576 float sum -1 123.50 33.96 63.68 0 131.71 31.84 59.71 0 - 8388608 2097152 float sum -1 189.42 44.29 83.04 0 183.01 45.84 85.95 0 - 16777216 4194304 float sum -1 274.05 61.22 114.79 0 265.91 63.09 118.30 0 - 33554432 8388608 float sum -1 490.77 68.37 128.20 0 490.53 68.40 128.26 0 - 67108864 16777216 float sum -1 854.62 78.52 147.23 0 853.49 78.63 147.43 0 - 134217728 33554432 float sum -1 1483.43 90.48 169.65 0 1479.22 90.74 170.13 0 - 268435456 67108864 float sum -1 2700.36 99.41 186.39 0 2700.49 99.40 186.38 0 - 536870912 134217728 float sum -1 5300.49 101.29 189.91 0 5314.91 101.01 189.40 0 - 1073741824 268435456 float sum -1 10472.2 102.53 192.25 0 10485.6 102.40 192.00 0 - 2147483648 536870912 float sum -1 20749.1 103.50 194.06 0 20745.7 103.51 194.09 0 - Out of bounds values : 0 OK - Avg bus bandwidth : 53.7387 ```
@@ -296,5 +276,5 @@ out-of-place in-place ## What's next 1. Learn about [dev environments](https://dstack.ai/docs/concepts/dev-environments), [tasks](https://dstack.ai/docs/concepts/tasks), [services](https://dstack.ai/docs/concepts/services) -2. Read the [Kuberentes](https://dstack.ai/docs/guides/kubernetes), and [Clusters](https://dstack.ai/docs/guides/clusters) guides +2. Check out [backends](https://dstack.ai/docs/concepts/backends#crusoe-cloud) and [fleets](https://dstack.ai/docs/concepts/fleets#cloud-fleets) 3. Check the docs on [Crusoe's networking](https://docs.crusoecloud.com/networking/infiniband/) and ["Crusoe Managed" Kubernetes](https://docs.crusoecloud.com/orchestration/cmk/index.html) diff --git a/mkdocs.yml b/mkdocs.yml index 58c176f3db..de82cba605 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -106,8 +106,7 @@ plugins: "docs/examples/deployment/nim/index.md": "examples/inference/nim/index.md" "docs/examples/deployment/vllm/index.md": "examples/inference/vllm/index.md" "docs/examples/deployment/tgi/index.md": "examples/inference/tgi/index.md" - "providers.md": "partners.md" - "backends.md": "partners.md" + "backends.md": "docs/concepts/backends.md" "blog/monitoring-gpu-usage.md": "blog/posts/dstack-metrics.md" "blog/inactive-dev-environments-auto-shutdown.md": "blog/posts/inactivity-duration.md" "blog/data-centers-and-private-clouds.md": "blog/posts/gpu-blocks-and-proxy-jump.md" diff --git a/src/dstack/_internal/core/backends/crusoe/models.py b/src/dstack/_internal/core/backends/crusoe/models.py index f405eca1b7..d867301c0d 100644 --- a/src/dstack/_internal/core/backends/crusoe/models.py +++ b/src/dstack/_internal/core/backends/crusoe/models.py @@ -22,7 +22,7 @@ class CrusoeBackendConfig(CoreModel): Literal["crusoe"], Field(description="The type of backend"), ] = "crusoe" - project_id: Annotated[str, Field(description="The Crusoe Cloud project ID")] + project_id: Annotated[str, Field(description="The Crusoe project ID")] regions: Annotated[ Optional[List[str]], Field(description="The list of allowed Crusoe regions. Omit to use all regions"), diff --git a/src/dstack/_internal/core/models/backends/base.py b/src/dstack/_internal/core/models/backends/base.py index 47552010d4..ba382a0b66 100644 --- a/src/dstack/_internal/core/models/backends/base.py +++ b/src/dstack/_internal/core/models/backends/base.py @@ -8,7 +8,7 @@ class BackendType(str, enum.Enum): AWS (BackendType): Amazon Web Services AZURE (BackendType): Microsoft Azure CLOUDRIFT (BackendType): CloudRift - CRUSOE (BackendType): Crusoe Cloud + CRUSOE (BackendType): Crusoe CUDO (BackendType): Cudo DATACRUNCH (BackendType): DataCrunch (for backward compatibility) DIGITALOCEAN (BackendType): DigitalOcean