Hi Amila, No we need both, that is, we need to put the data source in governance registry, and with that, we need to resolve the caching issues, and then, to notify other nodes about the addition/editing of data sources, we need cluster communication between clusters.
Cheers, Anjana. On Fri, Jun 6, 2014 at 2:05 PM, Amila Maha Arachchi <ami...@wso2.com> wrote: > Hi Anjana, > > How does cross cluster communication solves this. Ideally each cluster > should have a separate config registry. So, how a datasource created in one > config registry, appears in another config registry? > > > > > On Fri, Jun 6, 2014 at 1:14 PM, Anjana Fernando <anj...@wso2.com> wrote: > >> Hi Isuru, >> >> As we chatted offline, for this to work, we need the cross cluster >> communication working, and also, we need governance registry caching >> working also, because at the moment, the 15 mins cache validation interval >> is a problem for adding the data sources globally. >> >> Cheers, >> Anjana. >> >> >> On Fri, Jun 6, 2014 at 12:30 PM, Isuru Haththotuwa <isu...@wso2.com> >> wrote: >> >>> Hi, >>> >>> Currently if we create a DataSource from the UI is is persisted in the >>> config space in registry. If we need to $subject, across all clusters, is >>> there a recommended way to do this? >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >> >> >> -- >> *Anjana Fernando* >> Senior Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > -- *Anjana Fernando* Senior Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
