| | 1 | == How to use Omni during a Clearinghouse maintenance window == |
| | 2 | |
| | 3 | '''Problem''' |
| | 4 | Omni will download either you user or slice credential from the clearinghouse during each call you make to an aggregate. If the clearinghouse is down for maintenance, then you can't do this. |
| | 5 | |
| | 6 | '''Solution''' |
| | 7 | If you download your user credential and slice credentials before the outage you can continue to act on and reserve resources at aggregates (although you can't make calls to the clearinghouse). |
| | 8 | |
| | 9 | To download your user credential into a file: |
| | 10 | {{{ |
| | 11 | omni.py getusercred -o |
| | 12 | }}} |
| | 13 | |
| | 14 | To download slice credentials you might use during the window: |
| | 15 | {{{ |
| | 16 | omni.py getslicecred MySlice -o |
| | 17 | }}} |
| | 18 | |
| | 19 | In both cases, the output will tell you the name of a file where the credential was stored. |
| | 20 | |
| | 21 | To use the credentials use the `--usercredfile` and `--slicecredfile` options with Omni. |
| | 22 | {{{ |
| | 23 | omni.py -a ig-gpo sliverstatus myslice --slicecredfile myslice-cred.xml |
| | 24 | omni.py -a ig-gpo listresources --usercredfile sedwards-portal-usercred.xml |
| | 25 | }}} |
