COmanage Developers List

[Emily Eisbruch <>]

Draft Minutes: COmanage Call: 29-April-2011 

Attending

Heather Flanagan, Internet2 (chair)  
Ken Klingenstein, Internet2  
Steven Carmody, Brown  
Keith Hazelton, University of Wisconsin-Madison 
RL “Bob” Morgan, U-Washington  
Benn Oshrin, Internet2 
Steve Olshansky, Internet2  
Emily Eisbruch, Internet2 (scribe)  

New Action Items

[AI] (Heather) will revise the COmanage TAC proposed charter based on feedback received.  

[AI] (Heather) will create a wiki space for the COmanage TAC.  

[AI] (Ken) will inform the appropriate Internet2 executives of the upcoming international travel funded by SURFnet

[AI] (Heather) will review the CO Requirements Assessment tool to see if it needs updating
 https://spaces.internet2.edu/display/COmanage/CO+Requirements+Assessment

Carry Over Action Items
 
[AI] (Ken) will provide a link to the French listing regarding applications and sets/bundles of attributes.   

[AI] (Ken) will contact David Groep about VOMS GUMS.   

[AI] (Steven) will develop a one-page write-up on attribute aggregation.  

DISCUSSION

COmanage Technical Advisory Committee (TAC) 

The proposed charter that Heather developed for the COmanage TAC was reviewed. Heather stated that the idea is that the COmanage TAC would start as a mailing list, with no calls scheduled.

_______________________

Proposed charter:
The COmanage Technical Advisory Committee will focus on the technical questions and issues that relate to the COmanage platform.  They will look at key questions in terms of technical challenges in the platform, such as resolving identity correlation within a VO, namespace issues, adding external attribute providers to a VO, APIs, metadata management, UI recommendations, etc.  This group will run in parallel to the Dev group, which is more of broader view forum, looking more towards the platform roadmap, discussing service model concerns, application domestication, feeding input in to the international collaboration group, and looking at VO participation.  This is a technical committee and a focus on development up to and including code submission is encouraged.
Initial membership: Benn Oshrin, Scott Koranda, Keith Hazelton, Michael Gettes, RL Bob Morgan, Tom Barton, others?

_______________

Keith suggested revising the following sentence for clarity: "This group will run in parallel to the Dev group, which is more of broader view forum, looking more towards the platform roadmap, discussing service model concerns, application domestication, feeding input in to the international collaboration group, and looking at VO participation. "

Keith noted that the description for the TAC sounds like a users group, soliciting input, etc.  

Q: Why is another list needed now, since a relatively small number of people are involved?

A: The VO / CO space is central to the middleware initiative and to our funding. This is a possible way to pull more people into the process, which could be beneficial.

Benn: Should we rename the "dev" list (perhaps to a "discuss" list) and reserve the name "dev" for the actual coders? 

SteveO: a recent change of the OPENID list to the SOCIALIDENTITY list caused problems.

[AI] (Heather) will revise the COmanage TAC proposed charter based on feedback received.  

[AI] (Heather) will create a wiki space for the COmanage TAC.    

SteveO will ensure that this space is "readable" to the world and "writeable" to the COmanage TAC group.

 Meetings at SURFnet in July

In July, SURFnet will fund Heather and Benn to visit Amsterdam for meetings around collaboration platform logistics.

This will be a good opportunity to continue discussions that started at SMM around sharing work that can benefit both COIN and COmanage.

[AI] (Ken) will inform the appropriate Internet2 executives of the upcoming international travel funded by SURFnet

Ken suggested two agenda items for the meetings with SURFnet:

- metadata for different platforms working together. 

- do we want to use Janus for metadata manager for multiple federations?

Benn noted regarding the inter-CMP metadata exchange, Benn and Niels discussed this, and they would like to have use cases.

COmanage Assessment Tool and COmanage Assembly Kit

Ken suggested checking the COmanage Assessment Tool to see if it needs any updates:

[AI] (Heather) will review the CO Requirements Assessment tool to see if it needs updating
 https://spaces.internet2.edu/display/COmanage/CO+Requirements+Assessment

Heather is working on a downloadable document called the COmanage Assembly Kit and would appreciate feedback. Scott Koranda has reviewed the COmanage Assembly kit already.

Once approved by the broader COmanage team, Heather will ask the Internet2 Technical Services Group to review the COmanage Assembly Kit.

Ken: Does the service that Globus Online is crafting from Grouper and Shib assemble piece parts in the same fashion as COmanage?  

Heather: will find out.

Ken: Some representatives from Rachana's group (at Argonne National Laboratory) will be at Advance CAMP May 25-27.  Benn will be there and can ask how they have assembled our piece parts.

VO Updates

LIGO Update: Benn had useful technical discussions and design talk with ScottK of LIGO at 2011 SMM

- IPlant Update: Heather is working on a setting up a call with iPlant, Shib and IRODS representatives to talk about the work being planned. Ken suggested including Bob or Scott Cantor in that conversation. There could be discussions about the PDP and the PEP.  Option to move the PDP upstream raises important design questions. Keith would like be on the call from the MACE-paccman point of view

- Project Bamboo Update : Steve Masover is getting ready for some upcoming demos. Bamboo service platform (infrastructure services) is of particular interest. They are a sort of IdP for the Bamboo community in terms of entitlements. Keith hopes to bring back to COmanage info on the specifications needed for interfaces, web services signatures needed for the early demos, info on a simple registry, group management, etc.

RL "Bob" mentioned that  U-Washington has a working restful web services for person and groups. Keith will follow up on this.

Ken: A possible Bamboo requirement is a gateway between social ID, OPEN ID and the federated world.  This has come up in conversations with NSF.

Keith: Yes, Project Bamboo would like to be able to serve social identities. Approaches: Keep close watch on work going on at NORDUnet for gateway services, as well as Chris Hubing's work at Penn State.

The topic of social identities and federations will likely arise at the upcoming REFEDS meeting

- GENI Update : Heather understood that GENI downloaded COmanage code from the SVN repository. Tom Mitchell is working towards a demo in July.  Steven has been in touch with Tom Mitchell and will check in with him again next week.

- Penn State Update: JimL informed Heather that he gave a COmanage presentation to the faculty advisory committee, and it went well.

- VIVO  Update: Ken spoke to Debbie Bucci recently about VIVO . There are access control decisions in VIVO (e.g., is this person a PI?)  that should be managed by attributes.

Next Call: Friday, 13-May-2011, 2pm ET

Emily Eisbruch, Technology Transfer Analyst

Internet2

office: +1-734-352-4996 | mobile +1-734-730-5749

Visit our website: www.internet2.edu
Follow us on Twitter: www.twitter.com/internet2
Become a Fan on Facebook: www.internet2.edu/facebook