Call for Community Testing: 3.9.4 RLS

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, the Globus Alliance hopes to expose its 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.

Participating in the RLS Testing Call is easy!

  1. Optional: Consider sending mail to [email protected] to let us know that you're helping out and describing what you intend to test.
  2. Install the software in a non-production environment. Use the 3.9.5 distribution from http://www-unix.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag [tag].
  3. Exercise the software.
  4. Log your experiences in http://bugzilla.globus.org/globus/ under the "Replication Services" product "RLS" component. Please mention 3.9.5 explicitly in the body of the report.
  5. Optional: Consider sending descriptions of your tests to [email protected] so that we might use them to build standard tests in the future.
  6. If you have any questions or comments about the process, send an email to [email protected].
  7. If you have any questions or comments regarding this component, join the gt4-friends list to participate in discussions with other testers. (To subscribe, send an email to [email protected] containing the words "subscribe gt4-friends" in the message body.)

Testing period

The testing period for this call is December 17 - January 31 2005.

About RLS

Reasons for testing RLS

RLS is available for a variety platforms (Linux, UNIX flavors). We can only maintain a small number of possible platforms and most of our work takes place on RedHat Linux 7 and 9 and with MySQL server for database management. In addition, the distributed nature of RLS, and the wide array of use cases that can be satisfied with it, make it difficult to simulate the many production configurations that exist for the RLS.

Technology dependencies

Environment/build parameters and other special conditions to test

  1. Build, install, and test on RedHat (ES, AS), Fedora, and Debian flavors of Linux.
  2. Build, install, and test on FreeBSD, Solaris, AIX, and HP-UX flavors of UNIX.
  3. Build and test Java clients using JDK 1.4 compliant JVM's from vendors other than Sun (e.g., IBM).
  4. Deploy with PostgreSQL and Oracle for database management.
  5. Test large-scale deployment with multiple sites for LRC and RLI services in fully connected and partially connected architectures.
  6. Test large-scale deployment by registering several million logical and physical file names at each LRC and propagate to connected RLIs.
  7. Test large-scale deployment using C Client API to execute 1000's of bulk operations per second.