|
|
|
*(AKA: Stuff that broke when I tried to use Bridges)*
|
|
|
|
|
|
|
|
- DB files must exist locally or the code bails. This is fine when running directly, but when using BOSCO this means the DB will get staged again for every run via SSH. Would be better to allow specifying a location on the remote resource. This would require people to manually copy the files initially, but then Pegasus would just do symlinking for each run.
|
|
|
|
|
|
|
|
- Default resource requirements are way off.
|
|
|
|
|
|
|
|
- The BOSCO installer for a remote resource doesn't include the helper script to translate Pegasus resource specifications to SLURM job attributes (`slurm_local_submit_attributes.sh`). Not really a chipathlon problem, but needs fixed.
|
|
|
|
|
|
|
|
- The code that adds things in the `jobs/scripts` directory as executables is also picking up the `.pyc` byte-compiled files. Doesn't really break anything, but should be cleaned up.
|
|
|
|
|
|
|
|
- All the executables are added using `site="local"`. That's probably ok for things in `jobs/scripts` and `jobs/wrappers`, but the system commands (mv, cp, etc.) should be added using the remote site. If added using local, Pegasus will copy the binaries, which might cause issues if the submitting machine is a different enough version of Linux (or OS X even). |
|
|
|
\ No newline at end of file |
