Page1    Page115                                                                        Page117  Page177

2.

Further code development:

·

Addition of a suite of a sophisticated web interface, web services, and a secure program

API to facilitate user and application generated reservations. GridFtp developers with the

GLOBUS group at Argonne National Lab have developed C-based client software based

on the TeraPaths API to invoke TeraPaths dynamic network provisioning services and

reserve network bandwidth between the end sites of the TeraPaths testbed.

·

Addition of basic user AAA infrastructure

·

Tightening of security through use of accounts, https, and server- and client-side

authentication server-specific and user DOE grid certificates

·

Addition of ssh-based hardware (router) drivers

3.

Interoperability with WAN services:

Development of necessary client software to support new specifications and interfaces

with new Java-based implementation of the OSCARS software (in close cooperation with

the ESnet and Internet2 OSCARS development teams).

4.

Documentation:

Creation of official TeraPaths website containing documentation on the project and the

software; software downloads, installation instructions and examples; conference

publications and slide presentations: http://www.terapaths.org.

5.

Software integration:

Commenced development of a Command Line Interface (CLI) module and plug-ins for

popular data transfer software (e.g., SRM/dCache). We generalized the concept of

dCache/Storage Resource Manager network plug-ins and implemented the necessary

framework for any network control plug-in additions. We integrated TeraPaths network

provisioning services into the dCache software framework to enable storage services to

make network bandwidth reservation prior to data transfers and bring the quality of

service guarantee up to the level of the storage service layer.

6.

Collaborative activities:

We initiated research into issues involved with the utilization of dynamic circuits (L2

connections) by end sites; utilizing such circuits using policy based routing within an end

site essentially enables flow-specific routing along with QoS guarantees. We organized

the 2nd TeraPaths Interoperability workshop at BNL in May 2007 with developers and

researchers from ESnet, Internet2, University of Michigan, and BNL. The workshop

proposed solutions for connectivity issues between TeraPaths-enabled end-sites and

ESnet, and Internet2 dynamically provisioned L2 connections, as well as for software

interoperability issues.

116