IMO it would be better if we can specify membership scheme information as
parameters rather than using XML elements with their names, WDYT?
<Cluster>
...
<MembershipScheme>
<!-- multicast membership scheme related properties -->
<Name>Multicast</Name>
<Parameters>
<Parameter name="Group">228.0.0.4</Parameter>
<Parameter name="Port">45564</Parameter>
<Parameter name="TTL">100</Parameter>
<Parameter name="Timeout">60</Parameter>
</Parameters>
<!-- wka membership scheme related properties -->
<!-- Name>WKA</Name>
<Parameters>
<Parameter name="Members">127.0.0.1:4000,127.0.0.1:4001
</Parameters>
</Parameters -->
<!-- private paas membership scheme related properties -->
<!-- Name>PrivatePaaS</Name>
<Parameters>
<Parameter name="ClusterIds">cluster-1,cluster-2</Parameter>
</Parameters -->
</MembershipScheme>
</Cluster>
On Fri, Aug 21, 2015 at 2:59 PM, Afkham Azeez <[email protected]> wrote:
> I have changed the Generic/MembershipScheme tag to Generic/Name.
>
> On Fri, Aug 21, 2015 at 2:55 PM, Afkham Azeez <[email protected]> wrote:
>
>> In addition to the 3 membership schemes, multicast, WKA & AWS, for
>> Stratos sort of deployments we will need to support other membership
>> management schemes. In order to support this, I am introducing the
>> following configuration into the cluster.xml
>>
>> <Generic>
>> <MembershipScheme>foo</MembershipScheme>
>> <Parameter name="xxx">xxx-val</Parameter>
>> <Parameter name="yyy">yyy-val</Parameter>
>> <Parameter name="zzz">zzz-val</Parameter>
>> </Generic>
>>
>>
>> The implementers will have to
>> implement org.wso2.carbon.clustering.hazelcast.HazelcastMembershipScheme
>> and register it as an OSGi service with the membership.scheme property.
>> This property will correspond to the MembershipScheme defined in the above
>> cluster configuration.
>>
>> Feedback welcome.
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>*
>> *email: **[email protected]* <[email protected]>
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* <http://blog.afkham.org>
>> *twitter: **http://twitter.com/afkham_azeez*
>> <http://twitter.com/afkham_azeez>
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> <http://lk.linkedin.com/in/afkhamazeez>*
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>*
> *email: **[email protected]* <[email protected]>
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* <http://blog.afkham.org>
> *twitter: **http://twitter.com/afkham_azeez*
> <http://twitter.com/afkham_azeez>
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> <http://lk.linkedin.com/in/afkhamazeez>*
>
> *Lean . Enterprise . Middleware*
>
--
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
