Interesting app bursting pattern is implemented in one-after-another algorithm

[Rajkumar Rajaratnam]

Hi Devs,

I have extended one-after-another algorithm to support any app bursting
pattern of your choice.

{
    "id": "application-policy-4",
    "algorithm":"one-after-another",
    "networkPartitions":[
        "network-partition-1",
        "network-partition-2",
        "network-partition-3",
        "network-partition-4"
    ],
    "properties":[
        {
            "name": "networkPartitionGroups",
            "value": "network-partition-1|network-partition-2,
network-partition-3, network-partition-4|network-partition-5"
        },
        {
            "name": "key-2",
            "value": "value-2"
        },
    ]
}

The property "networkPartitionGroups" can be used to configure your app
bursting pattern for one-after-another network partition algorithm. You can
group network partitions using a pipe character and you can separate
network partition groups using a comma character. Stratos will create
application instances in network partition groups in each app bursting
iteration.

For example, according to above application policy;

   - Initially stratos will create 2 application instances, each in
   network-partition-1 and network-partition-2
   - In the 1st app bursting iteration, it will create an application
   instance in network-partition-3
   - In the 2nd app bursting iteration, it will create 2 application
   instances, each in network-partition-4 and network-partition-5

So at the end of 2nd app bursting iteration, we will have 5 application
instances running. There is no app bursting after that.
For more information, refer app-bursting-pattern sample application [1]

1.
https://github.com/apache/stratos/tree/master/samples/applications/app-bursting-pattern

Thanks.

-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2

Mobile : +94777568639
Blog : rajkumarr.com