| 128 | The easiest way to turn the scheduler on and off is to put the scheduler utility script in {{{/usr/local/bin/omf}}}. When you want it to be turned on, make it executable: |
| 129 | |
| 130 | {{{ |
| 131 | chmod a+x /usr/local/bin/omf |
| 132 | }}} |
| 133 | |
| 134 | and when you want it to be turned off, turn off the execute bit: |
| 135 | |
| 136 | {{{ |
| 137 | chmod a-x /usr/local/bin/omf |
| 138 | }}} |
| 139 | |
| 140 | On WITest, as part of the script that runs at the beginning of each reservation, the scheduler script is turned on if it is a group reservation and off if it isn't, and all queues are disabled. |
| 141 | |
| 142 | It is then up to the group "leader" (i.e. tutorial instructor, teaching assistant, etc.) to enable individual queues for the experiment that the group will run. The group "leader" also needs to know to use the full path {{{/usr/bin/omf}}} for "load" commands, which are disabled in the utility script (because it is generally not desirable to load images in a group reservation.) |
| 143 | |
| 144 | |
| 147 | Some important commands follow. |
| 148 | |
| 149 | To enable a queue named e.g. node13-10 so that it starts accepting jobs (user must be listed as a torque operator or manager): |
| 150 | |
| 151 | {{{ |
| 152 | qenable node13-10 |
| 153 | }}} |
| 154 | |
| 155 | To disable a queue named e.g. node13-10 so that it will finish currently queued jobs but not accept new ones (user must be listed as a torque operator or manager): |
| 156 | |
| 157 | {{{ |
| 158 | qdisable node13-10 |
| 159 | }}} |
| 160 | |
| 161 | To see the current torque server configuration: |
| 162 | |
| 163 | {{{ |
| 164 | qmgr -c 'p s' |
| 165 | }}} |
| 166 | |
| 167 | To add a user e.g. ffund01 as a torque manager: |
| 168 | |
| 169 | {{{ |
| 170 | qmgr -c "set server managers += ffund@console.grid.orbit-lab.org" |
| 171 | }}} |
| 172 | |
| 173 | |
| 174 | To kill a job with job ID e.g. 13: |
| 175 | |
| 176 | {{{ |
| 177 | qdel 13 |
| 178 | }}} |
| 179 | |
| 180 | To see currently queued and running jobs (all if you're a torque manager, otherwise your own): |
| 181 | |
| 182 | {{{ |
| 183 | qstat |
| 184 | }}} |
| 185 | |
| 199 | These instructions are for installing the dashboard locally as an unprivileged user, not system-wide. |
| 200 | |
| 201 | First, install RVM and prepare to use it: |
| 202 | |
| 203 | {{{ |
| 204 | command curl -sSL https://rvm.io/mpapis.asc | gpg --import - |
| 205 | curl -L https://get.rvm.io | bash -s stable |
| 206 | source ~/.rvm/scripts/rvm |
| 207 | }}} |
| 208 | |
| 209 | Install ruby 1.9.2 with RVM: |
| 210 | |
| 211 | {{{ |
| 212 | rvm install ruby-1.9.2 |
| 213 | }}} |
| 214 | |
| 215 | Get the [https://github.com/Shopify/dashing dashing] gem: |
| 216 | {{{ |
| 217 | rvm use 1.9.2 |
| 218 | gem install dashing |
| 219 | gem install sqlite3 |
| 220 | gem install execjs --version 1.4.0 # see https://github.com/Shopify/dashing/issues/195 |
| 221 | gem uninstall execjs --version 2.0.2 |
| 222 | }}} |
| 223 | |
| 224 | In {{{~/.rvm/gems/ruby-1.9.2-p330/specifications/dashing-1.3.6.gemspec}}} (or equivalent), change the version for the "execjs" dependency to 1.4.0. |
| 225 | |
| 226 | |