core/oc-schedulerd

Schedules looks for the next workflow to execute and starts them

Go to file

pb b43cb6d758 cleaned README, need to add more documentation in it		2025-04-18 11:27:24 +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	added logging to see if monitord is running well	2025-04-17 19:59:33 +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	modify Docker related files to adapt to new architecture	2025-04-17 18:37:48 +02: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	cleaned README, need to add more documentation in it	2025-04-18 11:27:24 +02:00

README.md

oc-scheduler

oc-schedulerd is a daemon performing to actions at the same time :

subscribing to the local NATS instance' custom channels for message commanding either the scheduling or the removing of an execution.
polling oc-catalog for scheduled executions

Depending on the environment it is running in, oc-schedulerd will either :

execute the oc-monitord binary
run an oc-monitord container