getting started with your own experiment

Sponsored by the National Science Foundation

Getting Started With Your Own Experiment


Intermediate Topics

Solutions to Common Problems

Getting Help

Advanced Topics

Sponsored by the National Science Foundation 3GEC20– 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


Inter-aggregate Connectivity

Different experiments have different needs, chose based on your experiment!


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


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?


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 documentationHow to configure omni:

http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure/AutomaticOmni workflow and command documentation:

http://trac.gpolab.bbn.com/gcf/wiki/OmniOverview#OmniworkflowHow to use omni:

http://groups.geni.net/geni/wiki/HowToUseOmni


Acting against known aggregatesQuery 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


Add a member to existing slivers

1) Add member to slice

$ omni addslicemember SLICENAME USERNAME2) 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


Advanced Topics


Getting Help



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


Three ways to get SliverStatus

• Flack– “green” is good– Use “Get Status” button to refresh status

• Omni– Use readyToLogin

• Portal– On slice page, use “Ready?” button

Demo

Demo


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


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 timeslice

expiration timeresource

expiration timenow

In general, to extend the lifetime of your resource reservation, you must renew the slice and all resources

resourceresource


Extend slice/resource 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


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’ optionssh –v [email protected]


Clean up now!

Try this now:

$ omni deletesliver SLICENAME --useSliceAggregates

sliceproject

aggregateexperimenter

resource


Advanced Topics


Getting Help Getting Help


Answer is

[email protected]

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)


Ways to Get Help

• Sign Up for :

[email protected]

• Use #geni IRC chatroom

• Go over HowTo pages

http://groups.geni.net/geni/wiki/GENIExperimenter/GetHelp

mailto:[email protected]


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 [email protected] for help

3. Register for resource mailing lists


Finding other resources

• GENI wiki– Pages for Instructors and Experimenters

http://groups.geni.net/geni/wiki


“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


Ways to Learn More

Sign up for [email protected] to be notified about:• Train-the-TA at the start of each semester

(online-only)• GENI Summer Camp

Sign up at: http://lists.geni.net/mailman/listinfo/geni-announce


http://tinyurl.com/GEC19-Feedback

Thank you for attending!

Please fill out the survey

http://tinyurl.com/GEC19-Feedback


Working With Collaborators


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


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


Populating a Project

1. Member-initiated Each experimenter asks to join a project, approval needed

• Typical for Research projects

2. Admin-initiated Project Lead/Admin bulk-adds experimenters

• Typical for Classrooms or Tutorials


Working with multiple members in a slice

Research AsstSlice Lead Post-Doc

Slice MemberProfessor

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


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!


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

getting started with your own experiment

Documents

omni nicknames

omni listslices

omni deletesliver slicename

geni racks

available resources

readytologin slicename

existing slice

existing images