Sponsored by the National Science Foundation Working with Collaborators.
-
Upload
lawrence-cannon -
Category
Documents
-
view
216 -
download
1
Transcript of Sponsored by the National Science Foundation Working with Collaborators.
Sponsored by the National Science Foundation 2GREE-SC – July 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
Sponsored by the National Science Foundation 3GREE-SC – July 21, 2014
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 (Post-docs, researchers)
Other can be added manually
http://groups.geni.net/geni/wiki/GENIConcepts#Slice
Sponsored by the National Science Foundation 4GREE-SC – July 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!
Sponsored by the National Science Foundation 5GREE-SC – July 21, 2014
To ensure access in collaborator’s resources:Option 1: Make resource reservation from Portal or omni
Option 2: Use a common public key
Add slice member’s accounts to existing resources:$ omni -V 3 poa SLICE geni_update_users
--useSliceAggregates –-useSliceMembersAlternatively…
$ addMemberToSliceAndSlivers myslice username
Slice Access: Logging in to resources
Slice membership does not guarantee ability to login to resources!
Only works on InstaGENI/ProtoGENI
Sponsored by the National Science Foundation 7GREE-SC – July 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
Sponsored by the National Science Foundation 8GREE-SC – July 21, 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 “Ready?” button
Demo
Demo
Sponsored by the National Science Foundation 9GREE-SC – July 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
Sponsored by the National Science Foundation 10GREE-SC – July 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 timeslice
expiration timeresource
expiration timenow
In general, to extend the lifetime of your resource reservation, you must renew the slice and all resources
resourceresource
Sponsored by the National Science Foundation 11GREE-SC – July 21, 2014
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
Sponsored by the National Science Foundation 12GREE-SC – July 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’ optionssh –v [email protected]