blob: e2ba06d867726e0c1f7eb192bc264de8df07174b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
# expect call back:
``` ruby
expect /---more---/ do
@output.pop
cmd "\n"
```
I don't really need it myself, since I don't have platforms where it would be needed
# thread number
* think about algo
* if job ended later than now-iteration have rand(node.size) == 0 to add thread
* if now is less than job_ended+iteration same chance to remove thread?
* should we try to avoid max threads from being hit? (like maybe non-success thread is pulling average?)
# restful API (puma+sinatra):
* ask to reload node list
* move node to head of queue
# config
* save keys as strings, load as symbols?
# other
should it offer cli mass config-pusher? (I think not, I have ideas for such
program and I'm not sure if synergies are high enough for shared code without
making both bit awkward)
use sidekiq? Any benefits?
# docs, testing
* yard docs
* rspec tests
# multiple input methods
* ssh, with telnet fallback
|
