COmanage Call 19-Mar-2010
*Attending*
Ken Klingenstein, Internet2
Steven Carmody, Brown
Chris Hubing, Penn. State U
Michael Gettes, MIT
Jim Leous, Penn. State U.
Dan Pritts, Internet2
Steve Olshansky, Internet2
*New Action Items*
[AI] (Ken and Michael) will rev the job description
[AI] (Ken) will confirm the monthly call slot (10 am ET first Thursday of the month?) with the Dutch and send it out to the list.
[AI] Jim will send the group some screenshots of the Penn State Confluence dashboard.
[AI] (Jim) will send out info about a potential Energy Dept. hub
*Carry Over Action Items*
[AI] (Tom) and (Ken) will discuss moving forward on incorporating the Grouper Lite UI into COmanage.
[AI] (Jim) will discuss with Kevin possible CIC engagement with COmanage.
[AI] (Ken) will follow up with Niels about domesticating Adobe Connect.
[AI] (Danno) will continue to pursue communication with U. Minnesota about domesticating Adobe Connect.
[AI] (Heather) will resubmit the request for COmanage service for the Ivy+ Infrastructure.
*DISCUSSION*
*Spring Internet2 Member Meeting, Dutch CIO Visit, NIH Meeting*
Fifteen Dutch CIOs will be attending SMM. There will be a conversation about COmanage with the Dutch and other international attendees at the "Interfederation Meeting" on Sunday evening. Ken may invite NIH representatives as well. There does not seem to be another time during SMM for a meeting with NIH.
Spring Member Meeting sessions of note for COmanage:
- Interfederation Meeting (Invitation Only)
April 25, 5:00 PM - 7:00 PM, Salons E/F
- COmanage Working Group
April 26, 9:15 AM - 10:15 AM, Salon A
- Federated Collaboration Approaches (Track Session)
April 27, 8:45 AM - 10:00 AM, Salon A
Speakers: Heather, Steven, Michael and Niels
*Calls with the Dutch and Status*
Calls to touch base with the Dutch have been tentatively scheduled for on the first Thursday of each month at 10:00 am EDT. Ken will confirm.
[AI] (Ken) will confirm the monthly call slot (10 am ET first Thursday of the month?) with the Dutch and send it out to the list.
The Dutch plan to set up a registry of domesticated applications. This will be discussed at the next call with the Dutch.
The Dutch are starting to roll out their nationwide COIN collaboration infrastructure project. This involves a national service to handle identity and group work with applications, distributed to most of the SURFnet member institutions. Campuses will be hosting/offering the applications, not SURFnet directly.SURFnet also has a wing dedicated to e-science and e-research that is targeted to big science VOs for which there will be a broader collaboration service with applications. We will learn more at the SMM.
*Job Description for COmanage Project Person*
Ken sent out a draft of the job description for the COmanage Project Person to work under Heather's direction. Ken welcomes input.
Michael's input will be valuable. Ken and Michael will chat next week to discuss further.
The COmanage Project Person will be expected to engage with the other developer groups, and Ken will modify the job description to reflect this.
[AI] (Ken and Michael) will rev the job description
*Future Directions*
Michael: Has there been a determination on whether COmanage will take on functions similar to what is happening in SURFnet?
Ken: A decision needs to be made whether COmanage falls under the InCommon or Internet2 structure. This is not clear yet. Once decided, either InCommon Steering or Internet2 governance will provide more specific direction about COmanage. Most likely COmanage will initially have a service for several VOs that is similar in scope to the Dutch research service.
It was noted that a multi-year commitment is not required for work with GENI. COmanage engagement with most likely LIGO is expected regardless of the result of grant applications.
Steven briefly outlined two VOs he sees as prospects for COmanage engagement. One is interested in social networking, email, Drupal , etc. This VO is able to fund a programmer. Another potential VO is an international institute that will have more extensive application and support needs.
*TSG Support*
Ken asked if will be reasonable to expect that TSG might ramp up a greater level of service for COmanage in the future. Danno suggested that most likely TSG can help host a COmanage pilot service, but probably cannot support applications.
Ken stated the desire to offer Adobe Connect as part of COmanage. The Dutch have successfully offered Adobe Connect as part of their collaboration service, but they are hosting Adobe Connect internally. Michigan State and Penn State also both host Adobe Connect. Internet2 does not host Adobe Connect - it buys the Adobe Connect service --- and is currently not considered hosting Adobe Connect, due to cost.
DimDim is an open source meeting service. However, there were issues integrating it with COmanage, which is why COmanage integrated OpenMeetings. Ken is going to ask Michael for more details on the history of using DimDim and OpenMeetings in COmanage.
It was mentioned that COmanage will probably require 4-6 months of testing and developer time before being ready for usage in a production environment. Also, the Grouper Lite UI needs to be integrated into COmanage.
*Service Offering Document*
SteveO and Heather would like feedback on the COmanage Service Offerings document:
https://spaces.at.internet2.edu/display/COmanage/COmanage+Service+Offerings+-+DRAFT
*Dashboard*
Using Confluence or Drupal as a COmanage "dashboard" was discussed.
There are examples at Penn State of using Drupal for a dashboard with pointers to a wiki spaces on Confluence. The GUI has been made to look similar between Confluence and Drupal.
[AI] Jim will send the group some screenshots of the Penn State Confluence dashboard.
*Domestication and Getting Shib to work with SSH*
LIGO is interested in domesticating Subversion, but this is challenging. In reply to an inquiry, Ken inform LIGO that the Dutch have not tackled Subversion domestication yet. Chris and a key LIGO developer will talk more about Subversion domestication issues at the SMM. Chris explained that the solution involves SSH and keys.
Getting Shib to work in the SSH environment will help solve issues with domesticating Subversion.
Steven mentioned two approaches:
1) an approach developed in Spain is to use a Shib enabled service thru which SSH keys are uploaded. This is leveraging Shib to create and environment where traditional SSH will work.
2) a complex approach called Moonshot involving pushing SAML into lower layers. The result is every protocol would be running over SAML enabled tunnels. Steven shared Josh Howlett's Moonshot slides with the list. Josh will present aspects of Moonshot at the MACE-Dir Working Group at SMM:http://events.internet2.edu/2010/spring-mm/agenda.cfm?go=session&id=10001155&event=91
*Documentation Status*
Rebecca has reorganized the existing COmanage documentation on the wiki, and she would like feedback on what to document next. Suggestion is to focus on documenting how to bring up and step through COmanage.
Next call: Fri. April 2 at 2pm ET.