scbi_queue_system 0.0.2 → 0.0.3

Sign up to get free protection for your applications and to get access to all the features.
data/History.txt CHANGED
@@ -1,3 +1,7 @@
1
+ === 0.0.3 2011-07-12
2
+
3
+ Updated documentation
4
+
1
5
  === 0.0.2 2011-07-12
2
6
 
3
7
  Fixed daemon installation
data/README.rdoc CHANGED
@@ -67,9 +67,16 @@ Once installed, you should start the queue manager:
67
67
 
68
68
  queue_manager.rb
69
69
 
70
- By default, it is configured to use localhost with 1 cpu as testing
70
+ By default, it is configured to use localhost with all available cpus.
71
71
 
72
- <b>NOTE:</b> See automatic startup
72
+
73
+ Once the gem is installed you can start the queue manager (it is recommended to setup automatic startup so you don't have to start it manually after each reboot). The queue manager only should be started up in the manager machine, and not on frontends. This script will enable automatic startup on OSX or linux:
74
+
75
+ sudo sqs_install_daemon SQS_USER
76
+
77
+ Be sure to use a SQS_USER different to root.
78
+
79
+
73
80
 
74
81
 
75
82
  === 2.-Cluster:
@@ -86,32 +93,34 @@ Start the queue manager:
86
93
 
87
94
  queue_manager.rb
88
95
 
89
- Share your QUEUED folder with frontend machines and give write-only permission to others (chmod 772)
96
+ <b>If you are using a front-end machine<b/>: Share your QUEUED folder with frontend machines and give write-only permission to others (chmod 772)
97
+
98
+ Enable automatic startup
99
+
100
+ Once the gem is installed you can start the queue manager (it is recommended to setup automatic startup so you don't have to start it manually after each reboot). The queue manager only should be started up in the manager machine, and not on frontends. This script will enable automatic startup on OSX or linux:
101
+
102
+ sudo sqs_install_daemon SQS_USER
103
+
104
+ Be sure to use a SQS_USER different to root.
105
+
90
106
 
91
107
  ==== -On the frontends machines:
92
108
 
93
109
  Later on, you should install the sqsub command on your cluster's frontend machines (the one/ones from where you are going to submit jobs).
94
110
 
95
111
  gem install scbi_queue_system
112
+
113
+ After gem installation you need to define the SQS_QUEUED_PATH environment variable and point it to the shared QUEUED folder of your manager machine.
114
+
96
115
 
97
116
  === 3.- Environment variables:
98
117
 
99
- * SQS_BASE_PATH : sets the location of sqs directoies.
118
+ * SQS_BASE_PATH : sets the location of sqs directories.
100
119
 
101
120
  * SQS_QUEUED_PATH : sets the location of QUEUED directory. This location must be shared and with write only permissions for all SQS clients (those that need to use sqsub).
102
121
 
103
122
  * SQS_LOG_FILE: sets the location of log files.
104
123
 
105
- === 4.- Automatic startup
106
-
107
- Once the gem is installed you can start the queue manager (it is recommended to setup automatic startup so you don't have to start it manually after each reboot). The queue manager only should be started up in the manager machine, and not on frontends.
108
-
109
- ==== -On Linux
110
-
111
-
112
- ==== -On Mac OS X
113
-
114
-
115
124
  == LICENSE:
116
125
 
117
126
  (The MIT License)
@@ -53,5 +53,5 @@ require 'done_job_list'
53
53
 
54
54
 
55
55
  module ScbiQueueSystem
56
- VERSION = '0.0.2'
56
+ VERSION = '0.0.3'
57
57
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: scbi_queue_system
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.0.2
5
+ version: 0.0.3
6
6
  platform: ruby
7
7
  authors:
8
8
  - Dario Guerrero