Simulated-Cloud Controller Configuration

managed.regionNames={custom-region}
managed.availabilityZoneNames={custom-region-zone}
managed.operationTimeoutMilliseconds=20000
managed.recycleDeadNodes=true

managed.regionNames

This attribute takes a comma separated list of region names. For managed instances we create our own region names which represent where the servers are located. The region name should be in the format similar to us-test1. You do not need to add more than one region.

managed.availabilityZoneNames

This attribute takes a comma separated list of zone names. For managed instances we create our own zone names which represent where the servers are located. The zone names should be in the format simlilar to us-test1-a. You do not need to add more than one zone.

managed.operationTimeoutMilliseconds

This attribute is common to all cloud platform controllers. It controls the max time allowed for a cloud operation. However in the context of SimulatedCloud, this attribute is instead used to set the simulated responseDelay in milliseconds. A responseDelay makes the SimulatedCloud, simulate an operation like a cloud operation.

managed.recycleDeadNodes

This attribute configured how the simulated cloud handles dead nodes. Normally when nodes are scaled down they are recycled automatically (ie: They are soft-reset & put back in availability list for reuse). A node that is being deleted because of failure is generally not a healthy node. Hence it is not a candidate for reuse by default. Setting this attribute to true, directs the controller to force reusability of the node. If the value is set to true, the failed node being deleted will be reused; if set to false then the node will not be reused.