One more thing to note is that we will need to add back the dispatch phases into the axis2.xml in order to be able to call this service. Also, we should deploy this service on a separate internal HTTP transport which will be blocked from the firewall for external parties.
On Mon, Aug 6, 2012 at 10:40 AM, Nirmal Fernando <[email protected]> wrote: > > > On Mon, Aug 6, 2012 at 10:25 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> On Mon, Aug 6, 2012 at 10:10 AM, Nirmal Fernando <[email protected]> wrote: >> >>> >>> >>> On Mon, Aug 6, 2012 at 8:56 AM, Sajith Kariyawasam <[email protected]>wrote: >>> >>>> Further we discussed about the situation where LB s are set up as >>>> primary and secondary, and there going to be two endpoints available. >>>> >>>> So in that case, should the service client making a call to both the >>>> endpoints at once, or the second endpoint only if the first endpoint is >>>> detected as not working? >>>> >>> >>> Only to the primary ELB, since ideally secondary ELB becomes primary, >>> when primary is down, using DNS round robin or something similar mechanism. >>> >> >> In that case you need to have state replication between the LBs. You >> need to think of some sort of persistence too, because if the LB crashes & >> is restarted, it should load all the members. >> > > Yes, for a moment, I forgot the context of the question :-) > > >> The other option is for all the member nodes to detect that the LB >> crashed & resend the member information once the LB recovers. >> >> >>> >>>> >>>> On Sat, Aug 4, 2012 at 1:32 PM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Sat, Aug 4, 2012 at 1:28 PM, Nirmal Fernando <[email protected]>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Sat, Aug 4, 2012 at 1:02 PM, Sanjeewa Malalgoda <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> +1 This is a useful feature. >>>>>>> >>>>>>> On Sat, Aug 4, 2012 at 12:01 AM, Afkham Azeez <[email protected]>wrote: >>>>>>> >>>>>>>> In order to allow Cartridges to register themselves with the LB, we >>>>>>>> should write a Web service which will run on the LB. >>>>>>>> >>>>>>>> MemberRegistrationService >>>>>>>> - addMember(MemberInfo memberInfo) >>>>>>>> >>>>>>> >>>>>>>> >>>>>>> >>>>>>>> MemberInfo >>>>>>>> - String host >>>>>>>> - String domain >>>>>>>> - String subDomain, >>>>>>>> - int httpPort >>>>>>>> - int httpsPort >>>>>>>> >>>>>>>> The implementation will add new configuration into the LB. This >>>>>>>> will specifically create a new GroupManagement agent, or get an >>>>>>>> existing GroupManagement agent & add the member to it. >>>>>>>> >>>>>>> >>>>>>> Why do we create new group management agent? >>>>>>> >>>>>> >>>>>> This way we do not need to restart ELB, each time a new Cartridge >>>>>> added, which is belong to a completely new clustering domain - sub domain >>>>>> combination. >>>>>> >>>>>> >>>>>>> If so we have specifically tell what is the associated service name( >>>>>>> appserver.com, dss.com etc.) >>>>>>> >>>>>> >>>>>> This is covered from "String host" variable. >>>>>> >>>>>> and other parameters as like tenant range for cluster domain(for new >>>>>>> group management agent). >>>>>>> >>>>>> >>>>>> Yes, tenant range should also be added for this MemberInfo object. >>>>>> >>>>> >>>>> Yes, I missed that one. I drafted this mail at home while trying to >>>>> recall an image I drew on my whiteboard during a discussion about this >>>>> yesterday with Sajith, and it contained the tenant range. >>>>> >>>>> >>>>>> >>>>>> >>>>>>> I think we need to add members to existing domains. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> For members added through this service, we will need a task that >>>>>>>> will check whether the members are alive by pinging the HTTP/S ports & >>>>>>>> remove inactive nodes. >>>>>>>> >>>>>>>> We can do get to server root or call load balance agent service >>>>>>> for this. >>>>>>> >>>>>>>> We will need this for the Cartridges milestone where any random >>>>>>>> Cartridge can be added to the LB. >>>>>>>> >>>>>>>> -- >>>>>>>> *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* >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Sanjeewa Malalgoda* >>>>>>> USA Mobile : +14084122715 >>>>>>> SL Mobile : +94713068779 >>>>>>> >>>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>>>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Thanks & regards, >>>>>> Nirmal >>>>>> >>>>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>>> Mobile: +94715779733 >>>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *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* >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> * >>>> * >>>> *Sajith Kariyawasam* >>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >>>> >>>> >>> >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> *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* >> >> > > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > -- *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*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
