An application policy defines the application availability in network partitions. Thereby, it would define whether to start the application in all the network partitions or whether to carryout cloud bursting. A sample application policy definition, together with information on all the properties that can be added in an application policy definition JSON are as follows:
The following are sample configurations that can be used in a JSON to define an application policy:
{ "id": "application-policy-1", "algorithm": "one-after-another", "networkPartitions": [ "network-partition-1" ], "properties": [ { "name": "key-1", "value": "value-1" }, { "name": "key-2", "value": "value-2" } ] }
All the properties that correspond to the application policy resource are explained as follows:
Property | Description | Data Type | Example | ||||||
---|---|---|---|---|---|---|---|---|---|
JSON | UI | ||||||||
| √ | √ | ID of the application policy. | Yes | N/A | String | application-policy-1 | ||
algorithm | √ | √ | Defines the algorithm that needs to be applied between network partitions. The available algorithms are as follows:
| Yes | N/A | String | one-after-another | ||
networkPartitions | √ | √ | This defines one or more partitions that are network bound and where communication among the partitions take place very efficiently. For more information, see Partition Groups. | Yes | N/A | String | network-partition-1 | ||
properties | √ | √ | This defines any properties that need to be passed in the application policy JSON. The properties will be listed as name value pairs. For more information on the sub-properties, see properties. | No | N/A | properties array | N/A |
Property | Description | Data Type | Example | ||||||
---|---|---|---|---|---|---|---|---|---|
JSON | UI | ||||||||
name | √ | √ | Name of the property being passed as a name value pair. | No | N/A | String | key-1 | ||
value | √ | √ | Value that corresponds to the name value pair. | No | N/A | String | value-2 |