Skip to content
This repository was archived by the owner on Mar 29, 2022. It is now read-only.

Commit 0a62992

Browse files
author
Joshua Urrutia
committed
adding example with -F flag to help with app.ini/app directory conflicts
1 parent 94bf4f9 commit 0a62992

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

docs/03.migrate_from_maverick.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ title: Migrating Apps from Maverick
44
tagline:
55
---
66

7-
With Maverick reaching the end of its service, we will need to migrate apps off of Maverick onto another HPC resource. Luckily, due to containerization, this process is pretty painless. You'll simply need to replace the `executionSystem` in the app definition (app.json.j2) from `hpc-tacc-maverick-username` to the newly created `hpc-tacc-wranlger-username`.
7+
With Maverick reaching the end of its service, we will need to migrate apps off of Maverick onto another HPC resource. Luckily, due to containerization, this process is pretty painless. You will simply need to replace the `executionSystem` in the app definition (app.json.j2) from `hpc-tacc-maverick-username` to the newly created `hpc-tacc-wranlger-username`.
88

99

1010
<br>
11-
#### Updated App Definition
11+
#### Example of an Updated App Definition
1212

1313
This is an example of a converted Agave app definition:
1414
{% raw %}
@@ -52,7 +52,11 @@ This is an example of a converted Agave app definition:
5252
{% endraw %}
5353

5454
#### Final steps
55-
After updating the app definition to point to `hpc-tacc-wrangler-username`, you can simply run `apps-deploy` to deploy the app to the new execution system. Make sure to double check the `app.ini` file to ensure it points to the correct DockerHub username, repo, etc. Once the application has been deployed you should run a test job to ensure it's working correctly.
55+
After updating the app definition to point to `hpc-tacc-wrangler-username`, you can simply run `apps-deploy` to deploy the app to the new execution system. Make sure to double check the `app.ini` file to ensure it points to the correct DockerHub username, repo, app name, and app version. If the app name and version in the app.ini differ from the name/version of the app directory, you can use a -F flag with `apps-deploy` to point to the correct app definition, ex:
56+
```
57+
apps-deploy -F app_directory-0.1.1/app.json.j2
58+
```
59+
Once the application has been deployed you should run a test job to ensure it's working correctly.
5660

5761

5862

0 commit comments

Comments
 (0)