Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor WebAPI Workflow #124

Closed
joschrew opened this issue Aug 26, 2022 · 1 comment
Closed

Refactor WebAPI Workflow #124

joschrew opened this issue Aug 26, 2022 · 1 comment
Assignees

Comments

@joschrew
Copy link

joschrew commented Aug 26, 2022

In the last sprint I refactored the workspace Part of the API. Mongodb was added to store information about a workspace in the database. For the workflow-part the mongodb should also be used to store information about jobs and to be able to send a job-status to the user. Overview about things to be done in this "refactoring":

  • use mongodb for jobs (and possibly for workflow-scripts)
  • refactor "run_workflow" to "better" fit to the specification
  • add GET /workflow/{workflow_id}/{job_id}. Therefore the mongdb is needed
  • fix (some) open tasks mentioned in the source-code and some open issues related to the workflow
  • revise the tests to fit the other mentioned changes
  • the outcome of this task should be an available test-server with which it is possible to upload a workspace and a workflow and run the workflow on the workspace
@joschrew joschrew self-assigned this Aug 26, 2022
@joschrew
Copy link
Author

joschrew commented Sep 9, 2022

Status:

  • code-refactoring finished for now
  • the service is available in gönet (e.g. curl 141.5.99.53:5050/workspace). Since it would be possible to upload any nextflow-script and run it, I don't want to make it publicly available
  • currently no processors except ocrd-dummy are available or useable. So running workflows is quite useless currently
  • I don't know yet how to do the setup (regarding the processors), how to make the processors available. I would try to find that out in the next sprint: Make ocrd-processors available inside webapi to be used with workflows #128

@joschrew joschrew closed this as completed Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant