Dec. 2, 2010

Attendees: Dantong, Dimitrios, Junmin, Viji

#5 Currently we use SRM client and interface. We would like to have a separate client interface for the bandwidth reservation, so that client makes bandwidth reservation first, checks the status, and then makes SRM requests based on the bandwidth reservation.
#6 This is the bestman-bestman coordination API/interface for storage bandwidth reservation and status check.
bestman will need to finish up negociation test, multi-request test and db integration.

#1 is not completed yet
#2, #7, #8, #9 are completed
#3, #4 are in progress
#5, #6 need clarification and discussion.
#10 is completed. We have one request with one file. Intention is for bestman to handle many requests asking reservations.
#11 is for setup the bestman between BNL and LBNL. #11 is about test plan for STAR. We will need to ask PDSF and Jerome the test feasibility. For the testbed on DOE sites, we should use ESnet ANI tabletop testbed which will give us root access to the kernel and possible access to switches and routers. The testbed will be back online in Feb. 2011. Until then we should continue using BNL-UMich, our current friendly testbed.
We will need to test multiple transfers in one single request, migrate to a large database, need to update the bandwidth information if the TeraPaths returns a different reservation as a result of negotiation.

#1: we choose layer 2. Uni or bi directional?
#2: 2.1 and 2.2 are done, 2.3-2.5?
#3, #4, #5, #6: Done.
#7: We will focus on our effort to setup this testbed between BNL and LBNL. For STAR use case, we need a discussion with PDSF and Jerome to start with.
For the next six months, complete the functions of API, and implement the negotiation.