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
49 Commits 6 Branches 0 Tags 107 MiB
Go 96.5%
Dockerfile 3.5%
6ab737c915
Go to file
mr 6ab737c915 test
2024-09-27 10:10:00 +02:00
.vscode minimize code + schedulerd naming + docker 2024-08-19 11:42:26 +02:00
conf simplify 2024-08-20 09:23:05 +02:00
daemons test 2024-09-27 10:10:00 +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
manifests for future k8s exec 2024-08-12 16:11:13 +02:00
.gitignore retrieve bookings from API and NATS 2024-07-11 18:26:40 +02:00
docker-compose.tools.yml test 2024-09-27 10:10:00 +02:00
docker-compose.yml simplify 2024-08-20 09:23:05 +02:00
Dockerfile simplify 2024-08-20 09:23:05 +02:00
go.mod test 2024-09-27 10:10:00 +02:00
go.sum test 2024-09-27 10:10:00 +02:00
LICENSE Initial commit 2023-10-18 17:04:06 +02:00
main.go change to fit update to oclib 2024-09-04 17:34:05 +02:00
oc-schedulerd test 2024-09-27 10:10:00 +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