+1 .. looks good!

Sanjiva.

On Thu, Jun 23, 2011 at 3:39 PM, Afkham Azeez <az...@wso2.com> wrote:

> Oops, I have made a mistake; the http protocol should not be part of this
> configuration; modified configuration shown below;
>
> <endpoint>
>                 <serviceAwareDynamicLoadBalanceEndpoint failover="true"
>
> algorithm="org.apache.synapse.endpoints.algorithms.RoundRobin">
>                     <membershipHandler
>
> class="org.apache.synapse.core.axis2.ServiceAwareLoadBalanceMembershipHandler">
>                         <services>
>                             <service>
>                                 <domain>as.cloud.wso2.com</domain>
>                                 <group>wso2as.domain</group>
>                             </service>
>                             <service>
>                                 <domain>esb.cloud.wso2.com</domain>
>                                 <group>wso2esb.domain</group>
>                             </service>
>                             <service>
>                                 <domain>governance.cloud.wso2.com</domain>
>                                 <group>wso2governance.domain</group>
>                             </service>
>                             <service>
>                                 <domain>gs.cloud.wso2.com</domain>
>                                 <group>wso2gs.domain</group>
>                             </service>
>                         </services>
>                     </membershipHandler>
>                 </serviceAwareDynamicLoadBalanceEndpoint>
>             </endpoint>
>
> On Thu, Jun 23, 2011 at 3:36 PM, Afkham Azeez <az...@wso2.com> wrote:
>
>> This is how the endpoint configuration in the synapse.xml will look like;
>>
>> <endpoint>
>>                 <serviceAwareDynamicLoadBalanceEndpoint failover="true"
>>
>> algorithm="org.apache.synapse.endpoints.algorithms.RoundRobin">
>>                     <membershipHandler
>>
>> class="org.apache.synapse.core.axis2.ServiceAwareLoadBalanceMembershipHandler">
>>                         <services>
>>                             <service>
>>                                 <url>http://as.cloud.wso2.com</url>
>>                                 <domain>wso2as.domain</domain>
>>                             </service>
>>                             <service>
>>                                 <url>http://esb.cloud.wso2.com</url>
>>                                 <domain>wso2esb.domain</domain>
>>                             </service>
>>                             <service>
>>                                 <url>http://governance.cloud.wso2.com
>> </url>
>>                                 <domain>wso2governance.domain</domain>
>>                             </service>
>>                             <service>
>>                                 <url>http://gs.cloud.wso2.com</url>
>>                                 <domain>wso2gs.domain</domain>
>>                             </service>
>>                         </services>
>>                     </membershipHandler>
>>                 </serviceAwareDynamicLoadBalanceEndpoint>
>> </endpoint>
>>
>> On Thu, Jun 23, 2011 at 2:20 PM, Afkham Azeez <az...@wso2.com> wrote:
>>
>>> Folks,
>>> I'm thinking of getting $subject implemented since otherwise we will have
>>> to have a large number of LBs for our services. The plan is to write a new
>>> ServiceAwareDynamicLoadBalanceEndpoint, which will do LB based on the
>>> service.
>>>
>>> Axis2 already has support for handling multiple cluster domains, so we
>>> will have to write a new Axis2LoadBalanceMembershipHandler which is service
>>> aware.
>>>
>>> The autoscaling would also need to be modified, but autoscaling is
>>> actually a separate aspect, and we can even run the autoscaler separately if
>>> we are going for the CPU load average based one.
>>>
>>> Thoughts please.
>>>
>>> Thanks
>>> Azeez
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * <http://www.apache.org/>**
>>> email: **az...@wso2.com* <az...@wso2.com>* 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*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **az...@wso2.com* <az...@wso2.com>* 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*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* <az...@wso2.com>* 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*
>
>
> _______________________________________________
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to