Hi, Please find the attached file that shows my current plan on CDL component test cases. In order to test CDL resolution, I think we need to have a special API. I will develop unit test code with such API if we agree on that. Thanks, Jun Milojicic, Dejan S wrote:
Hi,
My homework from the last meeting was to talk to Hiro about interoperability. I have done so and Hiro asked me to discuss this with Cees, whom I communicated with by email (see my earlier email today). I'll continue this investigation further with people who have pursued interoperability within IETF in the past.
I also discussed with Hiro how we can continue our engagement with OGSA. We are scheduled to be on the OGSA call next Wednesday, 11/9. We will address the homework we had received while at F2F after GGF, and which we have addressed at the first meeting after GGF.
The assignment for the meeting tomorrow was for everyone to think of the dependencies they may have from others so that we can start tracking progress we are making towards reference implementations. I would like to start tracking using GridForge trackers.
Please use our usual phone numbers:
+1 866-639-4732 (toll free while in US) Code 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international)
Thanks,
Dejan.
-----Original Message----- From: Milojicic, Dejan S Sent: Wednesday, October 26, 2005 6:49 AM To: 'cddlm-wg@ggf.org' Subject: Notes from the meeting
Attendees: Stuart, Steve, Ayla, Dejan.
Notes taker Dejan.
We discussed how to demonstrate that something constitutes a reference implementation. We suggested the following steps:
1. Individual components tests (every owner will contribute one).
2. Use cases:
a) Single app
b) Multi-tier, one machine
c) Multi-tier, multi-machine
3. Optional: Grid computing apps (Blast, Globus)
4. Optional: Scale experiments
Steve suggested that he will write a draft of the test components by next week, a more complete suggestion in two weeks.
Everyone will write a dependency list that they have on other components so that we create a roadmap from now until next GGF. One good example of dependencies is component tests that should be available as early as possible so that reference implementations can test their compatibility. We do not want to track detailed plan of individual reference implementations although we want to have some sense of the overall progress we are making and whether we shall have reference implementations completed for the next GGF.
Dejan will talk to Hiro today to find out about the proofs for interoperability and compatibility (if any).
Thanks,
Dejan.