Hi, Thanks for the comments. Yes the data is runtime and better to store in the DB. And the data is actually, mapping of "clusterId", and endpoint public IP (cartridge IP or LB IP). In this point, no knowledge of which clusterId maps to which tenant. Hence, this is a tenant unaware data set. But, final url is tenant aware and that is generated on the fly.
Thanks, Roshan Deniyage Associate Technical Lead WSO2, Inc: http://wso2.com Mobile : +94 777636406 Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>* LinkedIn : https://www.linkedin.com/in/roshandeniyage On Wed, Oct 15, 2014 at 3:41 PM, Gayan Dhanushka <[email protected]> wrote: > Hi Roshan, > > Since this is not metadata IMO it is better to use the runtime data DB > that we already have. It is not good to store constantly changing dynamic > data into the registry. > > Thanks > GayanD > > On Wed, Oct 15, 2014 at 3:39 PM, Danushka Fernando <[email protected]> > wrote: > >> 1. If these are runtime data don't store in registry. Registry is only >> for metadata not runtime data. >> 2. AFAIU this urls are strickly mapped to the application which is inside >> a tenant. So data are tenant related. Correct me if I am wrong. >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> On Wed, Oct 15, 2014 at 3:36 PM, Roshan Deniyage <[email protected]> >> wrote: >> >>> Hi Danushka, >>> The use case is that, we use a event listener to get newly spawned >>> catridges's information (public IP, dns etc) and keep the data inside the >>> app-factory side. These are runtime data and time to time get updated. >>> There is no tenant related info in these data. >>> When user, request for the url of his application, that is generated >>> using those above data and his other meta data. Presently, I keep the >>> cartridge information in memory which is not reliable, So, we need to >>> persist these data in carbon registry or in app-factory DB. >>> If carbon registry have no sharing mechanism, we have to use the db I >>> guess. >>> >>> >>> Thanks, >>> Roshan Deniyage >>> Associate Technical Lead >>> WSO2, Inc: http://wso2.com >>> >>> Mobile : +94 777636406 >>> Twitter : *https://twitter.com/roshku <https://twitter.com/roshku>* >>> LinkedIn : https://www.linkedin.com/in/roshandeniyage >>> >>> >>> On Wed, Oct 15, 2014 at 3:24 PM, Danushka Fernando <[email protected]> >>> wrote: >>> >>>> Hi Roshan >>>> Can you explain your use case. AFAIK this is not facilitated in carbon. >>>> Tenants are totally isolated and they cannot access each other's tenant. By >>>> going through the problem you are trying to solve we may be able to find a >>>> solution. >>>> >>>> Thanks & Regards >>>> Danushka Fernando >>>> Software Engineer >>>> WSO2 inc. http://wso2.com/ >>>> Mobile : +94716332729 >>>> >>>> On Wed, Oct 15, 2014 at 2:25 PM, Roshan Deniyage <[email protected]> >>>> wrote: >>>> >>>>> Hi Devs, >>>>> Can anyone provide me a sample code to write to carbon registry >>>>> component which can be shared by all tenants. (may be super tenant's user >>>>> registry). >>>>> I need to write data to shared location which can be read by all the >>>>> tenants. >>>>> >>>>> >>>>> Thanks, >>>>> Roshan >>>>> >>>>> Deniyage >>>>> >>>>> WSO2, Inc: http://wso2.com >>>>> >>>>> Mobile : +94 777636406 >>>>> Twitter : *https://twitter.com/roshku >>>>> <https://twitter.com/roshku>* >>>>> LinkedIn : https://www.linkedin.com/in/roshandeniyage >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
