Schedules looks for the next workflow to execute and starts them
Go to file
2024-08-12 16:08:34 +02:00
conf integrated oclib 2024-08-09 18:44:33 +02:00
daemons integrated oclib 2024-08-09 18:44:33 +02:00
docs scheduler doc 2024-07-11 18:27:57 +02:00
k8s commit before rebuild 2024-07-29 15:45:32 +02:00
logger integrated oclib 2024-08-09 18:44:33 +02:00
manifests commit before rebuild 2024-07-29 15:45:32 +02:00
models improved graph/workflow retrieval 2024-07-23 12:16:20 +02:00
.gitignore retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
docker-compose.yml added schedule network 2024-08-12 16:08:34 +02:00
Dockerfile Dockerfile for scheduler 2024-07-03 10:21:17 +02:00
execution_manager_test.go commit before rebuild 2024-07-29 15:45:32 +02:00
go.mod integrated oclib 2024-08-09 18:44:33 +02:00
go.sum integrated oclib 2024-08-09 18:44:33 +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 integrated oclib 2024-08-09 18:44:33 +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