Schedules looks for the next workflow to execute and starts them
Go to file
2024-07-11 18:26:40 +02:00
conf added conf/ and configuration logic 2024-07-03 10:22:22 +02:00
daemons restructuration 2024-07-11 18:25:40 +02:00
docs UML executiong management 2024-07-05 17:44:53 +02:00
logger restructuration 2024-07-11 18:25:40 +02:00
models retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
.gitignore retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
argo_builder.go restructuring 2024-07-05 15:28:24 +02:00
Dockerfile Dockerfile for scheduler 2024-07-03 10:21:17 +02:00
go.mod retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
go.sum retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
graph.go retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
graph.xml retrieve Links 2024-04-16 19:38:21 +02:00
LICENSE Initial commit 2023-10-18 17:04:06 +02:00
main.go restructuration 2024-07-11 18:25:40 +02:00
oc-scheduler added conf/ and configuration logic 2024-07-03 10:22:22 +02:00
README.md Changed component's retrieving from parsing XML to using the stored info in DB 2024-04-09 11:20:08 +02:00

oc-scheduler

OC-Scheduler retrieves the content of submitted workflows and prepare them to be executed.

## Parsing

From a workflow's name we retrieve the xml graph associated and parse it in order to create the object representing each componant. Each object is linked to another, represented by a links object with the two object IDs has attributes.

TODO :

  • Retrieve the user input's for each component.

## Organising

TODO :

  • [ ] create an argo file from the graph/worfklow
    • [ ] Create a different entry for each component
    • execute each element in the right order