Hi Sanjiva,
On Fri, Oct 11, 2013 at 11:27 AM, Sanjiva Weerawarana <[email protected]>wrote: > On Fri, Oct 11, 2013 at 10:23 AM, Nirmal Fernando > <[email protected]>wrote: > >> +1 for the new design. >> >> A question: >> >> How can we handle multiple load balancer scenario where one load balancer >> would not interested in all the clusters but a set of selected ones? I >> suggest we go for a hierarchical topic concept, instead of one single >> topology topic. >> > > Are you suggesting some topic hierarchy which recognizes the actual LB > type? I don't like that because that couples the CC to LB types. > I'm sorry, I don't get your point. What I meant was a topic hierarchy like below: Hierarchy is based on the services and service clusters. Topology | |____PHP | |____ php cluster 1 | |____ php cluster 2 | ...... |____MySql | |____ mysql cluster 1 | ...... ..... > My preference is a model where all LBs get all updates and they decide > what they care about and do something about those. > In the topic hierarchy case, LBs will get only the information that each one of them interested in and not other garbage. In someway, LB should know what services or even clusters, it gonna serve and then with a topic hierarchy in hand, LBs get the flexibility of subscribing only to the topics that it's interested in. > >>> - Traffic comes in thru any load balancer (e.g. HAProxy for non-HTTP >>> traffic and our LB for HTTP traffic). LB routes based on its >>> configuration >>> which is periodically updated by the Cloud Controller via topology update >>> messages. >>> >>> IMO we should send topology messages periodically (even there's no >> change), so that LB can get the current status of the system, even after a >> restart. >> > > Yeah to handle fresh LBs we either need to have a periodic update going > out or have a way for the LB to contact the CC and get the latest config. I > prefer the latter because that's a bit like ADC being used to config a > fresh instance. > +1. But I've heard from some other discussion that we are thinking of keeping ADC inside Stratos Manager. :) In fact, going forward we could even auto scale LBs .. but that's a bit far > fetched as it requires possibly doing DNS updates too. But its not that > hard. > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
