| 1 | If you are running a: |
| 2 | * class using GENI |
| 3 | * a GENI tutorial |
| 4 | * running a potential disruptive experiment (bandwidth intensive, uses unique GENI resources, etc) |
| 5 | you should notify the Resource providers and the [http://gmoc.grnoc.iu.edu/GENI Meta Operation Center (GMOC)] so that you get better support. This will ensure that: |
| 6 | * resources are available for your event |
| 7 | * your event does not conflict with any maintanance, outage, other GENI Event |
| 8 | |
| 9 | In order to do that you should send an email to GMOC describing the resources you need. What you need for that email is: |
| 10 | * '''type of event:''' |
| 11 | class, tutorial, disruptive experiment |
| 12 | * '''list of AMs you are going to use:''' |
| 13 | be as specific as you can and include number of resources (e.g. 20 VMs from GPO EG rack) |
| 14 | * '''list of tools:''' |
| 15 | list any GENI tools you migt be using, e.g. portal, flack, gemini, gimi |
| 16 | * '''scheduled time(s):''' |
| 17 | if this is not a one-time event include all the times you know about. If you are running a class and you have not finalized all the dates yet, its ok to update your ticket as you get more information |
| 18 | |
| 19 | This is a template email |
| 20 | {{{ |
| 21 | To: gmoc@grnoc.iu.edu |
| 22 | Subject: <GENI Event Type> |
| 23 | |
| 24 | <Brief summary> |
| 25 | |
| 26 | Affected AMs: <list of AMs that you are going to use> |
| 27 | Used tools : <list of tools that> |
| 28 | |
| 29 | Scheduled time(s) |
| 30 | |
| 31 | We would like the notification to show up as a GMOC ticket and to be |
| 32 | listed on the GMOC calendar. |
| 33 | Please also verify that there aren't any planned outages in the |
| 34 | underlying core infrastructure that would affect this <GENI Event Type> |
| 35 | |
| 36 | Thanks, |
| 37 | <Your Name> |
| 38 | }}} |