This discussion started in the mailing list: https://listsprd.osu.edu/pipermail/ood-users/2018-October/000245.html
The suggestion is this:
treat a provided directory as the staging directory (not copying). Maybe
just adding a manifest.yml to that provided directory. Ideally allowing
users to just use the GUI rather than navigate over a plain ssh
I think there are two thoughts here:
- Provide a new option to the New Job list: Use Specified Path. Instead of copying the job directory to
- Choosing the path should provide a file chooser dialog experience rather than just ask the user for a full path in a text field
Since a “Job” in Job Composer is really a job directory, it would seem implementing this (except for the file chooser) would be straight forward. I think the form should set the
Workflow#staged_dir to the path to use instead of the
Note: the file chooser could make use of the same Files API server side to get the directory listing etc. https://github.com/OSC/ood_appkit#files-app
This would streamline the process for adding a single directory that already exists as a job directory to the Job Composer. I guess if you do this a warning should be given if you are adding a directory like this that you do not own.
The only negatives is that it would be pointing to a completely different location than the “default project” directory. What would be best is if this feature were added in conjunction with the new project management interface we’ve internally discussed adding to Job Composer, where a project == a new parent directory for job directories (related issue https://github.com/OSC/ood-myjobs/issues/124). With both of these features in place one could imagine a simple view to add a check list of existing directories under a project directory as job directories all at once.