Page History

Table of Contents
style circle

General Assumptions

1. Single Application Catalog will exists in Airavata to be used by all the gateways.
2. Each gateway will be creating, updating, deleting, etc... their own application deployments in the supercomputers.
3. Each gateway will have ADMIN users who would do above tasks in the Application Catalog
4. Airavata ADMIN users will be able to view details entered through all the gateways using Airavata instance. They can also search and view application deployments;
   E.g.:
   • Search for all applications which are in turned-on state in all supercomputers
   • Search for application deployments of  specific gateway
5. If necessary Airavata ADMIN users will also be able to maintain application deployments across gateways.
   
6. Applications and workflows will always be deployed, created (workflows will be created using XBAYA), etc... prior to entering in the Application Catalog.

...

Enter details of application deployment (WRF) in supercomputer (Big Red II) into the Application Catalog.

• Create a new application deployment  instance in the catalog

• Add supercomputer detail which has it deployed

• Define application specific, application deployment specific information and parameters required to use the application

• Application specific information such as;

• • Application version

  • Input & output file sizes (maximum file size)

  • Input and output file locations (scratch locations)

  • duration of scratch location holding the output files

  • Error file and log file locations

• Application deployment specific information;

  • Deployed application version

  • Deployed Application description

  • Deployed location

  • Application accessible providers (GSI-SSH)

• E.g.: Define echo application in Big Red II (or some other application)
  • Step 1 : Define Big Red II details

...

• • •  Host address : bigred2.uits.iu.edu

...

• • •  Remote Access Protocol : GSI-SSH

...

• • •  Port : 22

...

• • •  Installed Path : /opt/torque/bin/

...

• • • Authentication : ???
  • Step 2 : Define application details
  • •  Input : [name: echo_input, type:String]

...

• • •  Output : [name: echo_output, type:String]

...

• • •  Executable Location : /bin/echo

...

• • •  App version : 1.0
  • Step 3 : Define Job details

...

• • •   Scratch Location : /home/ogce/scratch

...

• • •  
    •  Project Account : sds128

...

• • •  Queue Type : normal

...

• • •  CPU Count : 1

...

• • •  Job Type : Serial

...

• • •  Node Count : 1

...

• • •  Processors Per Node : 1

...

• • •  Max Wall Time : 10

Use Case II

Enter details of the application (Amber)  which has the same version (V 12) deployed in multiple supercomputers (BigRed II & Stampede)

• Create two instances of the application deployments  in the catalog for each supercomputer deployment with application version information  

• Define general set of application parameters for the deployment in first supercomputer

• Define resource specific set of parameters for the second supercomputer deployment

Use Case III

Enter details of the application (Amber)  which has the same application version (V 12) deployed in BigRed II but with different deployment variations; mpi & gpu

• Create two instances of the same application version in the catalog for Big Red II

• Define one instance as MPI deployment and other as GPU deployment

• Define the mandatory primary parameters and additional advance parameters for both instances

Use Case IV

• Enter details of WRF application which has two different versions (cray/3.5 & 3.4.1) deployed in Big Red II & Quarry supercomputers

• Create two instances of the application deployments  in the catalog for each supercomputer deployment for each version

Use Case V

Create two instances of application Scorep with two different versions (gnu/1.2beta & gnu/1.2.3) which are deployed in the Big Red II

• Create two instances of the application deployment in Big Red II with different versions

• One version of Deployment will have general set of application parameters

• The second version will have supercomputer specific set of parameters

Use Case VI

Create an application deployment instance which will not be visible to the gateway user to select at the time of creating experiment.

• Create the application deployment with a flag to say ‘ NOT visible’

Use Case VII

Create an application deployment instance which can only be used in workflows; not available for single submissions.

• Create the application deployment with a flag to say ‘ ONLY for workflows’

Use Case VIII

Create an application deployment which has its deployments in supercomputers hidden from the gateway users

• Create the application deployment with a flag to say ‘ Hidden deployments’

NOTE: Gateway users can only select the application but not the supercomputer; user will not know where the application is running

...

Enter details of an workflow and its nodes which executes using multiple applications deployed in Big Red II

• Create the workflow in the catalog and define the supercomputer as supercomputer-I

• Define the applications which will be used in the workflow

Use Case X

Enter details of the workflow which executes using multiple applications from two different supercomputers (Stampede & Lonestar)

• Create the workflow and its nodes  in the catalog and define the multiple supercomputers which runs the applications

• Define the applications which will be used in the workflow from each supercomputer

Publish Application/Workflow

...

Assumption: Each gateway will enter details of their application deployments in to the application catalog.

E.g. if two gateways are using the same application version deployed in the same supercomputer there will be two records in the catalog; one record for each gateway.

...