-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsteps.txt
57 lines (30 loc) · 1.58 KB
/
steps.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
1. create agave account
2. create github account if they dont’ have one
3. claim the VM we assigned to them ahead of time
Rion creates accounts on the VM's on Jetstream
based on the user's agave credentials.
4. login to a hub (a.k.a. a Jupyterhub)
6. login to their sandbox from the hub
7. find the funwave app in their sandbox home (edited)
8. build the source
9. build the source image
10. schedule auto-build
11. kick off auto-build and publish
12. Run thei published image on their sandbox
13. verify output showed up (edited)
14. view the output in their notebook
15. generate a quick viz of their output, create some metadata
16. save the notebook to their work directory, gnerate a postit, and share the link
17. Now share their system and app with another user (for i in jetsteam-gw17-training-[0-20]; apps-pems-addupdate…) (edited)
18. rerun the app and sample data across all the hosts shared with them and tehir own
19. see the results show up
20. introduce jupyter ui components to turn the previous step into a simple UI
21. Rerun a job with the UI
22. Update source. commit, and let image rebuilt.
23. rerun job through UI
24. compare results and see changes show up
25. save notebook again
26. Run notebook itself as a batch agave app on another host they haven’t used (just another jetstream VM)
(optional) 27. Run funwave as container on jetstream cluster, @lsu, @tacc though same notebook to see portability
(optinoal) 28. Show same UI and accesssibility in microsite on github
(optinoal) 29. Show same UI and accesssibility in agave togo on github (edited)