Getting Started W ith Your Own Experiment

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

2. Outline • Intermediate Topics • Solutions to Common Problems • Getting Help

3. Intermediate Topics Sarah Edwards, GENI Project Office

4. 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/ManageCustomImagesInstaGENI

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

6. Rack Differences 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.

7. 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. Working with multiple members in a slice Members of all slices in a project: • Project Leads (Professor) • Project Admins (TAs, Graders) Other can be added manually Professor Slice Admin Research Asst Post-Doc Slice Member Slice Lead

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

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

11. Solutions to Common Problems

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

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

14. Slice and Sliver Expiration $ omnirenewslice 01-31-14 $ omnirenewslivermyslice 01-31-14 Extend slice/resource expirations

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

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

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

18. Getting Help

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

20. Ways to Get Help • Check out the HowTo pages • Email geni-users@googlegroups.com or help@geni.net • Use #geniIRC chatroom • Sign up for mailing lists http://groups.geni.net/geni/wiki/GENIExperimenter/GetHelp

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