You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are using ssh protocol to connect to the AWS instances. This is prone to errors and we are forced to use non-elegant solutions (eg #503 to check if the instance has finished work on the submission we need to check if the screen sessions exist, and either score file or log file including Python error).
This web service should run on an instance and listen to incoming connections from RAMP.
For example this could be RESTful API to receive submissions and run them, and serve the artifacts (results, logs, etc).
you would start a tiny REST API server on the worker?
I heard good things about https://fastapi.tiangolo.com/
not sure how much this is a rabbit hole...
Right now we are using ssh protocol to connect to the AWS instances. This is prone to errors and we are forced to use non-elegant solutions (eg #503 to check if the instance has finished work on the submission we need to check if the screen sessions exist, and either score file or log file including Python error).
This web service should run on an instance and listen to incoming connections from RAMP.
For example this could be RESTful API to receive submissions and run them, and serve the artifacts (results, logs, etc).
This should be started on the AWS instance at the initiation of the instance for each submission.
(https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html)
what are your thoughts @agramfort @rth @kegl ?
The text was updated successfully, but these errors were encountered: