[hyades-dev] Meeting minutes for November 20th Hyades Execution Team Mee

[Kent D Siefkes <kdsiefke@xxxxxxxxxx>]

I have attached the meeting notes for this week's execution team meeting.  

Thanks,
Kent


Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, November 18, 2003

Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Antony Miguel, Scapatech
Stephane Leroy, IBM Rational Toulouse
Todd Merriweather, IBM Rational Raleigh


Proposed Agenda
---------------
1. Review final datapool runtime API (Joe) - see recent email from Joe Toomey
2. Need/interest in execution invocation APIs to enable another test's code to be called from an executing test, while running within the calling test's JVM (instead of a separate deployment involving a new JVM) - Kent
3. 1.2 development open issues, dependencies, blocking issues, etc. - Joe, Todd, all


Recorded Discussion/Decisons (new discussion/status preceded by *)
------------------------------------------------------------------
1. Review final datapool runtime API (Joe)

	Comments:
	A. Kent - Can we have ability to generically initialize an iterator (such as to initialize with a unique random # seed)
	B. Kent - Should really consider repackaging to execution.runtime.datapool instead of execution.datapool
	C. Joe - Edit interface should have ability to read the contents of a cell without processing it

2. Need/interest in execution invocation APIs to enable another test's code to be called from an executing test,
   while running within the calling test's JVM (instead of a separate deployment involving a new JVM) - Kent

	Discussed the limitation of the currest test harness APIs for invoking tests of different types from within another Hyades
	test (such as a schedule) for load testing, due to the inherent inefficiency of requiring a separate JVM invocation for
	each called test.  We agreed this was something we need, and discussed two requirements:
		1. An interface to query to see if a set of execution components for a test type support this capability.
		2. A runtime invocation API to be supplied by the test runner.

	Recommendation is to push both of these requirements into Hyades 1.3

3. 1.2 development open issues, dependencies, blocking issues, etc. - Joe, Todd, all

	Joe - working on hiearachy of execution events (runner, loader pieces - Ashish is out last two weeks)
	Brian - test execution viewer UI for displaying hierarchial events
	Sonny Pak - support for stop/suspend/resume
	Andrew - working on datapool runtime API
	Andrew (or Peter or Joe, if needed) - datapool edit API
	Peter - datapool editor UI
	HTTP - iteration 1 complete with some defects & enhancements being deferred to iteration 2
 
New Action Items
----------------
* None