Getting Started W ith Your Own Experiment

1. Getting Started With Your Own Experiment Sarah Edwards, GENI Project Office

2. GENI Accounts and Projects GENI Accounts and ProjectsAdvice and Intermediate TopicsGetting Help / Learning More

3. Access to GENI Leverage InCommonfor single sign-on authentication Experimenters from 342 educational and research institutions have InCommon accounts • For many experimenters: • no new passwords • familiar login screens GENI Project Office runs a federated IdP to provide accounts for non-federated organizations.

4. Projects Project Projects organize research in GENI Projects contain both peopleand their experiments A project is led by a single responsible individual: the projectlead Lead Members Slice

5. Project Membership example Projects have 1 Lead and any number of Admins, Members, and Auditors Expiration Typical Class Typical Research Project http://groups.geni.net/geni/wiki/GENIConcepts#Project

6. Populating a Project • Member-initiated Each experimenter asks to join a project, approval needed • Typical for Research projects • Admin-initiated Project Lead/Admin bulk-adds experimenters • Typical for Classrooms or Tutorials

7. Slice Membership example • Slices have: • 1 Lead (person who created the slice) • any number of Admins, Members, and Auditors • Project Lead/Admins added as slice Admins Research Asst Research Asst Professor Professor Post-Doc Slice Member Slice Lead Slice Lead Slice Admin Slice Admin http://groups.geni.net/geni/wiki/GENIConcepts#Slice

8. 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!

9. GENI Accounts and ProjectsIntermediate TopicsGetting Help / Learning More Advice and Intermediate Topics

10. Designing your experiment • Decide on compute resources (raw PCs, VMs, memory, etc) • Decide on networking needs • Start small • Debug your experiment is small, isolated topologies that you control all pieces

11. GENI Compute Resources ExoGENI, InstaGENI, ProtoGENI are they different and how do I choose? ExoGENI, InstaGENI: GENI racks developed by different teams ProtoGENI: Pre-existing testbeds that are GENI enabled, InstaGENI is based on ProtoGENI software The important thing is your experiment, so you should always start by designing your experiment and don’t worry about the aggregate.

12. Inter-aggregate Links • Stitching • Creates an inter-domain VLAN • Stitcher: Distributed with gcf/omni • Flukes: ExoGENI-only (not via GENI AM API) • GRE tunnels over control interface • Use Flack to connect IG nodes via a GRE tunnel • Manually configure GRE tunnels between EG nodes • Shared VLANs • Some pre-configured inter-domain shared VLANs are available • Some are OpenFlow-enabled

13. Running your experiment • Automate your experiment • Make it easy to bring up and run it • Save the Rspec • Backup your software • Resources can expire • Nodes may fail • Aggregates might go on maintanance

14. 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/ManageCustomImagesInstaGENI • … or combine the two approaches

15. Disruptive experiments Experiments: • with high resource constraints • e.g. high bandwidth, many compute resources • OpenFlow experiments with “risky” topologies • e.g with loops traversing national backbones • requiring performance isolation Notify resource owners and the community

16. GMOC GMOC: GENI Meta-operation Center • Keeps track of outages • Notification system for resource reservation GMOC Google Calendar keeps track of reservations/outages http://groups.geni.net/geni/wiki/HowTo/PreReserveGENIResources

17. GENI Accounts and ProjectsAdvice and Intermediate TopicsGetting Help / Learning More Getting Help / Learning More

18. Have a question? Answer is help@geni.net which is an email list which only goes to members of the GPO including… Vic Thomas Niky Riga Sarah Edwards (However, the archive of the list is public)

19. Ways to Get Help • Sign Up for : geni-users@googlegroups.com • Use #geniIRC chatroom • Go over HowTo pages http://groups.geni.net/geni/wiki/GENIExperimenter/GetHelp

20. General debug advice • 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 • Contact geni-users@googlegroups.comfor help • Register for resource mailing lists

21. Finding other resources • GENI wiki • Pages for Instructors and Experimenters http://groups.geni.net/geni/wiki

22. Popular Samples • Tutorials: • Lab Zero • Basic GENI understanding, ensures students setup their environment • http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/GettingStarted_PartI • Intro To OpenFlow • Basic OpenFlow introductory tutorial, students learn how to setup OVS and write simple controllers • http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/OpenFlowOVS • Assignments: • IPv4 Routing • Students understand IPv4 forwarding and how to configure static routes • http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/IPRouting/Procedure • TCP Network Awareness • Students explore different TCP flavors and TCP parameters • http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/TcpAssignment http://groups.geni.net/geni/wiki/GENIExperimenter/ExampleExperiments http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments

23. “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

24. Ways to Learn More Sign up for announce@geni.net to be notified about: GENI Engineering Conferences, 3x/year, open to all: Planning & discussion for experimenters, software, infrastructure Tutorials and workshops Travel grants to US academics for participant diversity GEC19 March 17-19, 2014, Georgia Tech, Atlanta GENI Summer Camp Train-the-TA at the start of each semester (online-only) Sign up at: http://lists.geni.net/mailman/listinfo/geni-announce

25. http://tinyurl.com/GENI-IC2E14 Thank you for attending! Please fill out the survey

26. Backup

27. Solutions to Common Problems

28. 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

29. 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 resource (optional) project expiration time resource resource expiration time slice expiration time now In general, to extend the lifetime of your resource reservation, you must renew the slice and allresources

30. Slice and Sliver Expiration $ omnirenewslice 01-31-14 $ omnirenewsliver –a gpo-igmyslice 01-31-14 $ omnirenewsliver –a renci-egmyslice 01-31-14 $ omnirenewsliver –a missouri-igmyslice 01-31-14 Extend slice/resource expirations

31. Common Problems Problem: Can’t login to a node Possible causes: • Wrong username • Public key isn’t loaded/ Private key is wrong or non-existing • Private key has wrong permissions (it should have 0600) • Slice/sliver expired • Technical issue with node Debug strategy: • Ask another member of the slice to login to the node • If successful look for your account • cd ..; ls • Look for loaded keys • sudo cat <user_path>/.ssh/authorized_keys • Ask them to use ‘-v’ option • ssh –v foo@bar.example.net

32. 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/KnownGENIPorts • Frequent issues on Campus Guest WiFi networks

33. 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