Attending
Heather Flanagan, Internet2 (chair)
Ken Klingenstein, Internet2
Steven Carmody, Brown
Keith Hazelton, U-W, Madison
Benn Oshrin, Internet2
Dan Pritts, Internet2
Steve Olshansky, Internet2
Emily Eisbruch, Internet2 (scribe)
New Action Items
[AI] (Heather) will schedule the GENI demo.
[AI] (Heather) will schedule a call with Keith to discuss various issues, including creating a written record of ScottK's COmanage / LIGO work.
[AI] (Heather) will talk to Nirav regarding COmanage involvement with iPlant and IRODS
[AI] (Heather) will work on arranging a meeting with NSF people during SMM
[AI] (Steven) will extend his inquiry on iPlant and Shibboleth to Nirav
[AI] (Benn) will create a design draft for COmanage enrollment / onboarding and circulate it to the group
Carry Over Action Items
[AI] (Keith) will make sure that the COmanage glossary covers roles and groups accurately. https://spaces.at.internet2.edu/display/COmanage/Glossary
[AI] (Ken) will provide a link to the French listing regarding applications and sets/bundles of attributes.
[AI] (Keith) will ask Roland and Leif to clarify how social identity assertions will be handled in their system.
[AI] (Ken) will contact David Groep about VOMS GUMS.
[AI] (Steven) will develop a one-page write-up on attribute aggregation.
DISCUSSION
COmanage Demo
• Steven is now able to login to the COmanage demo https://demo.co.internet2.edu/gears/
• Steven worked on the Discovery Service issue.
• Brown is now releasing attributes.
• Steven will do more exploration and investigation of the demo and provide feedback.
• Also, Benn will give Danno permission to log into the COmanage demo
COmanage GENI Demo
• Heather: What we’ve been doing with the demo is straightforward
• Q: Is this general demo sufficient for the needs of GENI, or is GENI looking for something more specialized/customized?
• Steven: let’s start w a general demo and then listen carefully
• Tom Mitchell is working towards a demo for the GENI meeting, July 26-29, 2011 in Chicago
• For the GENI demo Stage One, the plan is:
• ability to do federated login to a portal
• behind portal should be ability to store info about people and assign them privileges
• embedded in the portal should be some ability to access things in GENI
• embedded in the portal should be some of the CIlogon code
• This Stage One GENI demo is similar to the software that Benn has built
• Possible Stage Two for GENI:
• Stand up a second instance representing a project that wants to use GENI
• This would involve reconfiguring Shib in front of the GENI portal
• So involved communication with another CO regarding group memberships and permissions
[AI] (Heather) will schedule the GENI demo.
Steven has been communicating with JohnK regarding getting GENI into InCommon as a member
IPlant and IRODS
• An email from Nirav mentioned working with IRODS to build interfaces for user data management
[AI] (Heather) will talk to Nirav regarding COmanage involvement with iPlant and IRODS
• Based on Nirav's email Steven has questions on iPlant's planned use of Shibboleth
• Assuming iPlant will run their own IdP, if a member of IPlant has a federated identity, can that be used?
• Is the plan to Shib-enable IRODS or to have the iPlant portal log into IRODS as a known super-user?
[AI] (Steven) will extend his inquiry on iPlant and Shibboleth to Nirav
Social to SAML
• Ken stated that Social to SAML could be of interest to iPlant
• There is a need to discuss how to approach Social to SAML and how to integrate it w COmanage.
Discussions with NSF at SMM
• Nirav will be a member meeting
• NSF Representatives will be at SMM
[AI] (Heather) will work on arranging a meeting with NSF people during SMM
Code Update (Benn)
• Demo server has been updated with extended attributes so it is possible to add per-CO attributes to the database without doing special coding.
• Next major coding project involves updating the enrolling/ onboarding
• [AI] (Benn) will create a design draft for COmanage enrollment / onboarding and circulate it to the group
Involving a Broader Group in Discussion (Ken)
• Should we involve a larger group in COmanage discussions on a periodic basis, to be sure we are putting together all angles, including Shib and provisioning, etc.?
• Incorporate some of what the Moonshot people are doing?
• Could include the application issues, separate from some gears work
• Harness around a group of people, who have primary activities elsewhere, and see if we are on the same page
• Benn noted that he is plugged into the provisioning discussions that are ongoing
• COmanage is a natural point of integration for many new things being developed.
• One approach would be to make the COmanage roadmap more public and invite comment.
• Ken: Are we going to go beyond the kit approach, looking at a more turnkey approach?
• Will there be a COmanage service offering?
• Benn: a few months back, we had talked about integration services consulting arm.... maybe we need to push that along
• How is LIGO deploying COmanage? Can we document that?
[AI] (Heather) will schedule a call with Keith to discuss various issues, including creating a written record of ScottK's COmanage / LIGO work.
Terminology
• Ken noted there are still some needs for more precise terminology.
• Heather will work on terminology and report back to the group.
Next Call: Friday, April 15, 2pm ET
__________________
2011 Spring Member Meeting in Arlington, VA
__________________
COmanage Working Group at SMM:
Monday, April 18, 2011, 9:15 AM - 10:15 AM
Location: Salon A
http://events.internet2.edu/2011/spring-mm/agenda.cfm?go=session&id=10001750&event=1035
__________________
ALSO AT SMM:
International Collaboration Platforms – SURFconext, COIP, COmanage
Monday, April 18, 2011, 4:30 PM - 5:30 PM
Location: Salon D/Ehttp://events.internet2.edu/2011/spring-mm/agenda.cfm?go=session&id=10001706&event=1035
---------------
Supporting Research Communities: Collaborations in Action
Tuesday, April 19, 2011, 1:15 PM - 2:30 PM
Location: Salon I/II/IIIhttp://events.internet2.edu/2011/spring-mm/agenda.cfm?go=session&id=10001705&event=1035
---------------