9 | | 1. ['''Optional'''] '''emaill [maito:help@geni.net help@geni.net] ''': to let us know you will be using GENI. This will let us help you along the process. We '''strongly recommend''' this, if this is your first time using GENI |
10 | | 1. '''Access to GENI Portal''' If you are planning to use the [https//portal.geni.net GENI Portal] in your class you should figure out how you and your students will get access to GENI. Read the SignMeUp page for more details. |
11 | | 1. '''[wiki:SignMeUp#a2b.CreateaGENIProject Create a Project']''' for your event. Although you might already have a project we recommend that you use a separate project for your class/tutorial. This will make the account management easier. We also '''strongly recommend''' to add an expiration date for your project. The expiration date should not be right after your event in case the students want to experiment for a bit after, but it should be close. We suggest to use ''1 week'' after your event. |
12 | | 1. '''Add''' any other instructors or teaching assistants to the project as Admins. This will allow them to help with the management of the project and with debugging problems with the students. |
13 | | 1. If you haven't already, you and any other instructors or teaching assistants should read through the slides (including the notes) and '''work through the exercise''' and let us know if you have any questions. |
| 9 | 1. [Optional] '''[mailto:help@geni.net Notify us]''' that you will be using GENI. [[BR]]This will let us help you along the process. We '''strongly recommend''' this, if this is your first time using GENI |
| 10 | 1. '''Access to GENI Portal''' [[BR]]If you are planning to use the [https//portal.geni.net GENI Portal] in your class and you have not used it before you should figure out how you and your students will get access to GENI. Read the SignMeUp page for more details. |
| 11 | 1. '''[wiki:SignMeUp#a2b.CreateaGENIProject Create a Project]''' for your event. |
| 12 | * Use a separate project for each class/tutorial you are organizing. This will make the account management easier. |
| 13 | * We also '''strongly recommend''' to add an expiration date for your project. The expiration date should not be right after your event in case the students want to experiment for a bit after, but it should be close. We suggest to use ''1 week'' after your event. |
| 14 | * Add any other instructors or teaching assistants to the project as Admins. This will allow them to help with the management of the project and with debugging problems with the students. |
18 | | === Approximately one week in advance === |
19 | | 1. Invite attendees to '''[http://groups.geni.net/geni/wiki/SignMeUpPortal login to the portal]''' and request an account from the GENI IdP if necessary. This may require some manual intervention, so it's important that people do this early. |
20 | | 1. e-mail attendees information about any other '''pre-work'''. In particular, they will need a machine that allows them to ssh using a private key and has omni installed. |
21 | | 1. Make a worksheet for each attendee |
22 | | 1. If desired, print hardcopies of the exercise and worksheets. |
| 19 | == Approximately one week in advance == |
| 20 | 1. '''Email pre-work to attendees''' |
| 21 | * Gain access to the GENI portal. This may require some manual intervention, so it's important that people do this early. |
| 22 | * Include laptop requirements if attendees are using their personal laptop |
| 23 | * Instructions about downloading/installing the VM if you are using one. |
24 | | === Day of exercise === |
25 | | 1. A few hours before hand, '''bulk add attendees''' to the project (doing this in advance makes the exercise go more quickly) |
26 | | 1. At the exercise, add any stragglers who haven't joined the project by having them clicking the "Request to Join a Project" button on the home page. Then you are one of the project Admins should manually add each of these users to the project. |
27 | | 1. At the exercise, please distribute: |
28 | | a. one worksheet to each attendee (or pair of attendees) doing this exercise. The worksheet does three things: |
29 | | i. it helps attendees identify the data (and not the control plane interface) which they will bring down during the exercise |
30 | | i. it ensures slice names are unique |
31 | | a. a [attachment: hardcopy of the instructions] |
32 | | a. Use the [attachment: slides] to cover the background material needed to do the exercise |
| 25 | == A few days before each exercise == |
| 26 | 1. Prepare any material needed for the exercise (worksheets, printed instructions, etc) If you are using one of the [wiki:GENIEducation/SampleAssignments out-of-the-box assignments] they come with a page for instructors that will include all necessary material. |
| 27 | |
| 28 | == Day of exercise == |
| 29 | 1. '''bulk add attendees''' to the project (doing this in advance makes the exercise go more quickly) |
| 30 | * If this is the first exercise plan to handle students that have not done the pre-work, work with them as they login to the Portal and join the project. |