GridFTP Test Plan

TableOfContents

1 Testing and Verification Plan 1.1 Test Environment 1.1.1 Test server installation 1.2 Defects and Issues 1.3 Tests 1.3.1 Software Versions to Test 1.3.2 GridFTP-Basic 1.3.3 GridFTP-Prod-and-Test-Servers 1.3.4 GridFTP-GO-Endpoint 1.3.5 GridFTP-Usage-Stats-Verify 1.3.6 Verify GSI cipher list blocking

Testing and Verification Plan

Test Environment

The tester will need at least 3 host/machines with root access for deploying a GridFTP server with multiple backends configured. Also, a Globus Online account will be required for creating and testing a test endpoint using the test GridFTP server. Additionally, confirmation from the central XSEDE Globus Usage Stats Server that the usage stats were successfully sent will be necessary.

Test server installation

• Install latest GridFTP server using the administrator guide linked here: http://software.xsede.org/development/globus-gridftp-xsede/latest/XSEDE-GridFTP-install.html. More notes and instructions are here: http://toolkit.globus.org/toolkit/docs/6.0/admin/install/ . Xsede certificate setup information is here: https://www.xsede.org/security/certificates
• To test individual installation, use the following test package:

  Note: Perl Test::Harness is required for this test framework

  • Current state of test package: wget http://www.mcs.anl.gov/~mlink/xsede/gridftp-server-test-2.tar.gz
  • tar xfz gridftp-server-test-2.tar.gz
  • README file has deatils
  • cd gridftp-server-test
  • ./run-test [host1] [host2]

Note: this test package is designed to run between hosts that share a shared filesystem, or on a single host (as both source and destination). If you do not have two hosts that share a filesystem, running on a single host is sufficient. If a single host is used as both source and destination, you may need to up instances, per_source, and cps values to 2000 in the /etc/xinetd.d gsiftp and gsiftpdata files, and may need to expand GLOBUS_TCP_PORT_RANGE to 50000,52000.

• The above test does the following reporting: It prints out progress (test, success, test success, etc) as it goes, but no reports. There are multiple main tests, each with subtests. All main tests will always attempt to run. If any of the subtests fail, that main test will stop immediately and print ERROR. At the end of all tests, ERROR will be printed if there were any errors, and the test will exit with a nonzero return code so it can be scripted. If no errors, exit code will be 0 and "Success" will be printed.

Defects and Issues

1. Any issues at the testing phase should be reported to "smartin@mcs.anl.gov".

Tests

Software Versions to Test

The version of GridFTP to test is from Globus Toolkit version 6.0

GridFTP-Basic

• Description
  • Run a set of tests used by the Globus team to verify the server is operational
• Prerequisites
  • User has a XSEDE account and an entry in the GridMap file
• Steps:
  • install a "production" GridFTP server per the XSEDE GridFTP installation Guide
  • download the test program
  • run the test program
• Results:
  • User should see output from the test program indicating success
• Notes:

GridFTP-Prod-and-Test-Servers

• Description
  • Perform 2 installations on the same host. One setup a an XSEDE production server and a second as an XSEDE test server. Verify each can co-exist and each can be used independently. This will be a common situation for the GridFTP lifecycle on XSEDE.
• Prerequisites
  • User has a XSEDE account and an entry in the GridMap file
• Steps:
  • install a "production" GridFTP server per the XSEDE GridFTP installation Guide
  • install a "test" GridFTP server per the XSEDE GridFTP installation Guide
  • download the test program
  • run the test program against the production server
  • run the test program against the test server
• Results:
  • User should see output from the test program indicating success for both the production and test servers
• Notes:

GridFTP-GO-Endpoint

• Description
  • After successfully installing and testing a GridFTP server, create a GO endpoint for that server and use it in a GO transfer.
• Prerequisites
  • User has a XSEDE account and an entry in the GridMap file
  • User has a production GridFTP server installed and working
  • User has a GO account
• Steps:
  • User logs into GO website
  • User creates the endpoint for the production GridFTP server
  • User submits a transfer using the new endpoint
• Results:
  • User receives an email from GO indicating success once the transfer is complete
• Notes:

GridFTP-Usage-Stats-Verify

• Description
  • If the GridFTP server is properly configured following the XSEDE GridFTP admin guide, then it should have sent a usage stat packet/record for each of the test transfers from the above tests. Check with the XSEDE Usage Stats System Admin (Lukasz Lacinski,lukasz@ci.uchicago.edu) to verify these packets contain the extra user information and were properly stored in the XSEDE Usage Stats DB. Also, have Lukasz verify that the usage stats sent to the Globus Usage Stats DB do not contain the extra user information.
• Prerequisites
  • User has successfully executed all above tests.
• Steps:
  • Look up transfer UUID from the Globus Transfer performed in the previous test. The transfer UUID can be found in globus.org activity tab transfer detail as "Task ID".
  • Send email to Lukasz with transfer UUID and ask him to verify the usage records were correct
• Results:
  • User receives an email reply from Lukasz stating that the usage stats are correct.
• Notes: