Repository: airavata-docs Updated Branches: refs/heads/master 2cbcc70f2 -> d4adcf445
Added link to Airavata update page and typo fix Project: http://git-wip-us.apache.org/repos/asf/airavata-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/airavata-docs/commit/d4adcf44 Tree: http://git-wip-us.apache.org/repos/asf/airavata-docs/tree/d4adcf44 Diff: http://git-wip-us.apache.org/repos/asf/airavata-docs/diff/d4adcf44 Branch: refs/heads/master Commit: d4adcf44502ee3e40911fb5d76bb6b13a28cf79a Parents: 2cbcc70 Author: Eroma Abeysinghe <[email protected]> Authored: Fri May 13 13:52:56 2016 -0400 Committer: Eroma Abeysinghe <[email protected]> Committed: Fri May 13 13:52:56 2016 -0400 ---------------------------------------------------------------------- Airavata-Upgrades.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/airavata-docs/blob/d4adcf44/Airavata-Upgrades.md ---------------------------------------------------------------------- diff --git a/Airavata-Upgrades.md b/Airavata-Upgrades.md index ec2712c..a06446e 100644 --- a/Airavata-Upgrades.md +++ b/Airavata-Upgrades.md @@ -1,6 +1,5 @@ -## Airavata Code Upgrade +## Airavata Update -### Updating Airavata Codebase 1. In order to update Airavata with latest master code; go to the folder (Created in installation; LocalAiravata) initially created to clone Airavata. 2. Within your local folder navigate to folder 'airavata' and execute <pre><code>git pull </code></pre> Hint: If you are in the wrong folder you would probably get message <pre><code>'fatal: Not a git repository (or any of the parent directories): .git'</code></pre> @@ -19,17 +18,22 @@ Navigate to bin folder where airavata server exists (LocalAiravata/apache-airava 7. Un-tar the copied new release <pre><code>tar -xvf apache-airavata-server-0.16-SNAPSHOT-bin.tar.gz</code></pre> 8. Navigate to the new bin folder and back up airavata-server.properties and gfac-config.yaml files. -8. Copy your previously used airavata-server.properties from the backed up release to bin folder (This is the easiest way to get the properties file updated. If you prefer, you can change the new file manually. ☺) +9. Copy your previously used airavata-server.properties from the backed up release to bin folder (This is the easiest way to get the properties file updated. If you prefer, you can change the new file manually. ☺) <pre><code>/<your local path>/LocalAiravata/LocalAiravata/apache-airavata-server-0.16-SNAPSHOT-bk/bin/airavata-server.properties .</code></pre> -9. Copy your previously used gfac-config.yaml from the backed up release +10. Copy your previously used gfac-config.yaml from the backed up release <pre><code>cp /<your local path>/LocalAiravata/apache-airavata-server-0.16-SNAPSHOT-bk/bin/gfac-config.yaml .</code></pre> -10. Now compare with the new airavata-server.properties and gfac-config.yaml and make necessary changes in the copied files. -11. Check the path correctness of credential store keystore in airavata-server.properties file. +11. Now compare with the new airavata-server.properties and gfac-config.yaml and make necessary changes in the copied files. +Try <pre><code> diff airavata-server.properties airavata-server.properties-bk</code></pre> +12. Check the path correctness of credential store keystore in airavata-server.properties file. <pre><code>credential.store.keystore.url=/<your local path>/LocalAiravata/airavata_sym.jks</code></pre> -12. Go to lib folder and copy mySQL jar (mysql-connector-java-5.1.38-bin.jar) from old backed up lib to the new lib +13. Go to lib folder and copy mySQL jar (mysql-connector-java-5.1.38-bin.jar) from old backed up lib to the new lib <pre><code> cp /home/airavata/LocalAiravata/apache-airavata-server-0.16-SNAPSHOT-bk/lib/mysql-connector-java-5.1.38-bin.jar .</code></pre> -13. Now restart airavata server in bin folder +14. Now restart airavata server in bin folder <pre><code>./airavata-server.sh start</code></pre> +15. Airavata ready for job submissions! +16. For PGA updating steps try <a href="../PGA-Upgrades">PGA Update</a> + +
