On Sat, Dec 4, 2010 at 10:09 PM, Ruwan Linton <[email protected]> wrote:
> On 12/4/10 8:54 PM, Supun Kamburugamuva wrote: > > > > On Sat, Dec 4, 2010 at 5:45 PM, Sanjiva Weerawarana <[email protected]>wrote: > >> On Sat, Dec 4, 2010 at 2:45 PM, Supun Kamburugamuva <[email protected]>wrote: >> >>> >>>> >>>> The registry based repo, when enabled syncs the >>> axis2 repository periodically. Basically it syncs what ever files that are >>> in the axis2 repository of a cluster of servers that are connected to a >>> single configuration registry. It stores the files in to the registry and >>> then sync the file from there. Now we have moved the synapse configuration >>> to the axis2 repository as well. So when a synapse configuration file is >>> modified the changes will be synched across the cluster. Because we have hot >>> update these changes will immediately taken in to account without requiring >>> a restart of the read-only nodes. >>> >> >> Are we going to allow any node's config to be edited and have that sync >> across all nodes or do we still have a master node concept? >> > > I think we should allow only the master node to be changed. There are > some part of the configuration that doesn't work without this mode. For > example we store things like security policy information about a service in > the registry. So in-order for these things to work user has to always change > the master node. > > Why? > I see Master-node as a concept that we've introduced to overcome some of the limitations we had in the past. If this model works, and if this is expected to scale, we should not have a concept of a master-node in this sense, as Ruwan points out. Somebody, needs to be the source of control, so in that sense we could have a master. Thanks, Senaka. > Any explanation why those changes has to be on the master node, what is > special about the master node apart from the fact that it controls the > configuration? > Ruwan > > > Thanks, > Supun.. > > >> >> I think we have some issues in Stratos because the registry repo is >> synced on a timer. IIRC we discussed changing that to use registry eventing >> to notify the subscribers and they'll pull the changes in. Have we >> implemented that? >> >> We need to avoid getting into a change loop as a result too .. but we've >> dealt with that at a customer setup a while ago. >> >> 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 >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Supun Kamburugamuva > Technical Lead > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > > > _______________________________________________ > Carbon-dev mailing > [email protected]https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > -- > Ruwan Linton > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb > > WSO2 Inc.; http://wso2.com > > > Lean . Enterprise . Middleware > > phone: +1 408 754 7388 ext 51789 > email: [email protected]; cell: +94 77 341 3097 > blog: http://blog.ruwan.org > linkedin: http://www.linkedin.com/in/ruwanlinton > tweet: http://twitter.com/ruwanlinton > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Associate Technical Lead & Product Manager - WSO2 G-Reg; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
