1 / 13

Working with Collaborators

Working with Collaborators. 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. Working with multiple members in a slice.

ugo
Download Presentation

Working with Collaborators

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Working with Collaborators

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

  3. Working with multiple members in a slice Members of all slices in a project: • Project Leads (Professor) • Project Admins (Post-docs, researchers) Other can be added manually Professor Slice Admin Research Asst Post-Doc Slice Member Slice Lead http://groups.geni.net/geni/wiki/GENIConcepts#Slice

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

  5. Slice Access: Logging in to resources 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 –-useSliceMembers Alternatively… $ addMemberToSliceAndSliversmyslice username Slice membership does not guarantee ability to login to resources! Only works on InstaGENI/ProtoGENI

  6. Solutions to Common Problems

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

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

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

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

  11. Slice and Sliver Expiration $ omnirenewslice 01-31-14 # renew each sliver individually $ omnirenewsliver –a gpo-igmyslice 01-31-14 $ omnirenewsliver –a renci-egmyslice 01-31-14 $ omnirenewsliver –a missouri-igmyslice 01-31-14 # OR renew all known slivers for “as long as possible” $ omni-V 3 renew myslice 01-31-14 -–useSliceAggregates--alap Extend slice/resource expirations Hands-On

  12. 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: • Check the status of the sliver • Try having a collaborator login • Look for loaded keys sudo cat ~other_user_path/.ssh/authorized_keys • Ask them to use ‘-v’ option ssh –v foo@bar.example.net

  13. Clean up now! Try this now: $ omnideletesliver SLICENAME --useSliceAggregates project resource experimenter aggregate slice

More Related