Hi, +1 So AFAIU with this modification, single node have one clustering domain. We have to change only load balancer code to identify nodes as domains or sub domains and we have to start clustering agents for each domain and sub domain when load balancer starts up. And also we have to keep some mapping between domain and sub domain. Also hope we don't have to change in synapse side getNextApplicationMember() method, since it calls per each clustering domain(domain or subdomain). I think i understood this clearly. Correct me if it's wrong.
Thanks. On Mon, Jul 23, 2012 at 9:13 PM, Srinath Perera <[email protected]> wrote: > +1 > > On Mon, Jul 23, 2012 at 5:35 PM, Afkham Azeez <[email protected]> wrote: > >> While working on the management node & worker node separation problem, I >> came up with this concept of partitions within clusters, which I would like >> to call sub-domains. All members of a domain can communicate with each >> other. However, the management nodes & worker nodes clearly have different >> roles, hence belong to different sub-domains. The load balancer should be >> aware of these sub-domains & direct management requests to nodes within the >> management sub-domain according to the specified load balancing algorithm, >> and regular requests to applications & services should be directed to nodes >> within the worker sub-domain. >> >> The members can advertise sub-domains as member properties. The load >> balancer code has to be changed to be sub-domain aware. A sample >> loadbalancer.conf segment is shown below. >> >> appserver-worker { >> # multiple hosts should be separated by a comma. >> hosts appserver.cloud-test.wso2.com, >> as.cloud-test.wso2.com; >> domains { >> *wso2.as.domain* { >> *sub_domain worker;* >> tenant_range *; >> } >> } >> } >> >> appserver-mgt { >> # multiple hosts should be separated by a comma. >> hosts mgt.appserver.cloud-test.wso2.com, >> mgt.as.cloud-test.wso2.com; >> domains { >> >> *wso2.as.domain* { >> *sub_domain mgt;* >> tenant_range *; >> } >> } >> } >> >> Nirmal & I are working on this. Without this change, we will not be able >> to achieve proper management & worker node separation. >> >> Thoughts 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 >> 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* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://www.cs.indiana.edu/~hperera/ > http://srinathsview.blogspot.com/ > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sanjeewa Malalgoda* mobile : +94 713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
