|
5 | 5 | [](https://www.python.org/download) |
6 | 6 | []() |
7 | 7 |
|
8 | | -This project is an effort to create Open-source implementation of a task execution engine based on the [TES standard](https://github.com/ga4gh/task-execution-schemas) |
9 | | -distributing executions to services exposing [Pulsar](https://github.com/galaxyproject/pulsar) application. For more details |
10 | | -on `TES`, see the Task Execution Schemas [documentation](https://ga4gh.github.io/task-execution-schemas/docs/). `Pulsar` |
11 | | -is a Python server application that allows a [Galaxy](https://github.com/galaxyproject/galaxy) server to run jobs on remote systems. The original intention of this |
12 | | -project was to modify the `Pulsar` project (e.g. via forking) so its Rest API would be compatible with the `TES` standard. |
13 | | -Later a decision was made that rather a separate microservice will be created, decoupled from the `Pulsar`, implementing the `TES` |
14 | | -standard and distributing `TES` tasks execution to `Pulsar` applications. |
| 8 | +This is a task execution microservice based on the [TES standard](https://github.com/ga4gh/task-execution-schemas) that sends job executions to [Pulsar](https://github.com/galaxyproject/pulsar) application. |
| 9 | + |
| 10 | +Read about our project on the [Galaxy Hub](https://galaxyproject.org/news/2025-10-06-tesp-api/) and [e-INFRA CZ Blog](https://blog.e-infra.cz/blog/tesp-api/). |
| 11 | + |
| 12 | +This effort is part of the [EuroScienceGateway](https://galaxyproject.org/projects/esg/) project. |
| 13 | +For more details on TES, see the [Task Execution Schemas documentation](https://ga4gh.github.io/task-execution-schemas/docs/). |
| 14 | +Pulsar is a Python server application that allows a [Galaxy](https://github.com/galaxyproject/galaxy) server to run jobs on remote systems. |
15 | 15 |
|
16 | 16 | ## Quick start |
17 | 17 |
|
@@ -279,3 +279,8 @@ longer configured to redirect stdout into the file. |
279 | 279 | | _TES_ | tasks `executors.workdir` and `executors.env` functionality is not yet implemented. You can use them but they will have no effect | |
280 | 280 | | _TES_ | tasks `volumes` and `tags` functionality is not yet implemented. You use them but they will have no effect | |
281 | 281 | | _TES_ | tasks `logs.outputs` functionality is not yet implemented. However this limitation can be bypassed with tasks `outputs` | |
| 282 | + |
| 283 | + |
| 284 | +History note: _The original intention of this project was to modify the `Pulsar` project so its Rest API would be compatible with the `TES` standard. |
| 285 | +Later a decision was made that rather a separate microservice will be created, decoupled from the `Pulsar`, implementing the `TES` |
| 286 | +standard and distributing `TES` tasks execution to `Pulsar` applications._ |
0 commit comments