1. Sponsored by the National Science Foundation Getting Started With Your Own Experiment

2. Sponsored by the National Science Foundation Intermediate Topics Solutions to Common Problems Getting Help Advanced Topics

3. Sponsored by the National Science Foundation 3 GEC20– June 21, 2014 Reproducible Experiments Two approaches: –Use existing images with install scripts http://groups.geni.net/geni/wiki/HowTo/WriteInstallScript –Use custom images or snapshots Image creation –ExoGENI provides a sandbox for image creation Snapshot images –InstaGENI provides standard images which are easy to snapshot Snapshot image: http://groups.geni.net/geni/wiki/HowTo/ManageCustomImagesIns taGENI … or combine the two approaches

4. Sponsored by the National Science Foundation 4 GEC20– June 21, 2014 Inter-aggregate Connectivity Different experiments have different needs, chose based on your experiment!

5. Sponsored by the National Science Foundation 5 GEC20– June 21, 2014 Inter-aggregate Links Stitching –Creates an inter-domain VLAN –Stitcher: Distributed with gcf/omni –Flukes: ExoGENI-only (not via GENI AM API) Shared VLANs –Some pre-configured inter-domain shared VLANs are available –Some are OpenFlow-enabled GRE tunnels over control interface –Use Flack to connect IG nodes via a GRE tunnel –Manually configure GRE tunnels between EG nodes

6. Sponsored by the National Science Foundation 6 GEC20– June 21, 2014 Rack Differences ExoGENI, InstaGENI, ProtoGENI are they different and how do I choose? The important thing is your experiment, so you should always start by designing your experiment and don’t worry about the aggregate. ExoGENI, InstaGENI: GENI racks developed by different teams ProtoGENI: Pre-existing testbeds that are GENI enabled, InstaGENI is based on ProtoGENI software

7. Sponsored by the National Science Foundation 7 GEC20– June 21, 2014 Designing your experiment: Things to consider Do I need access to bare metal hosts? What are my networking needs? What tools do I want to use? What platform am I familiar with?

8. Sponsored by the National Science Foundation 8 GEC20– June 21, 2014 Omni Commands & Documentation Find aggregate nicknames: $ omni nicknames Find all [available] resources at aggregates (aka advertisement RSpec): $ omni –a … listresources [--available] [-o] Find all resources in slice (aka manifest RSpec): $ omni –a … listresources SLICENAME [-o] Find status of resources in slice: $ omni –a … sliverstatus SLICENAME Omni documentation How to configure omni: http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/Automatic Omni workflow and command documentation: http://trac.gpolab.bbn.com/gcf/wiki/OmniOverview#Omniworkflow How to use omni: http://groups.geni.net/geni/wiki/HowToUseOmni

9. Sponsored by the National Science Foundation 9 GEC20– June 21, 2014 Acting against known aggregates Query for existing slice, members, slivers … $ omni listslices $ omni listslicemembers SLICENAME $ omni listslivers SLICENAME Omni/Portal report sliver creation/deletion to Clearinghouse. --useSliceAggregates queries against aggregates known to have resources in your slice $ readyToLogin SLICENAME --useSliceAggregates $ omni deletesliver SLICENAME --useSliceAggregates http://trac.gpolab.bbn.com/gcf/wiki/HowTo/UseCHAPIInOmni Hands-On Clearinghouse info is only advisory! Query aggregates for authoritative info

10. Sponsored by the National Science Foundation 10 GEC20– June 21, 2014 Add a member to existing slivers 1) Add member to slice $ omni addslicemember SLICENAME USERNAME 2) Add slice member’s accounts to existing slivers $ omni -V 3 poa SLICE geni_update_users --useSliceAggregates –-useSliceMembers Alternatively, the Linux version has a script to do the above two steps $ addMemberToSliceAndSlivers myslice username http://trac.gpolab.bbn.com/gcf/wiki/HowTo/UseCHAPIInOmni Only works on InstaGENI/ProtoGENI Demo

11. Sponsored by the National Science Foundation Advanced Topics Solutions to Common Problems Getting Help Solutions to Common Problems

12. Sponsored by the National Science Foundation 12 GEC20– June 21, 2014 Common Problems Problem: Slice did not come up (“not green”) Possible causes: –Did not wait long enough –Problem with RSpec Debug strategy: –Check slice/sliver status –Use rspeclint on your rspecs http://www.protogeni.net/wiki/RSpecDebugging

13. Sponsored by the National Science Foundation 13 GEC20– June 21, 2014 Three ways to get SliverStatus Jacks/jFed –“green” is good Omni –Use readyToLogin Portal –On slice page, use “Ready?” button Demo

14. Sponsored by the National Science Foundation 14 GEC20– June 21, 2014 Common Problems Problem: Resources disappeared Possible causes: –Slice expired –Resources (aka slivers) expired Debug strategy: –Check slice/sliver status –Reserve resources again if expired  –Don’t rely on nodes for storage Edit scripts locally and scp to your nodes Copy data off machines

15. Sponsored by the National Science Foundation 15 GEC20– June 21, 2014 Expiration and renewal slice expiration time ≤ project expiration time each resource expiration time ≤ slice expiration time each resource expiration time ≤ aggregate’s max expiration project slice resource (optional) project expiration time slice expiration time resource expiration time now In general, to extend the lifetime of your resource reservation, you must renew the slice and all resources resource

16. Sponsored by the National Science Foundation 16 GEC20– June 21, 2014 Extend slice/resour ce expirations Slice and Sliver Expiration $ omni renewslice 01-31-14 # renew each sliver individually $ omni renewsliver –a gpo-ig myslice 01-31-14 $ omni renewsliver –a renci-eg myslice 01-31-14 $ omni renewsliver –a missouri-ig myslice 01-31-14 # OR renew all known slivers for “as long as possible” $ omni -V 3 renew myslice 01-31-14 -–useSliceAggregates --alap Hands-On

17. Sponsored by the National Science Foundation 17 GEC20– June 21, 2014 Common Problems Problem: Can’t login to a node Possible causes: –Slice/sliver expired –Wrong username –Public key isn’t loaded, Private key is wrong or non-existing –Private key has wrong permissions (it should have 0600) –Technical issue with node Debug strategy: 1.Check the status of the sliver 2.Try having a collaborator login Look for loaded keys sudo cat ~other_user_path/.ssh/authorized_keys 3.Ask them to use ‘-v’ option ssh –v foo@bar.example.net

18. Sponsored by the National Science Foundation 18 GEC20– June 21, 2014 Common Problems Problem: Can’t access AMs Possible causes: –Firewall issues –AM is down Debug strategy: –Check the GMOC calendars for planned/unplanned outages http://globalnoc.iu.edu/gmoc/index/support/gmoc-operations- calendars.html –Try to telnet to the port: e.g. telnet www.emulab.net 12369 Complete list of ports: http://groups.geni.net/geni/wiki/KnownGENIPortshttp://groups.geni.net/geni/wiki/KnownGENIPorts –Frequent issues on Campus Guest WiFi networks

19. Sponsored by the National Science Foundation 19 GEC20– June 21, 2014 Check Calendar / Notify GMOC GMOC: GENI Meta-operation Center Keeps track of outages Notification system for resource reservation http://groups.geni.net/geni/wiki/HowTo/PreReserveGENIResources GMOC Google Calendar keeps track of reservations/outages

20. Sponsored by the National Science Foundation 20 GEC20– June 21, 2014 Common Problems Problem: Omni is not working Possible causes: –Computer is not connected to the Internet/behind firewall –$PATH/$PYTHONPATH is not correct Python error –omni is not configured Debug strategy: –Verify omni working: Omni installed: omni --version Omni configured to speak to the clearinghouse: omni getusercred -o Omni can speak to an aggregate: omni getversion -a ig-gpo –Check $PATH and $PYTHONPATH variables: echo $PATH echo $PYTHONPATH –Verify connectivity to: The Internet: ping www.google.com To the CH: telnet ch.geni.net 8443 To the AMs: telnet bbn-hn.exogeni.net 11443 telnet instageni.gpolab.bbn.com 12369

21. Sponsored by the National Science Foundation 21 GEC20– June 21, 2014 Clean up now! Try this now: $ omni deletesliver SLICENAME --useSliceAggregates slice project aggregate experimenter resource

22. Sponsored by the National Science Foundation Advanced Topics Solutions to Common Problems Getting Help Getting Help

23. Sponsored by the National Science Foundation 23 GEC20– June 21, 2014 Answer is help@geni.net Have a question? Sarah Edwards Niky Riga Vic Thomas which is an email list which only goes to members of the GPO including… (However, the archive of the list is public)

24. Sponsored by the National Science Foundation 24 GEC20– June 21, 2014 Ways to Get Help Sign Up for : geni-users@googlegroups.com Use #geni IRC chatroom Go over HowTo pages http://groups.geni.net/geni/wiki/GENIExperimenter/GetHelp

25. Sponsored by the National Science Foundation 25 GEC20– June 21, 2014 General debug advice 1. Gather as much information as you can –Be specific about what is not working Step-by-step run through usually helps –Include what you see (screenshots, omni output errors) –Always include: type of account you are using (eg portal) the tool you are using (eg Flack, omni, portal) your slice name or URN aggregates you are using a detailed description of what's wrong including any error messages 2.Contact geni-users@googlegroups.com for help 3.Register for resource mailing lists

26. Sponsored by the National Science Foundation 26 GEC20– June 21, 2014 Finding other resources GENI wiki –Pages for Instructors and Experimenters http://groups.geni.net/geni/wiki

27. Sponsored by the National Science Foundation 27 GEC20– June 21, 2014 “How To” pages Listed under the “Experimenters” section Each “How To” is a short descriptions of how to do various tasks New entries being added all the time

28. Sponsored by the National Science Foundation 28 GEC20– June 21, 2014 Ways to Learn More Sign up for announce@geni.net to be notified about: Train-the-TA at the start of each semester (online-only) GENI Summer/Winter Camps Sign up at: http://lists.geni.net/mailman/listinfo/geni-announce

29. Sponsored by the National Science Foundation 29 GEC20– June 21, 2014 http://tinyurl.com/GEC19-Feedback Thank you for attending! Please fill out the survey

30. Sponsored by the National Science Foundation Working With Collaborators

31. Sponsored by the National Science Foundation 31 GEC20– June 21, 2014 Projects Projects organize research in GENI Projects contain both people and their experiments A project is led by a single responsible individual: the project lead Project Lead Members Slice

32. Sponsored by the National Science Foundation 32 GEC20– June 21, 2014 Project Membership example Projects have 1 Lead and any number of Admins, Members, and Auditors http://groups.geni.net/geni/wiki/GENIConcepts#Project Typical Class Expiration Typical Research Project

33. Sponsored by the National Science Foundation 33 GEC20– June 21, 2014 Populating a Project 1.Member-initiated Each experimenter asks to join a project, approval needed Typical for Research projects 1.Admin-initiated Project Lead/Admin bulk-adds experimenters Typical for Classrooms or Tutorials

34. Sponsored by the National Science Foundation 34 GEC20– June 21, 2014 Project and Slice Roles Create project Modify project & manage membership Create sliceView project Project Lead ✔✔✔✔ Admin ✔✔✔ Member ✔✔ Auditor ✔ Manage slice membership Act on sliceView sliceAccount/ keys loaded on slice Slice Lead ✔✔✔✔ Admin ✔✔✔✔ Member ✔✔✔ Auditor ✔✔ http://groups.geni.net/geni/wiki/ProjectSlicesRoles

35. Sponsored by the National Science Foundation 35 GEC20– June 21, 2014 Working with multiple members in a slice Research Asst Slice Lead Post-Doc Slice Member Professor Slice Admin Members of all slices in a project: Project Leads (Professor) Project Admins (TAs, Graders) Other can be added manually http://groups.geni.net/geni/wiki/GENIConcepts#Slice

36. Sponsored by the National Science Foundation 36 GEC20– June 21, 2014 Slice Access Being a member of a slice means you can act on a slice: –Add resources –Check status –Delete resources –Renew resources With any tool!

37. Sponsored by the National Science Foundation 37 GEC20– June 21, 2014 Slice Access: Logging in to resources Slice membership does not guarantee ability to login to resources! To ensure access in collaborator’s resources: Option 1: Make resource reservation from Portal fix the membership of the slice Use the add resource button in the portal Option 2: Make resource reservation using omni fix the membership of the slice Call createsliver Option 3: Ensure common public key is loaded distribute common public key to collaborators ask collaborators to upload it in their profile use corresponding private key to login