You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by er...@apache.org on 2017/04/07 20:32:10 UTC
airavata-docs git commit: Modifications for airavata 0.17 release
Repository: airavata-docs
Updated Branches:
refs/heads/master 2cdb3e67b -> f7ca13eed
Modifications for airavata 0.17 release
Project: http://git-wip-us.apache.org/repos/asf/airavata-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/airavata-docs/commit/f7ca13ee
Tree: http://git-wip-us.apache.org/repos/asf/airavata-docs/tree/f7ca13ee
Diff: http://git-wip-us.apache.org/repos/asf/airavata-docs/diff/f7ca13ee
Branch: refs/heads/master
Commit: f7ca13eed98204da0b7bb7cbefd1f7a6805d5aad
Parents: 2cdb3e6
Author: Eroma Abeysinghe <er...@gmail.com>
Authored: Fri Apr 7 16:32:06 2017 -0400
Committer: Eroma Abeysinghe <er...@gmail.com>
Committed: Fri Apr 7 16:32:06 2017 -0400
----------------------------------------------------------------------
Gateway-Configurations.md | 35 +++++++++++++++++++++++------------
1 file changed, 23 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/airavata-docs/blob/f7ca13ee/Gateway-Configurations.md
----------------------------------------------------------------------
diff --git a/Gateway-Configurations.md b/Gateway-Configurations.md
index 103a31b..9457807 100644
--- a/Gateway-Configurations.md
+++ b/Gateway-Configurations.md
@@ -10,7 +10,7 @@
2. Gateway Admin need to configure;<br>
- <a href="#CompResource">Compute Resources</a><br>
- <a href="#StoreResource">Storage Resources</a><br>
- - <a href= "#Preference">Resource Preferences</a><br>
+ - <a href= "#Preference">Gateway Management</a><br>
- <a href= "#AppCatalog">Application Catalog</a><br>
- Application Module<br>
- Application Interface<br>
@@ -18,14 +18,19 @@
- <a href= "#Credentials">Credential Store</a>
- Generate Credential Store Token + SSH Key.
- Add these to authorized key files and into resource preferences.
-<br>
+ - <a href= "#Notices">Notices</a>
+ - Notices for all active gateway users.
+ - <a href= "#ISConfiguration">Identity Management</a>
+
+<b>NOTE</b>: for gateways hosted by SciGaP gateway admins/PIs not required to register the compute resources and storage resource. Please skip the 1st and 2nd and go to Gateway Management section.
<br>
###<h3 id="CompResource">Compute Resources</h3>
1. Navigate to Admin Dashboard ⇒ Compute Resources ⇒ Register
2. Add Host Name, Description and create the resource.
+<br>Hint: host name is used when ssh to the resource from airavata.
3. 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)
+ - Queues (Queue name is unique 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. So can skip if you want)
- Job Submission Interfaces
- Data Movement Interfaces
5. Similarly you can add multiple compute resources in to your gateway by selecting 'Register' from the left-hand-side menu.
@@ -38,13 +43,14 @@
2. Add Storage Name, Description and create the resource.
3. Then add data storage information in
- Data Movement Interfaces
-5. Similarly you can add multiple storage resources in to your gateway by selecting 'Register' from the left-hand-side menu.
-6. To view the added resources navigate to Admin Dashboard ⇒ Storage Resources ⇒ Browse
-7. All the resources will be listed. Gateway admin can view, edit, delete them.
+4. Similarly you can add multiple storage resources in to your gateway by selecting 'Register' from the left-hand-side menu.
+5. To view the added resources navigate to Admin Dashboard ⇒ Storage Resources ⇒ Browse
+6. All the resources will be listed. Gateway admin can view, edit, delete them.
+7. Although enable and disable can be done in registration it's functionality is not yet implemented.
<br>
<br>
-###<h3 id="Preference">GatewayPreferences for Resources</h3>
-1. Navigate Admin Dashboard ⇒ Gateway Profile
+###<h3 id="Preference">Gateway Management of Resources</h3>
+1. Navigate Admin Dashboard ⇒ Gateway Management
2. Both compute resource and storage resource specific preferences are defined here.
3. To add compute resource related preferences click "Add a Compute Resource Preference" and select the resource from the drop-down list.
4. Add/select preferred options and click "Set preferences".
@@ -52,11 +58,16 @@
4. 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 job submission protocols
+ - Preferred 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)
+ - Resource specific credential store token <br>(When added Base Credential Store Token is not valid for the specific resource)
+ - Gateway ID for usage reporting <br>(This field will only appear if the compute resource registration is set to report usage details back to the resource)
+ - Quality of service
+ - Reservation name
+ - Reservation start and end date time
5. For adding storage resource preference click "Add a Storage Resource Preferences", and rest is similar to adding a compute resource preference.
6. 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.
7. For storage resource preference, gateway admin need to add;
@@ -101,7 +112,7 @@
4. Generated key can be either assigned at gateway level; one key + token pair for all the resources OR have separate key for each resource.
5. SSH keys are used for communication with compute resources, storage resources and WSO2 identity server.
-### <h3 id="Preference">WSO2 IS Configuration</h3>
+### <h3 id="ISConfiguration">Identity Server Configuration</h3>
1. Setting up WSO2 IS for the new gateway.
2. 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.
3. For user identity management we could either use Airavata WSO2 IS or users own WSO2 IS.