Hi Simon, Please see my answers in line:
On 6/22/07, Simon Laws <[EMAIL PROTECTED]> wrote:
Can I just check that I understood what you have said. I.e. that "there will be only one ODE server instance on which processes will be deployed". Does this mean, 1 ODE server instance per Tuscany runtime node (a tuscany Java SCA runtime in a Java VM) - I think this is the case given what you say about module activator Or 1 ODE service instance per machine that handles any number of tuscany runtime nodes.
Your first statement is the right one yes, one ODE server per Tuscany runtime node. I'm asking because one of the things I'm interested in is how we manage a
domain running across multiple runtime nodes.
So if I understand correctly we're talking about clustering here. As far as ODE is concerned, I believe both deployment models should be supported: one single ODE instance that all Tuscany nodes use (locally or remotely depending on where the instance is physically instantiated) and one instance per node (and in that second deployment model, ODE would need to support clustering). From the ODE standpoint the first mode is the easiest to support (no need to be clustering aware and handle state propagation) and it's not quite what we're doing right now. So I guess we'd have to migrate at some point to that mode when it's possible? Looking to the future I have to be able to provide such data out to nodes
remotely. To allow for this each distributed runtime node starts a small SCA assembly purely for managing meta data, I.e. it defines services with interfaces for reading and writing specific meta data. In that way I can use any SCA binding to send data to a node. So a binding could still allow the data to be read from a (distributed) file system but it doesn't have to be.
Sounds good. That's actually more or less what I was thinking of when I mentioned the usage of files, configuration or any type of external resource. Ideally, within Tuscany, ODE shouldn't care about where things are physically located. I'm not suggesting you do anything about this specifically yet but I would
like to talk about it as the implementation progresses just in case we have to do anthing to keep ODE happy.
Yep, good idea. When the implementation matures we'll have to answer to those questions so it's good to ask them early :) Thanks, Matthieu Regards
Simon
