...
Heather Flanagan, Independent (Chair)
Benn Oshrin, Internet2
Tom Barton, University of Chicago
Jim Leous, The Pennsylvania State University
Steven Carmody, Brown
Ann West, Internet2
Renee Frost, Internet2
Steve Olshansky, Internet2
Wiki Markup
[AI\] (Steven) will email the group a proposed demo script.
Wiki Markup
[AI\] (Benn) will assess the current infrastructure inside COmanage and start defining edge testing.
\
[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.
\
[AI\] (Jim) will send the group screenshots of the Penn State Confluence dashboard.
DISCUSSION
*Assessment*
Benn reported that he has now received access to almost all elements of the project. Benn inquired if the AI to perform an assessment related to any specific objectives (demo, service instance, etc.). Heather replied that the assessment should involve Benn becoming familiar with the components and asking for help if immediate assistance is needed with any issues.
...
TomB stated that Grouper can certainly be used to define/specify a group that has access to a resource. The issue for the GENI VO use case is that the course roster would most likely be defined in the Duke's Grouper system, not in the proposed GENI instance of COmanage. The GENI instance of COmanage will need access to that course roster information. There could be policy issues involved in referring data from one system to another (from Duke's Grouper to the GENI CO). Possibly there could be a federated solution? Possibly the system administrators for the Duke Grouper and for the GENI COmanage instance could work out the details.
Wiki Markup
Ken and Steven will work on getting more details of the GENI/Duke use cases.
...