A small correction to properties section. Property should be a name-value
pair.
{
"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"
},
]
}
Thanks.
On Fri, Mar 6, 2015 at 11:59 PM, Imesh Gunaratne <[email protected]> wrote:
> Great work Raj! Nicely done!
>
> Thanks
>
>
> On Friday, March 6, 2015, Rajkumar Rajaratnam <[email protected]> wrote:
>
>> Hi Devs,
>>
>> I have now changed the application policy schema as below. This is the
>> same schema that Imesh proposed in other thread .
>>
>> {
>> "id": "application-policy-1",
>> "algorithm":"one-after-another",
>> "networkPartitions":[
>> "network-partition-1",
>> "network-partition-2",
>> "network-partition-3",
>> "network-partition-4"
>> ],
>> "properties":[
>> {
>> "key1" : "value1"
>> },
>> {
>> "key2" : "value2"
>> }
>> ]
>> }
>>
>> I have implemented two network partitions algorithms.
>>
>> - one-after-another : Stratos will create 1st application instance in
>> network-partition-1, 2nd instance in network-partition-2 and so on.
>> - all-at-once : Stratos will create application instances per network
>> partitions in parallel
>>
>> Properties can be used to send additional information to algorithms.
>>
>> Thanks.
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
>
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
Mobile : +94777568639
Blog : rajkumarr.com
