Schedules looks for the next workflow to execute and starts them
Go to file
2025-04-17 19:58:19 +02:00
.vscode minimize code + schedulerd naming + docker 2024-08-19 11:42:26 +02:00
conf Merge branch 'feature/order' into main 2025-02-18 08:31:54 +01:00
daemons checking execution more often for dev purposes 2025-04-17 19:57:55 +02:00
docs neo oclib 2024-11-07 13:35:16 +01: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_schedulerd.json modify Docker related files to adapt to new architecture 2025-04-17 18:39:34 +02:00
docker-compose.yml adjustment 2025-03-28 08:48:12 +01:00
Dockerfile Merge branch 'main' of https://cloud.o-forge.io/core/oc-schedulerd into feature/order 2025-04-17 18:38:19 +02:00
go.mod loki traefik + neo oclib 2025-02-21 11:24:56 +01:00
go.sum loki traefik + neo oclib 2025-02-21 11:24:56 +01:00
LICENSE Initial commit 2023-10-18 17:04:06 +02:00
main.go Added some test and logging on the path to execute monitord 2025-04-17 19:58:19 +02:00
Makefile adjustment 2025-03-28 08:48:12 +01:00
oc-schedulerd Use regular conf oclib library instead of custom implem to leverage env variable injection fonctionality; Dockerfile refactor 2025-01-14 18:33:51 +01:00
README.md dev launch mode 2025-03-06 09:33:03 +01:00

oc-scheduler

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

make dev

## 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

CHANGE ENV FOR KUBE

Add your proper CA, Cert & Data + external IP for kube config.