On 03/04/2013 01:58 PM, Platonides wrote:
A few machines where you install the different tools. So you wouldn't need to manage a complete VM, or install apache for your web app. You would place the tool in the appropiate dir and it_should_ just work. Quite similar to how toolserver worked, but more tool-centric (as if you created a MMP per tool, but easier).
That's a very good nutshell.
The basic outline is thus: there is a compute grid and a webserver cloud (and, in the future, databases and other common services) that are managed at the project levels by the roots. Those are made available to all the tools.
Each "tool" is, essentially, storage, a webspace, a set of permissions, a user, and a group. Members of the group are the tool's maintainers and have complete control over it. They can queue jobs or continuous tasks, and put what they need in their webspace to function. They'll also have permission over future resources (like databases, etc).
-- Marc