Changes between Version 6 and Version 7 of GeniTutorialHints


Ignore:
Timestamp:
10/11/11 12:42:01 (8 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTutorialHints

    v6 v7  
    1212 3. ''Client software on attendee machines.''  If you need special client side software (e.g. GENI experiment control tools) installed on the attendee machines, it might be best to pre-install this software in a virtual machine and distribute this virtual machine for the attendees to run on their computers.  We've very successfully used  [https://www.virtualbox.org/ VirtualBox] for this purpose: All client-side software needed by the attendees is installed in a !VirtualBox virtual machine running an OS such as Ubuntu.  Attendees are asked to come with !VirtualBox installed on their computers.  They can install the virtual machine with tutorial software at the tutorial or ahead of time.  We strongly encourage making the virtual machine image available to attendees ahead of time so valuable class time isn't spent installing the virtual machine image.  Additionally, these virtual machine images tend to be large (many GBs) and so downloading and installing them during the tutorial might stress the network in the classroom.
    1313 4. ''Experimenter credentials.''  Setting up experimenter credentials, creating and installing ssh keys, etc. can be very time consuming.  So, unless an objective of your tutorial is to work through this process, we recommend creating credentials and installing the necessary keys ahead of time.  Some tutorials have created multiple user accounts on the virtual machine and have installed the necessary certificates and keys for each account.  Others have installed multiple sets of credentials in one virtual machine user account and have told each attendees which set of credentials they should be using.
    14  5. ''Dry runs''.  Dry run the tutorial.  If at all possible, do the dry-run with 20+ people in the room so you can identify  resource bottlenecks and concurrency issues.
     14 5. ''Dry runs''.  Dry run the tutorial.  If at all possible, do the dry-run with 20 people (or whatever your expected class size may be) doing the exercises simultaneously so you can identify  resource bottlenecks and concurrency issues.
    1515 5. ''Post tutorial material online''.  Make your slides and other material (including experimenter software) available online.
    1616 5. ''Hard copies of presentation material''.  Make a sufficient number of hardcopies of the presentation material available for distribution to all attendees.  Hardcopies are especially helpful for attendees falling behind as they can try to catch up even if the instructions they need are no longer on the projector screen in front of the classroom.