Customizing memory and cpu specifications for VMs

[Layth17]

• [x] Order matters! bash start.sh $GCS_INSTANCE_NAME --server-account $GCS_SERVICE_ACCOUNT --project $GCS_PROJECT --custom-cpu 10 --custom-memory 64G --boot-disk-size=200GB is ok .... but bash start.sh $GCS_INSTANCE_NAME --server-account $GCS_SERVICE_ACCOUNT --project $GCS_PROJECT --boot-disk-size=200GB --custom-cpu 10 --custom-memory 64G is not

because boot-disk-size is a param taken in through the @ and at that point MEM and CPU weren't specified so MACHINE_TYPE was added by default to the list of params.

In other words, set the flags that start.sh ask for first then add flags accepted by GCP afterwards.

I do not think this is new/unique to this case. This is probably just a new finding for me.

[Layth17]

rework* of parameters

[Layth17]

if MACHINE_TYPE is not specified by user then it is defaulted to e2-standard-2

if either MEM or CPU are empty, then --machine-type=$MACHINE_TYPE is added to the list of params.