robot-controller 2.0.beta2 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +15 -13
  3. data/VERSION +1 -1
  4. data/bin/controller +5 -1
  5. metadata +1 -1
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 3446fffd9b5e4fc0d97072f0e9f491ec1252ca52
4
- data.tar.gz: 5e85c22b3c75a99a3b1fc3b68e712310fbb85655
3
+ metadata.gz: b2f749801d61882786e5c4d20fed0f0d25e49330
4
+ data.tar.gz: 6d33a112ceecfc0e489d6a62ac1ede016fef30ce
5
5
  SHA512:
6
- metadata.gz: 911a499b4add966727b3e97e918793f1009b236d2b79b2a2452612257088eee37eabba456a63726c41f16b5d450cb8ce1a95caba6d3d89a2aa3a0818def672c9
7
- data.tar.gz: 178a30e94966732b047c89f6cc3cc60961cdc856c094ff45e4567f50f98dd0cbb4490b975929f23023c76a89113710562e1f406f0fac0d99bfe16099bdd23ae9
6
+ metadata.gz: a13063c8cf25fb05dcb0dd9fab4c0060cd9b2f25c2ae5702044089f98369f112b82f40843cdc61b198a5181fa38e2f8a3131354c752ceac48c23da1c862515f7
7
+ data.tar.gz: f15b215c9e5a88645ca4ca7ce351fa589f11b09ab41c6d283d91f180ddc62d299f411d777f8bc0855cf5521612149c6d616a8de5bca0850163630ca81c8eed02
data/README.md CHANGED
@@ -22,7 +22,7 @@ Then to use the controller to boot the robots:
22
22
  % bundle exec controller boot
23
23
 
24
24
  If you want to *override* the bluepill configuration but still use the
25
- controller, then add:
25
+ controller (though NOT recommended), then add:
26
26
 
27
27
  config/bluepill.rb
28
28
 
@@ -37,7 +37,7 @@ controller, then add:
37
37
  % controller boot # start bluepilld and jobs
38
38
  % controller status # check on status of jobs
39
39
  % controller verify # verify robots are running as configured
40
- % controller log 1_dor_accessionWF_descriptive-metadata # view log for worker
40
+ % controller log robot01_01_dor_accessionWF_descriptive-metadata # view log for worker
41
41
  % controller stop # stop jobs
42
42
  % controller quit # stop bluepilld
43
43
 
@@ -50,11 +50,13 @@ controller, then add:
50
50
 
51
51
  * `v1.0.0`: Initial version
52
52
  * `v1.0.1`: Add 'rake' as dependency
53
+ * `v2.0.0`: Added 'verify' command
53
54
 
54
55
  ### `verify` command
55
56
 
56
57
  You can run the `verify` command with an optional `--verbose` to print out
57
58
  details about whether the robots processes are running as configured.
59
+ To install create a `config/robots.yml` that lists all of the robots in your suite.
58
60
 
59
61
  When no errors are detected, the output looks like so:
60
62
 
@@ -62,22 +64,22 @@ When no errors are detected, the output looks like so:
62
64
  OK
63
65
 
64
66
  % bundle exec controller verify --verbose
65
- OK robot1 is up
66
- OK robot2 is up
67
- OK robot3 is not enabled
68
- OK robot4 is not enabled
67
+ OK robot1 is up (1 running)
68
+ OK robot2 is up (1 running)
69
+ OK robot3 is not enabled (0 running)
70
+ OK robot4 is not enabled (0 running)
69
71
 
70
- If `robot2` were down and `robot3` were up, the output would look like so:
72
+ If `robot2` were down and `robot3` were up, the output would look something like:
71
73
 
72
74
  % bundle exec controller verify
73
- ERROR robot2 is down (0 out of 3 processes running)
74
- ERROR robot3 is not enabled but 1 process is running
75
+ ERROR robot2 is down (1 of 3 running)
76
+ ERROR robot3 is not enabled (but 1 running)
75
77
 
76
78
  % bundle exec controller verify --verbose
77
- OK robot1 is up
78
- ERROR robot2 is down (0 out of 3 processes running)
79
- ERROR robot3 is not enabled but 1 process is running
80
- OK robot4 is not enabled
79
+ OK robot1 is up (1 running)
80
+ ERROR robot2 is down (1 of 3 running)
81
+ ERROR robot3 is not enabled (but 1 running)
82
+ OK robot4 is not enabled (0 running)
81
83
 
82
84
  The various states are determined as follows:
83
85
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 2.0.beta2
1
+ 2.0.0
data/bin/controller CHANGED
@@ -90,7 +90,11 @@ when 'verify'
90
90
  when :up
91
91
  puts "OK: #{robot} is up (#{status[:running]} running)" if verbose
92
92
  when :not_enabled
93
- puts "OK: #{robot} is not enabled (#{status[:running]} running)" if verbose
93
+ if status[:running] == 0
94
+ puts "OK: #{robot} is not enabled (0 running)" if verbose
95
+ else
96
+ puts "ERROR: #{robot} is not enabled (but #{status[:running]} running)"
97
+ end
94
98
  when :down
95
99
  ok = false
96
100
  puts "ERROR: #{robot} is down (#{status[:running]} of #{running[robot]} running)"
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: robot-controller
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.beta2
4
+ version: 2.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Darren Hardy