1. Sponsored by the National Science Foundation Getting Started With Your Own Experiment Sarah Edwards, GENI Project Office

2. Sponsored by the National Science Foundation 2 GREE WC ‘14 – Jan 8, 2014 Outline Intermediate Topics Solutions to Common Problems Getting Help

3. Sponsored by the National Science Foundation Intermediate Topics Sarah Edwards, GENI Project Office

4. Sponsored by the National Science Foundation 4 GREE WC ‘14 – Jan 8, 2014 Three ways to get SliverStatus Flack –“green” is good –Use “Get Status” button to refresh status Omni –Use readyToLogin Portal –On slice page, use “Get Status” or “Get All” buttons

5. Sponsored by the National Science Foundation 5 GREE WC ‘14 – Jan 8, 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 IG image: http://groups.geni.net/geni/wiki/HowTo/ManageCustomImagesIns taGENI

6. Sponsored by the National Science Foundation 6 GREE WC ‘14 – Jan 8, 2014 Inter-aggregate Links Stitching –Creates an inter-domain VLAN –Stitcher: Distributed with gcf/omni Note: Not yet included in Windows Beta release 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

7. Sponsored by the National Science Foundation 7 GREE WC ‘14 – Jan 8, 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

8. Sponsored by the National Science Foundation 8 GREE WC ‘14 – Jan 8, 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?

9. Sponsored by the National Science Foundation 9 GREE WC ‘14 – Jan 8, 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

10. Sponsored by the National Science Foundation 10 GREE WC ‘14 – Jan 8, 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!

11. Sponsored by the National Science Foundation 11 GREE WC ‘14 – Jan 8, 2014 Slice Access: Logging in to resources Slice membership does not guarantee ability to login to resources! Option 1: Make resource reservation from Portal fix the membership of the slice Use the add resource button in the portal Option 2: Ensure common public key is loaded distribute common public key to members ask members to upload it in their profile use corresponding private key to login Ability to login can help in debugging!

12. Sponsored by the National Science Foundation Solutions to Common Problems

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

14. Sponsored by the National Science Foundation 14 GREE WC ‘14 – Jan 8, 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

15. Sponsored by the National Science Foundation 15 GREE WC ‘14 – Jan 8, 2014 Extend slice/resour ce expirations Slice and Sliver Expiration $ omni renewslice 01-31-14 $ omni renewsliver myslice 01-31-14

16. Sponsored by the National Science Foundation 16 GREE WC ‘14 – Jan 8, 2014 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 /.ssh/authorized_keys –Ask them to use ‘-v’ option ssh –v foo@bar.example.net

17. Sponsored by the National Science Foundation 17 GREE WC ‘14 – Jan 8, 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

18. Sponsored by the National Science Foundation 18 GREE WC ‘14 – Jan 8, 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

19. Sponsored by the National Science Foundation 19 GREE WC ‘14 – Jan 8, 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

20. Sponsored by the National Science Foundation Getting Help

21. Sponsored by the National Science Foundation 21 GREE WC ‘14 – Jan 8, 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

22. Sponsored by the National Science Foundation 22 GREE WC ‘14 – Jan 8, 2014 Ways to Get Help Check out the HowTo pages Email geni-users@googlegroups.com or help@geni.net Use #geni IRC chatroom Sign up for mailing lists http://groups.geni.net/geni/wiki/GENIExperimenter/GetHelp

23. Sponsored by the National Science Foundation 23 GREE WC ‘14 – Jan 8, 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