Schedules looks for the next workflow to execute and starts them
| conf | ||
| docs | ||
| .gitignore | ||
| argo_builder.go | ||
| classe_scheduler.puml | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| graph.go | ||
| graph.xml | ||
| http.go | ||
| LICENSE | ||
| main.go | ||
| oc-scheduler | ||
| README.md | ||
| template_models.go | ||
| volume_models.go | ||
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