1 / 18

CoManage and CoCoA

Ken Klingenstein, Benn Oshrin. CoManage and CoCoA. CoManage and CoCoA. CoManage An identity management system for virtual organizations and collaborations Addresses identity and access control; leverages Shibboleth, federation, Grouper and …

astra
Download Presentation

CoManage and CoCoA

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. Ken Klingenstein, Benn Oshrin CoManage and CoCoA

  2. CoManage and CoCoA • CoManage • An identity management system for virtual organizations and collaborations • Addresses identity and access control; leverages Shibboleth, federation, Grouper and … • CoCoA (Comanage + Conext + Applications) • Integrates Comanage with • Connext, an open source Dutch collaboration platform • Any domesticated application, including lists, wikis, audioconferencing, videoconferenceing, Google Docs, Al Fresco, Adobe Connect, doodle, command line, etc.

  3. Collaboration platforms • Drive identity and access control for both general collaboration and domain-specific research apps • Leverage existing IdM technologies • Leverage existing IdM deployed infrastructure • Offer a variety of implementation and deployment options • https://spaces.internet2.edu/display/COmanage/Video

  4. CoCoA

  5. Use Cases • LIGO – a major international gravitational physics community with scientists and instruments • Raising – a collaborative effort with community, K-12 and university to preserve the history of an old school • Tenuring – a typical academic process

  6. ABC: A Typical Collaboration and IdM • Has 50 researchers who can schedule ABC instruments, run compute jobs on the TG with ABC allotments, etc • Has 500 academics who need access controlled wikis, ad hoc calendaring (ala Doodle), lists, VO event calendaring, file sharing, chat rooms, videoconferencing, etc. • Has administrators at fifteen universities who can access rosters, change roles, etc. • Has partner VO’s in other countries, with varying privileges on what they can see and use on ABC resources • Has outreach coordinators at 50 school districts who can post/read to certain wiki sections • Works closely with publishers, funding agencies, etc.

  7. Key collaboration questions • What is the anticipated collaboration lifecycle? • Drives deployment models • Who will use/participate? • Drives IdM • Who will administer/manage access controls? • Drives management strategies • What tools and apps does the collaboration need? • Pick from a growing buffet of choices

  8. LIGO • A long-term international cluster of gravitational physicists and their instruments, with hubs in the US, Netherlands, Japan, Italy, and soon India • Complex sharing rules across groups • Seeking integration across instrument management, data analysis, document sharing, outreach • Enabling competition and collaboration

  9. Who participates • Researchers on four continents and their grad students • Undergraduates and K-12 for outreach • Scientific agencies and their program officers

  10. Who manages • PI’s and admins manage large scale permissions • Individual teams create subareas to work on experiments • Coopition among groups creates security issues

  11. The first LIGO List for domestication • wiki/web (read, read-write, admin)  • mailing list (subscribe, moderate, post-only, view-archive, admin)  • repository (read, read-write, admin)  • ticketing system (post, view, modify, manage)  • voting system (create, vote, view)  • calendaring • polling • dcc- document control center  • command line tools • grid space  • guests • googleapps  • conferencing • activity streams  • roster

  12. Raising A School Lifecycle • A collaboration among the students in an old school, alumni, university departments to capture and preserve the history of the building, as it is being razed and a new school built. • Classes in education and history at the university are working with teachers, students, and community in driving the collaboration • Collaboration to exist for two years in development and outreach, then be preserved in the new school and periodically annotated • The history includes photos, journals, records, audio tapes of interviews, discussions, etc.

  13. Raising Participants • Faculty and classes in the University Depts of History and Education • Students in K-12 classes • Community participants

  14. Raising A School Managers • Initially, project leaders, university faculty • University classes will create the initiative, under guidance of faculty and school district staff • Bring in community leaders • Then add Community driven groups • Any group can create a small set of services (wiki, list, photo service, etc) - Distributed and delegated

  15. Raising applications • Wiki • Lists • Doodle • Google Docs • Adobe Connect • On-line photo sharing site with access controls for tagging, etc. • Event calendar with distributed authority

  16. Tenuring lifecycle • Gathering of materials • Internal review processes • Committees within the College • Committees across the university • Student input mechanisms • External reviewers

  17. Who participates • Internal faculty • External scholarly reviewers • Students

  18. Applications • Wiki • Scheduling committee tools • Lists • Secure, synchronizing external storage (alaDropbox) • Anonymous but restricted student input mechanisms

More Related