core/oc-schedulerd
5
0
Fork 0
Code Issues 6 Pull Requests Packages Projects Releases Wiki Activity
Schedules looks for the next workflow to execute and starts them
20 Commits 6 Branches 0 Tags 132 MiB
Go 96.5%
Dockerfile 3.5%
eab5162389
Go to file
pb eab5162389 minor fixes
2024-07-02 12:24:23 +02:00
docs diagrams documentation 2024-07-02 12:24:03 +02:00
.gitignore minor fixes 2024-07-02 12:24:23 +02:00
argo_builder.go minor fixes 2024-07-02 12:24:23 +02:00
classe_scheduler.puml diagrams documentation 2024-07-02 12:24:03 +02:00
go.mod full argo yaml, NEED TO BE TESTED 2024-05-07 19:45:20 +02:00
go.sum succesfully create a working argo worflow for alpr 2024-05-14 15:15:30 +02:00
graph.go minor fixes 2024-07-02 12:24:23 +02:00
graph.xml retrieve Links 2024-04-16 19:38:21 +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 improved structure, doc and naming 2024-05-03 10:58:06 +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
template_models.go full argo yaml, NEED TO BE TESTED 2024-05-07 19:45:20 +02:00
volume_models.go full argo yaml, NEED TO BE TESTED 2024-05-07 19:45:20 +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