Skip to content

Commit 4190cfc

Browse files
authored
Update README.md
1 parent 6a0411d commit 4190cfc

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

README.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,17 @@ allow service compute_management to manage compute-management-family in tenancy
77
allow service compute_management to read app-catalog-listing in tenancy
88
allow group user to manage all-resources in compartment compartmentName
99
```
10-
## Policies for autoscaling:
10+
11+
## What is cluster resizing (resize.py) ?
12+
TODO
13+
14+
## What is cluster autoscaling (resize.py) ?
15+
TODO
16+
17+
## How is resizing different from autoscaling ?
18+
TODO
19+
20+
## Policies for autoscaling or resizing:
1121
As described when you specify your variables, if you select instance-principal as way of authenticating your node, make sure your generate a dynamic group and give the following policies to it:
1222
```
1323
Allow dynamic-group instance_principal to read app-catalog-listing in tenancy
@@ -24,6 +34,11 @@ or:
2434

2535
`Allow dynamic-group instance_principal to manage all-resources in compartment compartmentName`
2636

37+
38+
# Resizing (via resize.py or OCI console)
39+
TODO
40+
41+
2742
# Autoscaling
2843

2944
The autoscaling will work in a “cluster per job” approach. This means that for job waiting in the queue, we will launch new cluster specifically for that job. Autoscaling will also take care of spinning down clusters. By default, a cluster is left Idle for 10 minutes before shutting down. Autoscaling is achieved with a cronjob to be able to quickly switch from one scheduler to the next.

0 commit comments

Comments
 (0)