You Need to Have
- Airavata & PGA installed and running.
- Tenant created in WSO2 IS hosted by you or Airavata team.
- Administrator privileges to the gateway. (How do you know? - Can you view Admin Dashboard and view buttons to create applications)
Apache Airavata Component Configuration
- For this we use ‘Admin Dashboard’
- Gateway Admin need to configure;
- Compute Resources
- Storage Resources
- Resource Preferences
- Application Catalog
- Application Module
- Application Interface
- Application Deployment
- Credential Store
- Generate Credential Store Token + SSH Key.
- Add these to authorized key files and into resource preferences.
- Navigate to Admin Dashboard ⇒ Compute Resources ⇒ Register
- Add Host Name, Description and create the resource.
- Then keep adding information on rest of the appeared tabs.
- Queues (Queue name is uniqie and cannot be updated. Can delete and create new if required)
- File Systems (This is only for information capturing for future use. Currently this information is not used)
- Job Submission Interfaces
- Data Movement Interfaces
- Similarly you can add multiple compute resources in to your gateway by selecting ‘Register’ from the left-hand-side menu.
- To view the added compute resources navigate to Admin Dashboard ⇒ Compute Resource ⇒ Browse
- All the resources will be listed. Gateway admin can view, edit, delete and enable and disable them.
- Navigate to Admin Dashboard ⇒ Storage Resources ⇒ Register
- Add Storage Name, Description and create the resource.
- Then add data storage information in
- Similarly you can add multiple storage resources in to your gateway by selecting ‘Register’ from the left-hand-side menu.
- To view the added resources navigate to Admin Dashboard ⇒ Storage Resources ⇒ Browse
- All the resources will be listed. Gateway admin can view, edit, delete them.
###GatewayPreferences for Resources
- Navigate Admin Dashboard ⇒ Gateway Profile
- Both compute resource and storage resource specific preferences are defined here.
- To add compute resource related preferences click “Add a Compute Resource Preference” and select the resource from the drop-down list.
- Add/select preferred options and click “Set preferences”.
Repeat this for all the resources used within the gateway.
- For each compute resource, gateway admin need to specify;
- Preferences can be overridden by Airavata - Yes/No?
- Resource login name
- Preferred job submission and data movement protocols
- Preferred queue
- Scratch location
- Project allocation number
- Resource specific credential store token (When added Base Credential Store Token is not valid for the specific resource)
- For adding storage resource preference click “Add a Storage Resource Preferences”, and rest is similar to adding a compute resource preference.
- For a gateway currently when a storage resource is selected, that resource ID need to be added in to the pga_config.php file in config folder of the hosted gateway.
- For storage resource preference, gateway admin need to add;
- Login username
- File System Root Location
- Resource Specific Credential Store Token
- Apart from adding preference the same interface is used to assign a 'Base Credential Store Token". If this is added this is the token used across the gateway for communication with all the compute resources and storage resource.
- Gateway admin add applications in to the gateway. Adding an application is a 3 step process.
- Admin need to add application module, interface and deployment information in order to launch specific application jobs on compute resources.
- Relationship between application module, interface and deployments.
- What each step means?
- Application Module
- Navigation: Admin Dashboard ⇒ App Catalog ⇒ Module
- This is the simple introduction of the application; Name, Version and Description.
- Click ‘Create a New Application Module’, provide information and create. On creation Application Module ID will be generated for the module.
- All existing modules are listed; Search by name is available for a particular module.
- Gateway admin can edit, delete existing modules.
- Deleting a module will be restricted if it has application interfaces and deployments linked.
- Application interface
- Navigation: Admin Dashboard ⇒ App Catalog ⇒ Interface
- Application interface defines the required inputs, outputs produced and their characteristics.
- Click on ‘Create a New Application Interface’, provide information and create. On creation Application Interface ID will be generated for the module.
- All available interfaces are also listed; admin has the option of searching for a particular interface by providing the name in the search.
- Gateway admin can edit, delete existing interfaces.
- Gateway admin cal also clone an existing interface in order to create a new similar interface with slight changes.
- Application deployment
- Navigation: Admin Dashboard ⇒ App Catalog ⇒ Deployment
- Application deployment describes application deployment details on a specific resource.
- For an application for each resource there is a separate deployment.
- A single application can be deployed in multiple resources.
- Multiple application modules can be deployed in a single resource. E.g: Gaussian09 and Gaussian16 both exists in bridges.psc.edu and they both use same application interface.
- Navigation: Admin Dashboard ⇒ Credential Store
- This interface is used to generate SSH key + token pairs.
- These generated keys can be added in to the authorized key files in each resource for SSH key based communication.
- Generated key can be either assigned at gateway level; one key + token pair for all the resources OR have separate key for each resource.
- SSH keys are used for communication with compute resources, storage resources and WSO2 identity server.
WSO2 IS Configuration
- Setting up WSO2 IS for the new gateway.
- Once PGA is cloned all information related to user identity will be in app/config/pga_config.php. No modifications required for users who are using hosted IS.
- For user identity management we could either use Airavata WSO2 IS or users own WSO2 IS.
- Download WSO2 Identity Server 5.0 from http://product-dist.wso2.com/products/identity-server/5.0.0/wso2is-5.0.0.zip
- Extract the downloaded IS binary archive to a location <IS_HOME>.
- Set JAVA_HOME variable and add jdk bin directory to the PATH variable.
- Open <IS_HOME>/repository/conf/carbon.xml and change the following property to false <HideAdminServiceWSDLs>false</HideAdminServiceWSDLs>
- Execute the following command to run the server sh <IS_HOME>/bin/wso2server.sh You should be able to login to the Identity Server Web App using your browser with url http://localhost:9443/carbon . Default admin credentials are username: admin, password: admin
- For more information regarding WSO2 Identity Server refer WSO2 IS Server
Gateway admin will be provided with;
- Domain URL for the Gateway
- Admin User name