Skip to Content.
Sympa Menu

comanage-dev - Draft Minutes: COmanage-dev call 21-May-2010

Subject: COmanage Developers List

List archive

Draft Minutes: COmanage-dev call 21-May-2010


Chronological Thread 
  • From: Emily Eisbruch <>
  • To:
  • Subject: Draft Minutes: COmanage-dev call 21-May-2010
  • Date: Mon, 24 May 2010 15:11:30 -0400

COmanage call 21-May-2010 (an “off-week” call)

*Attending*

Heather Flanagan, independent (chair)
Steven Carmody, Brown University
Jim Leous, The Pennsylvania State University
Chris Hubing, The Pennsylvania State University
Ken Klingenstein, Internet2
Benn Oshrin, Internet2
Renee Frost, Internet2

*New Action Items*

[AI]  (Benn) will assess the current infrastructure inside COmanage and start defining edge testing.

[AI]  (Steven and Benn) will talk with TSG about the possibility of provisioning additional VMs.   

[AI]  (Benn, Jim, Chris, Steven,) and possibly others at Brown will discuss what's needed to move ahead with the Women's Science Network VO.

[AI]  (Heather) will email the COmanage-dev list with proposed dates/times for an international call in June.

[AI]  (Steven) will email the COmanage-dev list a pointer to information on the Shibboleth Discovery Service.  

*Carry Over Action Items*

 

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

*Discussion*

Heather introduced Benn to the group.  
Password and access issues are getting worked out.  
Benn spoke with Michael this week and they will speak again next week.

Priorities:

  • Assessment of infrastructure  
    • Benn will provide an assessment.   
    • Will use Rebecca's documentation if possible.
       
  • Testing of “edge cases” to increase COmanage robustness
    • Benn noted that the best way to do Edge Testing is with real people using the product, rather than a staff person supposing what could happen.
[AI]  (Benn) will assess the current infrastructure inside COmanage and start defining edge testing.


  • New Grouper GUI - 
    • Benn spoke with TomB about this. 
    • The decision was to wait for the upcoming release of Grouper 1.6 (later in May) prior to implementing the new Grouper UI into COmaange.
  • Invitation issue 
    • Involves getting people registered on the COmanage instance and getting the right attributes released from the enterprise.
    • Does it make sense to use a mechanism in which people click on a URL inside an email message to initially authenticate?
  • Domestication 
    • The Dutch have made progress domesticating WebEx. 
    • A joint letter is being written to Cisco leadership stating that U.S., Dutch and Norwegions are all putting high priority on use of external groups
  • WAYF improvements and long-term management of the WAYF. 
    • Some of early COmanage users will most likely be international, so it's essential to internationalize the WAYF.
    • Steven suggested looking at the new Shib Discovery Service.
    • Ken remarked that a listing service is one approach to consider – listing providers that we’d like to make globally available: Spaces wiki, REFEDs wiki, etc.
[AI]  (Steven) will email the COmanage-dev list a pointer to information on the Shibboleth Discovery Service. 

  • COmanage Console questions - what should it look like?

  •  Developing a demo instance to include uPortal, as Steven has proposed in his recent email 
    • There is a  GENI Engineering Conference in San Diego July 20-22. Ken could demo the current generic demo or a demo like what Steven suggested, including uPortal. 
    • It will be difficult to have a demo including uPortal ready for July, but this should be developed for future opportunities
    • Would like to create the demo in a "bubble" that is separate and robust
    • Might or might not require multiple VMs

[AI]  (Steven and Benn) will talk with TSG about the possibility of provisioning additional VMs.  

  • Packaging issues: how should COmanage be made available to VOs? Is it run on Internet2 infrastructure? Run on Amazon EC2 cloud?  What level of skill will be needed to download it and run it locally? 
    • Ken said it has been decided it would be desirable for InCommon (rather than Internet2) to run a service instance of COmanage.  Ken is crafting a document outlining what might be needed for InCommon to operate a COmaange service. 

  • Discussions with the Women’s Science Network 
    • This group is interested in COmanage including Drupal. 
    • They would like a 4-year service commitment
    • Could the group's full-time administrator be helpful in entering data on the the initial COmanage users? Could she contact campuses where the participants are based and get the attribute release policy set?  
    • The best solution is to use uApprove.  

[AI]  (Benn, Jim, Chris, Steven,) and possibly others at Brown will discuss what's needed to move ahead with the Women's Science Network VO.


*Documentation Status*

Chris reported that Rebecca went as far as she could for now on developing COmanage documentation. The newest COmanage VM (from Sept.) had problems, so Rebecca was documenting things that weren’t working right. If a new VM is released that works well, Rebecca can continue her project.

The documentation Rebecca developed so far is in the Spaces wiki.  She didn’t overwrite any of the older documentation. 

*Organizations with COmanage Interest*

Duke University and Common Solutions Group may have interest in COmanage.

It was noted that iPlant and many other organizations use uPortal, another reason to pursue the type of demo Steven has envisioned.

U Penn is looking at HUBzero, which ties into Teragrid. 

Steven is pursuing information on a Math Institute that could be interested in COmanage.

*International Participation*

Niels is running a BoF about collaboration services at the Terena Networking Conference in Vilnius, Lithuania, May 31 - June 3.

Heather has spoken with Niels about consolidating international calls for the summer, with a hope
to set one up in June, after  Terena. 

[AI]  (Heather) will email the COmanage-dev list with proposed dates/times for an international call in June.
 

Next Call:  Friday, May 28, 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

 













  • Draft Minutes: COmanage-dev call 21-May-2010, Emily Eisbruch, 05/24/2010

Archive powered by MHonArc 2.6.16.

Top of Page