| 52 | | FIXME |
| | 52 | As in previous tutorials, it is always good practice to clean up slivers |
| | 53 | right away so that resources can be released and reused by other experimenters. |
| | 54 | While other tools (such as Flack and the GENI Portal) can also be used to |
| | 55 | clean up, no matter which software was used to establish the sliver in the |
| | 56 | first place, for this example we will demonstrate the clean up procedure |
| | 57 | using Omni. |
| | 58 | |
| | 59 | The command to use is: |
| | 60 | {{{ |
| | 61 | omni.py -a AM_NICKNAME deletesliver SLICENAME |
| | 62 | }}} |
| | 63 | where once again {{{AM_NICKNAME}}} is the aggregate manager nickname and |
| | 64 | {{{SLICENAME}}} is the name of your slice (both found on your worksheet). |
| | 65 | |
| | 66 | A minute or so later, Omni should respond with: |
| | 67 | {{{ |
| | 68 | INFO:omni: Completed deletesliver: |
| | 69 | }}} |
| | 70 | and some details of exactly what was deleted. |
| | 71 | |
| | 72 | Congratulations! You have completed the tutorial. |
| | 73 | |
| | 74 | (If you have extra time, you might want to go back and bring up a different |
| | 75 | sliver and explore some more advanced options. You can reuse the same slice |
| | 76 | name until it expires, so you need only to design a different rspec and |
| | 77 | submit it. For instance, try choosing a different "Sliver Type" and/or |
| | 78 | "Disk Image" from the node information screen in Flack -- these are very |
| | 79 | useful options for advanced GENI users.) |
