Re: [Carbon-dev] Multi tenanting background tasks
Guys do this type of discussion on architecture@ please. On Sat, Sep 24, 2011 at 12:37 PM, Tharindu Mathew thari...@wso2.com wrote: On Sat, Sep 24, 2011 at 12:06 PM, Prabath Abeysekera praba...@wso2.comwrote: Hi Tharindu, On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew thari...@wso2.comwrote: Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? I believe, you're referring to the schedule tasks component (pardon me if it's not). So here, If I'm not mistaken, this suggestion can be split into two main parts namely, 1. Multitenanting tasks (This is already available AFAIK) How is this achieved? Can you explain? 2. Storing tasks related configurations in the registry. Delving into the second point, which is persisting task configurations in the registry, we too have this requirement for DSS and for the moment we accomplish this by handling it in DSS side (which might not be the best suited solution). A better solution would be to handle it in scheduled-tasks component itself. So, +1 for a better way to persist task configurations. IMO, we should refactor the carbon tasks. But that aside, storing task configurations in a multi tenanted manner, is a platform requirement. +1 for this. I will also use the same workaround for now. -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Regards, -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: praba...@wso2.com harsha...@wso2.com Mobile: +94774171471 http://harshana05.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; 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 Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multi tenanting background tasks
Hi Tharindu, On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew thari...@wso2.com wrote: Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? I believe, you're referring to the schedule tasks component (pardon me if it's not). So here, If I'm not mistaken, this suggestion can be split into two main parts namely, 1. Multitenanting tasks (This is already available AFAIK) 2. Storing tasks related configurations in the registry. Delving into the second point, which is persisting task configurations in the registry, we too have this requirement for DSS and for the moment we accomplish this by handling it in DSS side (which might not be the best suited solution). A better solution would be to handle it in scheduled-tasks component itself. So, +1 for a better way to persist task configurations. -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Regards, -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: praba...@wso2.com harsha...@wso2.com Mobile: +94774171471 http://harshana05.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multi tenanting background tasks
An example would be for BAM: Tenant 1 would configure a task, example: summarizing to run on his data. Tenant 2 would not want this summarizer. But, he has another task which polls a web service as a heartbeat mechanism and records results. So, depending on the tenant we would only allow the task to access only their own key space/ database in their data storage. We also need to load/save the task configurations in the registry ( this part should be trivial). Hope the example is clear. On Sat, Sep 24, 2011 at 6:08 AM, Samisa Abeysinghe sam...@wso2.com wrote: What tenant specific task(s) are you talking about? Can you give some example? I assume the ESB task component can run in multi tenant mode. Samisa... On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew thari...@wso2.comwrote: Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? -- Regards, Tharindu blog: http://mackiemathew.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 -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multi tenanting background tasks
On Sat, Sep 24, 2011 at 12:06 PM, Prabath Abeysekera praba...@wso2.comwrote: Hi Tharindu, On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew thari...@wso2.comwrote: Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? I believe, you're referring to the schedule tasks component (pardon me if it's not). So here, If I'm not mistaken, this suggestion can be split into two main parts namely, 1. Multitenanting tasks (This is already available AFAIK) How is this achieved? Can you explain? 2. Storing tasks related configurations in the registry. Delving into the second point, which is persisting task configurations in the registry, we too have this requirement for DSS and for the moment we accomplish this by handling it in DSS side (which might not be the best suited solution). A better solution would be to handle it in scheduled-tasks component itself. So, +1 for a better way to persist task configurations. IMO, we should refactor the carbon tasks. But that aside, storing task configurations in a multi tenanted manner, is a platform requirement. +1 for this. I will also use the same workaround for now. -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Regards, -- Prabath Abeysekara Software Engineer WSO2 Inc. Email: praba...@wso2.com harsha...@wso2.com Mobile: +94774171471 http://harshana05.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Multi tenanting background tasks
Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? -- Regards, Tharindu blog: http://mackiemathew.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Multi tenanting background tasks
What tenant specific task(s) are you talking about? Can you give some example? I assume the ESB task component can run in multi tenant mode. Samisa... On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew thari...@wso2.com wrote: Hi everyone, I believe many products have this requirement. How can we do $subject? I was thinking of storing task related configurations in the tenant's registry. The task engine then executes the task only allowing access to resources that the specific tenant has access to. WDYT? -- Regards, Tharindu blog: http://mackiemathew.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
