You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/resources/cluster.md
-30
Original file line number
Diff line number
Diff line change
@@ -294,10 +294,6 @@ Required:
294
294
295
295
-`non_gpu_workers` (Block List, Min: 1, Max: 1) Setup auto scaling for non gpu nodes. (see [below for nested schema](#nestedblock--autoscale--non_gpu_workers))
296
296
297
-
Optional:
298
-
299
-
-`gpu_workers` (Block List, Max: 1) Setup auto scaling for gpu nodes. (see [below for nested schema](#nestedblock--autoscale--gpu_workers))
-`instance_type` (String) The instance type to use while auto scaling.
333
-
334
-
Optional:
335
-
336
-
-`disk_size` (Number) The disk size to use while auto scaling Defaults to `512`.
337
-
-`downscale_wait_time` (Number) The time to wait before removing unused resources. Defaults to `300`.
338
-
-`max_workers` (Number) The maximum number of workers created by auto scaling. Defaults to `10`.
339
-
-`min_workers` (Number) The minimum number of workers created by auto scaling. Defaults to `0`.
340
-
-`spot_config` (Block List, Max: 1) The configuration to use spot instances (see [below for nested schema](#nestedblock--autoscale--gpu_workers--spot_config))
341
-
-`standby_workers` (Number) The percentage of workers to be always available during auto scaling. If you set this value to 0 new workers will only be added when a job or a notebook requests the resources. This attribute will not be taken into account if you set the minimum number of workers to 0 and no resources are used in the cluster, instead, it will start to take effect as soon as you start using resources. Defaults to `0.5`.
Copy file name to clipboardexpand all lines: docs/resources/cluster_from_backup.md
-30
Original file line number
Diff line number
Diff line change
@@ -70,10 +70,6 @@ Required:
70
70
71
71
-`non_gpu_workers` (Block List, Min: 1, Max: 1) Setup auto scaling for non gpu nodes. (see [below for nested schema](#nestedblock--autoscale--non_gpu_workers))
72
72
73
-
Optional:
74
-
75
-
-`gpu_workers` (Block List, Max: 1) Setup auto scaling for gpu nodes. (see [below for nested schema](#nestedblock--autoscale--gpu_workers))
-`instance_type` (String) The instance type to use while auto scaling.
109
-
110
-
Optional:
111
-
112
-
-`disk_size` (Number) The disk size to use while auto scaling Defaults to `512`.
113
-
-`downscale_wait_time` (Number) The time to wait before removing unused resources. Defaults to `300`.
114
-
-`max_workers` (Number) The maximum number of workers created by auto scaling. Defaults to `10`.
115
-
-`min_workers` (Number) The minimum number of workers created by auto scaling. Defaults to `0`.
116
-
-`spot_config` (Block List, Max: 1) The configuration to use spot instances (see [below for nested schema](#nestedblock--autoscale--gpu_workers--spot_config))
117
-
-`standby_workers` (Number) The percentage of workers to be always available during auto scaling. If you set this value to 0 new workers will only be added when a job or a notebook requests the resources. This attribute will not be taken into account if you set the minimum number of workers to 0 and no resources are used in the cluster, instead, it will start to take effect as soon as you start using resources. Defaults to `0.5`.
Copy file name to clipboardexpand all lines: examples/complete/aws/autoscale/README.md
+3-12
Original file line number
Diff line number
Diff line change
@@ -44,15 +44,15 @@ terraform apply
44
44
45
45
## Update Autoscale
46
46
47
-
You can update the autoscale configuration after creations, by changing the `autoscale` configuration block. For example, you can configure autoscale for GPU workers as follows:
47
+
You can update the autoscale configuration after creations, by changing the `autoscale` configuration block. For example, you can configure autoscale as follows:
48
48
49
49
> **Notice** that you need to run `terraform apply` after updating your configuration for your changes to take place.
You can update the autoscale configuration after creations, by changing the `autoscale` configuration block. For example, you can configure autoscale for GPU workers as follows:
47
+
You can update the autoscale configuration after creations, by changing the `autoscale` configuration block. For example, you can configure your own worker as follows:
48
48
49
49
> **Notice** that you need to run `terraform apply` after updating your configuration for your changes to take place.
50
50
51
51
```hcl
52
-
data "hopsworksai_instance_type" "gpu_worker" {
52
+
data "hopsworksai_instance_type" "my_worker" {
53
53
cloud_provider = "AZURE"
54
54
node_type = "worker"
55
-
min_gpus = 1
55
+
min_cpus = 16
56
56
}
57
57
58
58
resource "hopsworksai_cluster" "cluster" {
59
59
# all the other configurations are omitted for clarity
0 commit comments