[news.eclipse.tools.hyades] Re: Hyades design?

[mgn@xxxxxxxxxxxxx (Mike Norman)]

Bryan Hunt wrote:

> I've been reading over your docs and I have some questions:

> Do you have any Use Case models I can take a look at?

Stuff is appearing over the next few days that may cover your needs. 
There is a backlog which has been built and not yet posted.  Give it a
week and come back to us if you need more info.

> Are the communication and execution frameworks plugable?  I'm going to 
> need to provide my own implementation of those.

The communication and execution frameworks are pluggable.  A number of
vendors currently see performance and scalability, reliability etc. at
this layer as being a value-add.  THe Execution group is working on the
API which this pluggable layer has to present into the workbench.  There
will be a reference implementation based upon the IBM RAC, but the tool
compatibility point is the Execution API. 

The other key compatibility point is the test model. Again, don't
initially expect all execution environments to deal with all tests
expressible in the test model, but do expect universal test execution
environments to emerge over time. 

> At first read, it appears you are targeting a small-scale testing 
> environment.  Any interest in looking at a large-scale environment?

There's nothing in the architecture that precludes scalability of tooling
based upon it. Scalability of the initial reference implementations will
be limited and vendors will be able to add value through enhanced
scalablity for the forseeable future, but the bar is likely to lift over
time.

> Are you looking for additional participants on the project?

Yes.  You should download drivers models etc (as they emerge) and start
playing with them.  Once you are familiar with them we can have a
conversation about how you feel able to contribute.

> Would you consider significant changes to the existing design?

There's a lot of flexibility in the current design (much of which is
poorly articulated in the docuemntation).  We should explore that before
committing to making changes.

> Bryan