| 358 | == 4 Wait for resources to be ready == |
| 359 | |
| 360 | You can tell whether your nodes are ''ready'' by using a script built on `omni` called `readyToLogin`. |
| 361 | |
| 362 | {{{ |
| 363 | #!html |
| 364 | <ol type='a'> |
| 365 | <li> |
| 366 | Please use the command: |
| 367 | <pre> |
| 368 | readyToLogin -a AM_NICKNAME SLICENAME |
| 369 | <pre> |
| 370 | where (as before) <tt>AM_NICKNAME</tt> and <tt>SLICENAME</tt> are your aggregate |
| 371 | manager nickname and your slice name (both found on your worksheet). |
| 372 | </li> |
| 373 | <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 |
| 374 | or two and try again. Once everything is complete, <tt>readyToLogin</tt> |
| 375 | will give output that should look something like this: |
| 376 | <pre> |
| 377 | ... |
| 378 | nodea's geni_status is: ready |
| 379 | User example logs in to nodea using: |
| 380 | ssh -p 34106 -i /Users/example/.ssh/geni_key_portal example@pc2.instageni.illinois.edu |
| 381 | |
| 382 | switch's geni_status is: ready |
| 383 | User example logs in to switch using: |
| 384 | ssh -p 34110 -i /Users/example/.ssh/geni_key_portal example@pc2.instageni.illinois.edu |
| 385 | |
| 386 | nodeb's geni_status is: ready |
| 387 | User example logs in to nodeb using: |
| 388 | ssh -p 34107 -i /Users/example/.ssh/geni_key_portal example@pc2.instageni.illinois.edu |
| 389 | |
| 390 | nodec's geni_status is: ready |
| 391 | User example logs in to nodec using: |
| 392 | ssh -p 34108 -i /Users/example/.ssh/geni_key_portal example@pc2.instageni.illinois.edu |
| 393 | |
| 394 | noded's geni_status is: ready |
| 395 | User example logs in to noded using: |
| 396 | ssh -p 34109 -i /Users/example/.ssh/geni_key_portal example@pc2.instageni.illinois.edu |
| 397 | ... |
| 398 | </pre> |
| 399 | |
| 400 | </li> |
| 401 | </ol> |
| 402 | }}} |
| 403 | |