Table of Contents |
---|
...
style | circle |
---|
...
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)
Use Case II
Enter details of the application (Amber) which has the same version (V 12) deployed in multiple supercomputers (BigRed II & Stampede)
...
Update details of a created workflow which executes using multiple applications deployed in the supercomputsupercomputer
Search for the workflow in the supercomputer
Add a another application in to the newly defined workflow node
...
Update details of a published workflow which executes using multiple applications deployed in the supercomputsupercomputer
Search for the workflow in the supercomputer
Add a another application in to the newly defined workflow node
...
Search for the workflow in the supercomputer-I & supercomputer-II
Add a new application to the new workflow node which is in the supercomputer-I
Remove existing application from a existing node which is in the supercomputer-II
Use Case I
Clone an existing application deployment which is in CREATED state and its owned by the same gateway
Search for the Application using application ID/Resource/Status/etc….
Clone the application and create the new application
The new application will get saved in CREATED state
Use Case II
Clone an existing application which is in PUBLISHED state and its owned by the same gateway
Search for the Application using application ID/Resource/Status/etc….
Clone the application and create the new application
The new application will get saved in CREATED state
Use Case III
Clone an existing application which is in CREATED state and its owned by the a different gateway
Search for the Application using application ID/Resource/Status/etc….
Clone the application to create the new application
Cloning between gateways will be restricted
Use Case IV
Clone an existing application which is in CREATED state but flagged as non-cloneable and owned by the same gateway
Search for the Application using application ID/Resource/Status/etc….
Clone the application to create the new application
Cloning will be restricted as the primary application is flagged as non-cloneable
Use Case V
Clone an existing workflow which is in CREATED state and its owned by the same gateway
Search for the workflow using workflow ID/Status/etc….
Clone the workflow to create the new workflow
The new workflow will get saved in CREATED state
Use Case VI
Clone an existing workflow which is in CREATED state and its owned by a different gateway
Search for the workflow using workflow ID/Status/etc….
Clone the workflow to create the new workflow
Cloning between gateways will be restricted
Use Case VII
Clone an existing workflow which is in PUBLISHED state but flagged as non-cloneable and owned by the same gateway
Search for the workflow using workflow ID/Status/etc….
Clone the workflow to create the new workflow
Cloning will be restricted as the primary workflow is flagged as non-cloneable
NOTE: Importing applications & workflows are done ONLY between gateways.
Use Case I
Import an application in CREATED state from a different gateway and create a new application
Search for an application from other gateways using gateway ID/Application ID/Application Name, /Resource/etc…
Select the application and import
A new instance will get imported leaving the primary application in the specific gateway
The new application will get saved as a CREATED application
Use Case II
Import an application in PUBLISHED state from a different gateway and create a new application
Search for an application from other gateways using gateway ID/Application ID/Application Name, /Resource/etc…
Select the application and import
A new instance will get imported leaving the primary application in the specific gateway
The new application will get saved as a CREATED application
Use Case III
Import an application in PUBLISHED state from a different gateway which is flagged as non-importable
Search for an application from other gateways using gateway ID/Application ID/Application Name, /Resource/etc…
Select the application and import
Importing the application details will fail as the primary application is tagged as non-importable
Use Case IV
Import a workflow in CREATED state from a different gateway and create a new workflow
Search for the workflow from other gateways using gateway ID/workflow ID/workflow Name, /etc…
Select the workflow and import
A new instance will get imported leaving the primary workflow in the specific gateway
The new workflow will get saved as a CREATED workflow
Use Case V
Import a workflow in CREATED state from a different gateway which is tagged as non-importable
Search for the workflow from other gateways using gateway ID/workflow ID/workflow Name, /etc…
Select the workflow and import
Importing the workflow details will fail as the primary workflow is tagged as non-importable
Use Case I
Delete a selected application deployment from the resource. The particular application has only a single deployment
Search for the application by giving the application ID
Delete the selected application deployment
The application is no longer available for the gateway users.
NOTE: Existing experiments which used or currently using the application will not have any impact
Use Case II
Delete a selected application deployment from the resource. The particular application has multiple deployments in multiple resources
Search for the application by giving the application ID
Delete the selected application deployment
The application is no longer available for the gateway users.
NOTE: Existing experiments which used or currently using the application will not have any impact
Use Case III
Delete a selected application deployment from the resource. The particular application has two different application versions deployed in the same resource. Only one of those is required to be deleted.
Search for the application by giving the resource ID
Delete the selected application deployment
The application is no longer available for the gateway users.
NOTE: Existing experiments which used or currently using the application will not have any impact. New users can only use the remaining version in the same resource.
Use Case IV
Delete all deployments of a selected application. Application has multiple versions and multiple deployments in multiple resources.
Search for all the application deployments (all versions)
Delete them all
The application is no longer available for all the gateway users using Airavata.
NOTE: This is possibly a Airavata ADMIN task.
Use Case V
Delete all deployments of a selected application. Application has multiple versions and multiple deployments in multiple resources.
Search for all the application deployments (all versions)
Delete them all
The application is no longer available for the gateway.
NOTE: This is possibly a Gateway ADMIN task. Only the application deployments of that particular gateway will get affected. Other gateways would have their deployments of the same application remaining.
Use Case I
Turn off a specific application from all the supercomputers it is been deployed in
Search for all the application deployments (different versions as well)
Temporarily turn-off all of them
Gateway users will not be able to create or launch experiments using the particular application
NOTE: Any ongoing experiments will not be interrupted. This is a gateway ADMIN level task.
Use Case II
Turn off a specific application deployment from a supercomputer it is been deployed in
Search for the application by providing the resource
Temporarily turn-off the particular application deployment
Users will not be able to create or launch experiments using the particular application deployment in the resource
NOTE: Any ongoing experiments will not be interrupted. This is a gateway ADMIN level task.
Use Case III
Turn off all the applications in Stampede for 48 hours as it is not available to launch experiments
Search for all the applications by providing the resource
Turn-off all the applications in the resource by giving start and end date/time
Users will not be able to create ,launch, list experiments in the particular resource for 48 hours
After 48 hours applications will be auto turned ON to use
Use Case IV
Turn on the specific application from all the supercomputers it is been deployed in
Search for the application by providing the application ID
Turn-on through method call in all resources
Users will be able to create,launch, list experiments using the particular application
Use Case V
Turn on the specific application version which was turned off from only one supercomputer
Search for the application version by providing the application ID
Turn-on through method call in all resources
Users will be able to create,launch, list experiments using the particular application
Use Case VI
Turn off a specific workflow by searching for the using the workflow ID
Temporarily turn-off the workflow
Gateway users will not be able to create or launch experiments using the particular workflow
NOTE: Any ongoing experiments will not be interrupted. This is a gateway ADMIN level task.
Use Case VII
Turn off all the workflows which runs one or many applications residing in Big Red II
Search for the applications in Big Red II which are used in the workflow
Temporarily turn-off all the workflows using applications from the supercomputer
Users will not be able to create or launch experiments using the particular application deployment in the resource
NOTE: Any ongoing experiments will not be interrupted. This is a gateway ADMIN level task.
Use Case VIII
Turn on the specific workflow which was turned OFF at workflow level
Search for the workflow by providing the workflow ID
Turn-on the workflow
Users will be able to create,launch, list experiments using the particular application
Use Case IX
Select a workflow which is turned of at resource level and turn it on
Search for all the workflow by providing the workflow ID/workflow name
Turn-on all the workflow
workflow cannot be turned on as it was turned OFF at resource level. use has to turn it ON at resource level
Use Case X
List all the applications/workflows in the Big Red II which are turned-on
Search for all the application deployments by giving ‘turn-on’ as current status
Use Case XI
List all deployments of the ‘application WRF’ which are in turned-on state
Search for all the application deployments of ‘application A’ & has state as ‘turn-on’
Use Case XII
List all workflows which runs application WRF and in turned-on state
Search for all the workflows which runs WRF & has state as ‘turn-on’
Use Case XIII
List all the applications/workflows in the supercomputer-I which are turned-off
Search for all the application deployments by giving ‘turn-off’ as current status
Use Case XIV
List all deployments of the ‘application A’ which are in turned-off state
Search for all the application deployments of ‘application A’ & has state as ‘turn-off’
Use Case XV
List all workflows which are in turned-off state
Search for all the workflows with state as ‘turn-off’
Use Case XVI
List all deployments of the ‘application A’ irrespective of the application active state
Search for all the application deployments of ‘application A’
Use Case XVII
List all deployments of the particular gateway which are in ‘turn-on’ state
Search for all active application deployments
Use Case XVIII
List all deployments of the particular gateway which are in ‘turn-off’ state
Search for all inactive application deployments