adding initial not-yet-implemented outline of ec2 scheduler module
added some initial basic tests for the ec2 scheduler (optional)
added questions for stuff needed by ec2
still mostly unimplemented, but a little testable now
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/ec2
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/ec2
fixed scheduler_cmd_line test
fixed scheduler_cmd_line test again
fixed scheduler_cmd_line test again2
determine_queue() properly implemented, other methods still non-functional
merge from develop
repull from develop
pill from develop
Merge branch 'develop' of /software/vertres/git/origin/vr-pipe into feature/ec2
we now require Proc::Daemon
clear out the farm_server if we can not continue sub management due to the redis server failing to start
use Parallel::ForkManager instead of AnyEvent::ForkManager for the process_queue, now that process_queue is called by daemon with no AnyEvent stuff
avoid use of VRPipe::Interface::BackEnd to speed up script start-up, letting status/start/stop respond quickly
improved log message when management can not start due to farm server still being alive
avoid meaningless errors from the server during testing