Updated readme

Author: MarcinZablocki

README.md

@@ -10,7 +10,17 @@ allow service compute_management to manage compute-management-family in tenancy
 allow service compute_management to read app-catalog-listing in tenancy
 allow group user to manage all-resources in compartment compartmentName
 ```
-## Policies for autoscaling:
+
+## What is cluster resizing (resize.py) ?
+TODO
+
+## What is cluster autoscaling ?
+TODO
+
+## How is resizing different from autoscaling ?
+TODO
+
+## Policies for autoscaling or resizing:
 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: 
 ```
 Allow dynamic-group instance_principal to read app-catalog-listing in tenancy
@@ -27,6 +37,11 @@ or:
 
 `Allow dynamic-group instance_principal to manage all-resources in compartment compartmentName`
 
+
+# Resizing (via resize.py or OCI console)
+TODO
+
+
 # Autoscaling
 
 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.