Dec. 3, 2009

Generalized coordinated schedule for multiple resources. Leave this item for discussion in January's face to face meeting. Module needs to know the commitment of all resources to make co-scheduling decision. OSCARS does not provide the full commitment picture. In the future, we can look into the OSCARS. So far, we need to look into source SRM, destination SRM, and TeraPaths, and look for the best match. A co-scheduling might be a follow-up project after StorNet finishes.

Short report. We can have a boilerplate for the summary that is same for both BNL and LBNL. Each site needs to submit a separate report.
August 01, 2009 is the beginning date of the project.
December 14, 2009 is the target date for completing the report and reviewing for each other.

January 27 and 28 for 1.5 days.
Email to reserve our parking space, and instruction. Dantong will send email to Rachel to ask for parking reservation.

Technical Discussion of BeStMan-to-TeraPaths interface

Dimitrios:

Went through TeraPaths code.
Updated document for API.
Went through the draft specification.
Could be more than one solution that can satisfy the reservation request.
Two options: shortest completion time or shortest transfer duration. Should we include this as an option into the API? Yes, we can have an option for the shortest completion time, the shortest transfer time or nothing. The default one will be “do not care”. Only return one transfer time window for now. As a long term goal, an interface for more than one window for a single request need to be developed to improve data transfer efficiency. (some discussion on how to handle multi-window, i.e. each window should have its own reservation ID).

Junmin’s comments to the current TeraPaths interface:

Some question regarding 60 seconds to commit after reservation. It might not be long enough for SRM to react.
Dimitrios: This 60 second will be internal to TeraPaths. SRM does not need to worry about it in reserveAndCommit call.
Remove the obsolete entries in the WSDL.
The returned data structure should include the proper error messages.
TeraPaths needs to have a separate set of interface for StorNet project. The StorNet interface does not need to include the interfaces that are not directly related with StorNet.
The source and destination parameters should be flexible to allow clients to pick host, subnet. Suggest to use entries of “Key/Value” pair.
Agreed on the time representation. Use long integer to represent time in milliseconds. Need to convert to UTC when needed for human readable format.
getReservationStatus(): What will be returned in the call? Dimitrios will propose a set of information as status. TeraPaths will include this functionality in the first version.

Xin:

Have implemented simulation platform.
Simulate different reservation mechanisms in TeraPaths.
Simulate the scalability of TeraPaths. For example, we can simulate the multi-window reservation for a particular request and evaluate the effectiveness.

Alex:

Setup the web site, and provided access to everyone involved: http://sdm.lbl.gov/stornet
The email list is setup
The draft StorNet interface (BeStMan-TeraPaths interface) is posted on the web. Dimitrios can make comments and update to the interface.

Action items