COmanage Developers List

[Emily Eisbruch <>]

COmanage Call 3-Sep-2010

*Attending*

Heather Flanagan, Independent (chair)  

Benn Oshrin, Internet2 

Ken Klingenstein, Internet2  

Steven Carmody, Brown   

Jim Leous, Pennsylvania State U.  

Renee Frost, Internet2 

Ann West, Internet2  

Steve Olshansky, Internet2 

Emily Eisbruch, Internet2, scribe 

*New Action Items*

[AI] (Ken) will send out an issue summary prior to the Sept 10th SSH call.

*Carry Over Action Items*

[AI] (Heather) will discuss with Benn timeframes for turning mockups into reality.

[AI] (Heather and SteveO) will continue work on updating the COmanage website and wiki.  

[AI] (Ken) will develop a COmanage Service Manager job description.

[AI] (Ken) will email the group a COmanage entrance interview/survey for a VO.

[AI] (Steven and Benn) will continue to work on demo development. 

[AI] (Ken) will initiate discussion with UK around collaboration platform work.

[AI] (Jim) will send the group screenshots of the Penn State Confluence dashboard. 

DISCUSSION

*SSH Call*

A call is scheduled for Friday, 10-Sep-2010 to discuss federated SSH. It was suggested to do some requirements gathering ahead of time.

Notes from ACAMP discussion on “Non-Browser Apps, Grids and CI” are:

https://spaces.internet2.edu/pages/viewpage.action?pageId=15172053

Steven summarized some of the issues:

• Possibility to add federated protocols to the set of authentication protocols used in SSH. This comes up in Moonshot discussions.  
• Issue of which SSH client to focus on and design for. There are several clients, including OpenSSH, Web-based SSH (used by Teragrid), PuTTY (on Windows systems).
• If federated protocols are not added to SSH, then how should account linking between SSH keys and targets be done?
• Provisioning / deprovisioning issues on the different targets.

Ken noted there are two layers:

1. Managing which set of groups and permissions get SSH accounts.
2. Populating SSH accounts with identities and assigned privileges

Benn stated that other issues could include:

-  protocols other than SSH

- discovery

- privacy

[AI] (Ken) will send out an issue summary prior to the SSH call on Sept 10.

*VO Workshop for 2011*

On a recent multi-agency phone call, the topic was raised of demand for a VO workshop (targeted to VO architects) in 2011. Focus could be on IdM issues and VIVO

 (http://www.vivoweb.org/)

 could be brought into the discussion. On a future COmanage-dev call, we should think about the best timing for such a VO Workshop, probably to be held in the DC area. Ken plans to be in communication with OCI about the possibility for such a VO Workshop. 

Jim: Penn State may be managing several VOs and would be interested in such a VO workshop.

Note: The proposed VO Workshop would be in addtion to ACAMP (scheduled for week before Memorial Day in 2011) and InCommon CAMP (date not yet set for 2011). 

*CO Assessment Tool*

https://spaces.internet2.edu/display/COmanage/CO+Requirements+Assessment

Ken hopes to present this assessment tool at the DataOne meeting in Chicago Sept 8-9. Ken will send to COmanage-dev a link to a survey about how to protect data inside DataOne. 

Heather received a few comments about the assessment tool from Niels and another colleague.  There was the suggestion to add a question on the importance of the resources being protected ( i.e. is  medical data involved, should HIPAA rules be considered? )

Ken noted that many VOs are working on similar IdM challenges, such as authentication, but generally they are working in isolation from other VOs rather than sharing their work.  Thus the VO Workshop in 2011 could be key.

Ken plans to share the assessment tool with representatives at OCI. 

Ken noted there could be advantages to generalizing instead of specifying Google apps on the assessment tool. Jim stated that there are various outsourced collaboration tools we could ask about. Perhaps mention Zotera, Delicious Bookmarks, VIVO, etc. 

[AI]  (Heather and SteveO) will elevate the assessment tool on the COmanage site. (DONE)

*Functional Roadmap *

https://spaces.internet2.edu/display/COmanage/Functional+Roadmap

Ben noted that a technical roadmap has also been started, but there is not enough information yet. 

https://spaces.internet2.edu/display/COmanage/Technical+Roadmap

There will be more info for the technical roadmap once we continue to flush out requirements (such as from the SSH discussion). 

Ken asked, could the roadmaps show the possibility of developing both a “standard” use interface and a social type of interface?  Can COmanage offer both types of interfaces? 

Benn:  Yes, we have focused on the backend. But on the front-end, it would be good to have optional integration with a portal-like interface. 

Steven: many of the VOs seem to already have a front-end portal or content management environment. They are looking for access to the gears components and a way to plug that into their existing front-end environment. 

It was suggested to add to the functional roadmap an item about working with the VOs, helping the VOs integrate the COmanage toolkit into their existing sites.

Next Call: Friday, Sept 17 at 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