Scheduling Workflow Sample Clauses

Scheduling Workflow. ‌ 1. The DECICE Control Manager updates the cluster via the platform-specific glue code wrapper to set up new pods in response to a new requests coming into the system or rescheduling 2. ▇▇▇▇▇▇▇▇▇▇ notices that pods are pending that have no node assigned 3. Kubernetes requests a scheduling decision 4. The request is forwarded to the custom endpoint exposed by the platform-specific glue code 5. The glue code translates the request into DECICE’s internal representation and forwards it to the DECICE Control Manager 6. The DECICE Control Manager considers relevant configurations from the DECICE Config Store 7. The DECICE Control Manager triggers a refresh of the metrics for the Digital Twin from the Metrics Storage 8. The DECICE Control Manager forwards the scheduling request to a scheduler installed in the DECICE Model 9. The DECICE Scheduler pulls in the current system state from the Digital Twin 10. The scheduler considers the current system state and the queue of unscheduled jobs/pods and then generates a scheduling decisions 11. The scheduler sends the scheduling decision back to the DECICE Control Manager 12. The DECICE Control Manager updates the Digital Twin accordingly and sends the scheduling decision as response back to the platform-specific glue code 13. The glue code translates the response to a valid responds for the scheduling request and responds to the original scheduling request 14. Kubernetes persists the response and acts on it