| 163 | == 2.5 Wait for resources to be ready == |
| 164 | |
| 165 | You can tell whether your nodes are ''ready'' by using a script built on `omni` called `readyToLogin`. |
| 166 | |
| 167 | {{{ |
| 168 | #!html |
| 169 | <ol type='a'> |
| 170 | <li> |
| 171 | Please use the command: |
| 172 | <pre> |
| 173 | readyToLogin slicename --useSliceAggregates |
| 174 | <pre> |
| 175 | where <tt>slicename</tt> is your slice name |
| 176 | </li> |
| 177 | <li>If it reports that the sliver is not yet ready (for example, it might say that the status is "changing"), then wait a minute |
| 178 | or two and try again. Once everything is complete, <tt>readyToLogin</tt> |
| 179 | will give output that should look something like this: |
| 180 | <pre> |
| 181 | ... |
| 182 | rschr's geni_status is: ready (am_status:ready) |
| 183 | User example logs in to rschr using: |
| 184 | ssh -p 32768 -i /Users/example/.ssh/geni_key_portal example@pc1.utah.geniracks.net |
| 185 | User example logs in to collar using: |
| 186 | ssh -p 32769 -i /Users/example/.ssh/geni_key_portal example@pc1.utah.geniracks.net |
| 187 | ... |
| 188 | </pre> |
| 189 | |
| 190 | </li> |
| 191 | </ol> |
| 192 | }}} |
| 193 | |