orchard/internal/controller
Fedor Korotkov f152043f19
Reactive Scheduling (#67)
Before we had two main loops: controller loop to assign VMs and worker loop to start VMs. Each of the loops was performed upon an interval every N seconds.

This change introduces a mechanism for reactively requesting loop execution:

 1. Controller loop will be executed upon VM creation to try to immediately schedule.
 2. A worker will be notified upon a VM assigment and worker loop will be requested to sync immediately.

 Fixes #31
2023-03-28 20:51:41 +04:00
..
notifier Remove UID for now and use machine ID to differentiate workers (#48) 2023-03-23 23:38:54 +04:00
proxy Refactorings for simplify readability (#35) 2023-03-17 06:11:28 -04:00
scheduler Reactive Scheduling (#67) 2023-03-28 20:51:41 +04:00
store Events Entity (#28) 2023-03-13 08:04:17 -04:00
api.go REST API: provide error messages in error responses (#66) 2023-03-27 14:12:03 -04:00
api_service_accounts.go REST API: provide error messages in error responses (#66) 2023-03-27 14:12:03 -04:00
api_test.go REST API: provide error messages in error responses (#66) 2023-03-27 14:12:03 -04:00
api_vms.go Reactive Scheduling (#67) 2023-03-28 20:51:41 +04:00
api_vms_portforward.go Make port-forward endpoint to wait for the VM (#65) 2023-03-27 23:52:21 +04:00
api_workers.go REST API: provide error messages in error responses (#66) 2023-03-27 14:12:03 -04:00
controller.go Reactive Scheduling (#67) 2023-03-28 20:51:41 +04:00
datadir.go Consolidate controller bootstrap login in `run` command (#38) 2023-03-21 15:36:55 -04:00
errorresponse.go REST API: provide error messages in error responses (#66) 2023-03-27 14:12:03 -04:00
option.go Resources support (#63) 2023-03-27 17:30:54 +04:00
rpc.go Remove UID for now and use machine ID to differentiate workers (#48) 2023-03-23 23:38:54 +04:00