The configurations included in the deployment-policy.json
file are as follows:
|
Parameter | Description | Required | Default value | Example value | |
---|---|---|---|---|---|
id | Unique ID of the deployment policy. | Yes | N/A | Dep-policy1 | |
partitionGroup | This defines one or more partitions that are network bound and where communication among the partitions take place very efficiently. For example, in EC2 a partition group can be defined with multiple partitions that belong to the same region.
For more information, see Partition Groups. | Yes | N/A | N/A |
Parameter | Description | Required | Default value | Example value | |
---|---|---|---|---|---|
id | Unique ID of the partition group. | Yes | N/A | EC2-Group1 | |
partitionAlgo | The sequence used to spawn up instances when scaling up. For more information, see Partition Algorithm. | Yes | N/A | round-robin, one-after-another | |
partition | The conditions that will be applied to the partitions that have already been deployed.
For more information, see Partitions. | Yes | N/A | N/A |
Parameter | Description | Required | Default value | Example value |
---|---|---|---|---|
id | The ID of the partition that is already deployed. | Yes | N/A | P1 |
partitionMax | The maximum number of instances that will be maintained for each subscription in this partition when scaling up. | Yes | N/A | 5 |
partitionMin | The minimum number of instances that will be maintained for each subscription in this partition when scaling down. | Yes | N/A | 1 |