Re: [Carbon-dev] Event Multi tenant support
On Mon, Feb 28, 2011 at 12:43 PM, Danushka Menikkumbura wrote: > That was not for topics but for queues. > > >> What is the approach for queues? >> > > Prefixing with domain name > This it self won't make Qpid component Multi tenant. you need to do following as well. 1. Authenticate the users with the tenant domain. Current implementation only check the user name and pass word. And also now you can get the user realm from the user realm service directly. 2. Get the tenant aware registry using tenant Id for authorization. thanks, Amila. > > Danushka > > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
On Mon, Feb 28, 2011 at 11:53 AM, Danushka Menikkumbura wrote: > Srinath, > > That was not for topics but for queues. What is the approach for queues? > I need to check on that. Anyway as I see what Amila has suggested is the > proper approach. Also (something that just popped into my mind) Qpid has > client id as part of its connection url which has no apparent use. I need to > check if we can use that as our tenant id so that we can use queue/topic > names as it is. > The normal convention for multitenacy is that users use the user name as userName@tenatdomain when the want to access the system as a tenant. Other are same. so in Qpid case if a user wants to access a queue or topic he sends his queue or topic name with the tenant specific name i.e us...@wso2.com Qpid should internally handle the proper queue/topic map. thanks, Amila. > > Thanks, > Danushka > > On Mon, Feb 28, 2011 at 7:11 AM, Srinath Perera wrote: > >> As I recall, we were discussing about Qpid MT with design meetings. >> Danushaka, what was the conclusion of those discussions? did we >> implement it? >> --Srinath >> >> On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi >> wrote: >> > hi, >> > >> > Shammi has started the $subject since registry required the multi >> tenancy >> > support and there is time >> > to finish this before end of march. >> > >> > Event Multi tenant has two parts >> > >> > 1. multi tenating topics and subscriptions stored in registry. >> > This can be done by using the tenant specific registry to store and >> retrieve >> > topics/subscriptions. >> > >> > 2. Qpid multi tenancy >> > I think Qpid does not support multi tenancy. so the possible way of >> > achieving multi tenancy is to append the domain name to >> > topic name then actual topics names would appear as follows. >> > >> > wso2.com/myTopic >> > ibm.com/myTopic >> > >> > But this gives a problem for the users who directly going to connect to >> Qpid >> > server. >> > now users need to given the topic name with the domain name. >> > >> > But a better solution would be to give the tenant domain with the user >> name >> > and internally qpid authenticate the user and >> > create the actually queue name. >> > >> > i.e a user will subscribe as >> > >> > us...@wso2.com to myTopic >> > internally qpid process the user name and actually subscribes to >> > wso2.com/myTopic. >> > >> > Danushka, is it possible to do this? If so I think even the carbonEvent >> > compoent can use this convention which I belive is the best way. >> > >> > thanks, >> > Amila. >> > >> > >> > >> > >> > >> > ___ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org >> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> >> >> >> -- >> >> Srinath Perera, Ph.D. >> Senior Software Architect, WSO2 Inc. >> Visiting Lecturer, University of Moratuwa >> Member, Apache Software Foundation >> Research Scientist, Lanka Software Foundation >> Blog: http://srinathsview.blogspot.com/ >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
> > That was not for topics but for queues. > What is the approach for queues? > Prefixing with domain name Danushka ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
Srinath, That was not for topics but for queues. I need to check on that. Anyway as I see what Amila has suggested is the proper approach. Also (something that just popped into my mind) Qpid has client id as part of its connection url which has no apparent use. I need to check if we can use that as our tenant id so that we can use queue/topic names as it is. Thanks, Danushka On Mon, Feb 28, 2011 at 7:11 AM, Srinath Perera wrote: > As I recall, we were discussing about Qpid MT with design meetings. > Danushaka, what was the conclusion of those discussions? did we > implement it? > --Srinath > > On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi > wrote: > > hi, > > > > Shammi has started the $subject since registry required the multi tenancy > > support and there is time > > to finish this before end of march. > > > > Event Multi tenant has two parts > > > > 1. multi tenating topics and subscriptions stored in registry. > > This can be done by using the tenant specific registry to store and > retrieve > > topics/subscriptions. > > > > 2. Qpid multi tenancy > > I think Qpid does not support multi tenancy. so the possible way of > > achieving multi tenancy is to append the domain name to > > topic name then actual topics names would appear as follows. > > > > wso2.com/myTopic > > ibm.com/myTopic > > > > But this gives a problem for the users who directly going to connect to > Qpid > > server. > > now users need to given the topic name with the domain name. > > > > But a better solution would be to give the tenant domain with the user > name > > and internally qpid authenticate the user and > > create the actually queue name. > > > > i.e a user will subscribe as > > > > us...@wso2.com to myTopic > > internally qpid process the user name and actually subscribes to > > wso2.com/myTopic. > > > > Danushka, is it possible to do this? If so I think even the carbonEvent > > compoent can use this convention which I belive is the best way. > > > > thanks, > > Amila. > > > > > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > > Srinath Perera, Ph.D. > Senior Software Architect, WSO2 Inc. > Visiting Lecturer, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
On Mon, Feb 28, 2011 at 7:11 AM, Srinath Perera wrote: > As I recall, we were discussing about Qpid MT with design meetings. > Danushaka, what was the conclusion of those discussions? did we > implement it? > Well I was not aware of that. If there is already support we should use it. thanks, Amila. > --Srinath > > On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi > wrote: > > hi, > > > > Shammi has started the $subject since registry required the multi tenancy > > support and there is time > > to finish this before end of march. > > > > Event Multi tenant has two parts > > > > 1. multi tenating topics and subscriptions stored in registry. > > This can be done by using the tenant specific registry to store and > retrieve > > topics/subscriptions. > > > > 2. Qpid multi tenancy > > I think Qpid does not support multi tenancy. so the possible way of > > achieving multi tenancy is to append the domain name to > > topic name then actual topics names would appear as follows. > > > > wso2.com/myTopic > > ibm.com/myTopic > > > > But this gives a problem for the users who directly going to connect to > Qpid > > server. > > now users need to given the topic name with the domain name. > > > > But a better solution would be to give the tenant domain with the user > name > > and internally qpid authenticate the user and > > create the actually queue name. > > > > i.e a user will subscribe as > > > > us...@wso2.com to myTopic > > internally qpid process the user name and actually subscribes to > > wso2.com/myTopic. > > > > Danushka, is it possible to do this? If so I think even the carbonEvent > > compoent can use this convention which I belive is the best way. > > > > thanks, > > Amila. > > > > > > > > > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > > Srinath Perera, Ph.D. > Senior Software Architect, WSO2 Inc. > Visiting Lecturer, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
As I recall, we were discussing about Qpid MT with design meetings. Danushaka, what was the conclusion of those discussions? did we implement it? --Srinath On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi wrote: > hi, > > Shammi has started the $subject since registry required the multi tenancy > support and there is time > to finish this before end of march. > > Event Multi tenant has two parts > > 1. multi tenating topics and subscriptions stored in registry. > This can be done by using the tenant specific registry to store and retrieve > topics/subscriptions. > > 2. Qpid multi tenancy > I think Qpid does not support multi tenancy. so the possible way of > achieving multi tenancy is to append the domain name to > topic name then actual topics names would appear as follows. > > wso2.com/myTopic > ibm.com/myTopic > > But this gives a problem for the users who directly going to connect to Qpid > server. > now users need to given the topic name with the domain name. > > But a better solution would be to give the tenant domain with the user name > and internally qpid authenticate the user and > create the actually queue name. > > i.e a user will subscribe as > > us...@wso2.com to myTopic > internally qpid process the user name and actually subscribes to > wso2.com/myTopic. > > Danushka, is it possible to do this? If so I think even the carbonEvent > compoent can use this convention which I belive is the best way. > > thanks, > Amila. > > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Lecturer, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Event Multi tenant support
On Sun, Feb 27, 2011 at 7:12 PM, Amila Suriarachchi wrote: > hi, > > Shammi has started the $subject since registry required the multi tenancy > support and there is time > to finish this before end of march. > That's great. > > Event Multi tenant has two parts > > 1. multi tenating topics and subscriptions stored in registry. > This can be done by using the tenant specific registry to store and > retrieve topics/subscriptions. > +1 for this approach. Thanks, Senaka. > > 2. Qpid multi tenancy > I think Qpid does not support multi tenancy. so the possible way of > achieving multi tenancy is to append the domain name to > topic name then actual topics names would appear as follows. > > wso2.com/myTopic > ibm.com/myTopic > > But this gives a problem for the users who directly going to connect to > Qpid server. > now users need to given the topic name with the domain name. > > But a better solution would be to give the tenant domain with the user name > and internally qpid authenticate the user and > create the actually queue name. > > i.e a user will subscribe as > > us...@wso2.com to myTopic > internally qpid process the user name and actually subscribes to > wso2.com/myTopic. > > Danushka, is it possible to do this? If so I think even the carbonEvent > compoent can use this convention which I belive is the best way. > > thanks, > Amila. > > > > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; 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 Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Event Multi tenant support
hi, Shammi has started the $subject since registry required the multi tenancy support and there is time to finish this before end of march. Event Multi tenant has two parts 1. multi tenating topics and subscriptions stored in registry. This can be done by using the tenant specific registry to store and retrieve topics/subscriptions. 2. Qpid multi tenancy I think Qpid does not support multi tenancy. so the possible way of achieving multi tenancy is to append the domain name to topic name then actual topics names would appear as follows. wso2.com/myTopic ibm.com/myTopic But this gives a problem for the users who directly going to connect to Qpid server. now users need to given the topic name with the domain name. But a better solution would be to give the tenant domain with the user name and internally qpid authenticate the user and create the actually queue name. i.e a user will subscribe as us...@wso2.com to myTopic internally qpid process the user name and actually subscribes to wso2.com/myTopic. Danushka, is it possible to do this? If so I think even the carbonEvent compoent can use this convention which I belive is the best way. thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
