Appendix B. GT 4.1.0 Call for Community Testing: RFT

1. What is a "Call for Community Testing"?

A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, we hope to expose the code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.

2. Participating in the RFT Testing Call is easy!

  1. Install the software in a non-production environment. Use the 4.1.0 distribution from http://www.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag globus_4_1_0.
  2. Exercise the software.
  3. Log your experiences in http://bugzilla.globus.org/globus/ under the "RFT" product. Please mention 4.1.0 explicitly in the body of the report.
  4. If you have any questions or comments regarding this component, join the rft-user@globus.org list to participate in discussions with other testers. (To subscribe, read the instructions here.)
  5. Optional: Consider sending descriptions of your tests to rft-dev@globus.org so that we might use them to build standard tests in the future. (To subscribe, read the instructions here.)

3. Testing period

The testing period for this call is [FIXME: date range].

4. About RFT

The Reliable Transfer Service (RFT) Service implementation in GT 4.1.0 uses standard SOAP messages over HTTP to submit and manage a set of 3rd party GridFTP transfers and deletion of files and directories using GridFTP. The service also provides an interface to control various transfer parameters of the GridFTP control channel like TCP buffer size, parallel streams, DCAU etc. The user creates a RFT resource by submitting a Transfer Request (consisting of a set of third-party gridftp transfers) to the RFT Factory service. The resource is created after the user is properly authorized and authenticated. RFT service implementation exposes operations to control and manage the transfers (the resource). The resource the user created exposes the state of the transfer as a resource property to which the user can either subscribe for changes or poll for the changes in state periodically using standard WS-RF command line clients and other resource properties.

5. Reasons for testing RFT

  • We need volunteers to exercise RFT to... [FIXME]

6. Technology dependencies

RFT depends on the following GT components:

  • Java WS Core
  • WS Authentication and Authorization
  • Delegation Service
  • Service Groups
  • MDS useful RP

RFT depends on the following 3rd party software:

  • PostgreSQL 7.1 or later. Not tested with 8.0 yet.
  • Apache Derby 1.1 (Packaged with the release

7. Environment/build parameters and other special conditions to test

  1. [FIXME]

8. For more information

For more information, see the RFT Release Notes.