core/oc-schedulerd
6
0
Fork 0
Code Issues 6 Pull Requests Packages Projects Releases Wiki Activity
Schedules looks for the next workflow to execute and starts them
6 Commits 6 Branches 0 Tags 132 MiB
Go 96.5%
Dockerfile 3.5%
a485831a01
Go to file
pb a485831a01 update component id with the one in the links
2024-04-09 15:03:12 +02:00
.gitignore initial commit 2023-10-18 17:08:53 +02:00
go.mod retrieve computing objects from workflow json 2024-04-04 12:31:12 +02:00
go.sum initial commit 2023-10-18 17:08:53 +02:00
graph.go update component id with the one in the links 2024-04-09 15:03:12 +02:00
graph.xml initial commit 2023-10-18 17:08:53 +02:00
http.go initial commit 2023-10-18 17:08:53 +02:00
LICENSE Initial commit 2023-10-18 17:04:06 +02:00
main.go Changed component's retrieving from parsing XML to using the stored info in DB 2024-04-09 11:20:08 +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

README.md

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