Open mcoffin opened 7 years ago
This could be a little problematic given how the scheduler state is currently managed via a StateT
monad transformer in the scheduler. With this approach, the scheduler will have to initiate the API, which isn't the end of the world, but certainly isn't ideal. It would be nicer if the API were initiated as a separate component, and the StateT SchedulerState
monad transformation were moved to Main
.
Likely, a good solution to this problem ^ will be to just have the Scheduler store it's state in an STRef at the end of each loop. That, or we could move the state management in to Main, but that's not super ideal.
User should be able to query a RESTful api to get the following information about task statuses.
/slaves
GET
/slaves/:id
GET