Initial Implementation

[colhom]

This is a working implementation of the discussed pod scheduler/unscheduler, which has been named rcscheduler

I've concocted a routine/collector design paradigm which I think will work well with our desired design pattern.

routines are blocks of logic which have the a lifecycle:

• initialize: set up resources
• poll for state: this block is run in a loop, which has two parameters
  1. poll interval: how many seconds to sleep between each poll
  2. poll count: how many polls to do before cleaning up and re-initializing ( <1 to delimit)
• cleanup restore state expected by initialize

As routines progress through the lifecycle and observe the api, they emit events which describe the latest known state.

collectors are aggregators which collect events from routines over time and consolidate the current state.

The only assumption made at the architecture level is that collectors
a) Consume events from some number of routines
b) Consolidate that state into a single http handler function

[colhom]

@philips ping

[philips]

lgtm.