Apache Airavata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This page is to describe the integration testing steps for Airavata release verification and effort to automate those test for future release.

SCOPE

Airvata testing for running Grid (XSEDE, Campus Clusters) and Cloud jobs to verify the release. You need to have knowledge about running applications on XSEDE or other cluster to perform part of these tests.

Verify Build

  1. Compile the project with an empty Maven repository mvn install -Dmaven.repo.local=/tmp/cleanrepo
  2. Verify the modules/distribution/ (Make sure size of each distribution is less than 100MB)
    • airavata-server
      1. /apache-airavata-server-<version>-bin.tar.gz
      2. target/apache-airavata-server-<version>-bin.zip
      3. target/aapache-airavata-server-<version>.war.tar.gz
      4. target/apache-airavata-server-<version>.war.zip
    • airavata-client
      1. target/apache-airavata-client-<version>-bin.tar.gz
      2. target/apache-airavata-client-<version>-bin.zip
    • xbaya-gui
      1. target/apache-airavata-xbaya-gui-<version>-bin.tar.gz
      2. target/apache-airavata-xbaya-gui-<version>-bin.zip
  3. Untar/zip the Airavata server bin distribution to verify the embedded version.
  4. Untar/zip the Xbaya GUI bin distribution and work with embedded version of Airavata server.
    • Follow the instructions to run 5 min and 10 min tutorials.
  5. Deploy the war distribution to Tomcat 7. Follow Deployment Guide to configure Airavata on Mysql and Tomcat. Guide also have details on server property configuration.
  6. Use Xbaya GUI bin distribution to perform test.

Test Registry (Xbaya currently)

  1. Add a new host to the registry.
  2. Edit the exiting host by updating all the properties and verify the changes
  3. Try to add/edit different types of hosts.
  4. Add applications for each type of host configuration. You can use local/SSH/GSISSH/GRAM5 protocols in Airavata to run your applications. You need to update airavate-server.properties for security setting for above protocols.
  5. Edit Applications to make sure all the parameter can be updated and saved to registry.

Test Running Workflow (Xbaya currently)

Test Airavata API

h3.Note: Add test scenarios for other components like Messaging, XBaya, Workflow

  • No labels