Open wvengen opened 12 years ago
The solution for issue #4 implemented loading the configuration from LGI_* files on the resource. Still different LGI API calls are used for job submission and querying are used, these still need to be implemented. The feature set does not overlap completely with user-side submission.
This may be possible by LGI already by resource daemon submission (using a different LGI API than user submission). If the user decides to submit new jobs from a resource in his R code, it would make sense that these jobs appear in the user's job list. This can be done by setting the owners
field to include the user upon submission.
Currently Rlgi only works on a user's local computer. It would be nice to be able to run lgi.par?apply() from a compute node as well. In the last hands-on session, people expected it to work from the web LGIportal web interface. For intuitiveness only it would be useful to have. For production it may be useful to have the local node do computations as well, because in the current approach it's just waiting.
This requires loading key, certificate (and possibly other settings) from the LGI_* files in the current directory instead of ~/.LGI or ~/LGI.cfg. Security is another issue that needs to be looked at.