comanage-dev - Notes from COmanage discussion @ Stanford, 5/1/2008
Subject: COmanage Developers List
List archive
- From: Heather Flanagan <>
- To:
- Subject: Notes from COmanage discussion @ Stanford, 5/1/2008
- Date: Fri, 2 May 2008 10:53:11 -0700
Attendees: Digant Kasundra, Scotty Logan, Heather Flanagan, Bruce Vincent (phone), Ken Klingenstein
High level discussion:
* Direction with respect to grouper and signet; Development priorities for
signet/grouper with respect to COmanage
** grouper and signet are still more research project than product
** goal of COmanage is to be a product, a working appliance, and not a
research project
** this does raise issues around modularity of tools in COmanage;
modularity of applications and modularity of infrastructure
components
* Emphasize packaging and production deployment concerns
** one of our goals is to make an appliance that has enough intelligence
to keep itself up to date (is this in scope?)
* Open question: what should the GUI look like? In this space, we'll need
feedback from the VO's - what works for them?
Details:
Each appliance will be identical, and have a base line of tools. One can choose during the setup which of the available base line they'll install. The packages for these tools will come from Debian repositories - the standard for the unconfigured installation, and then a special comanage-package for appropriate configuration overlay.
Base line of tools currently on the list:
* wiki: confluence, mediawiki
* group management: grouper,
* authZ management: signet, webrat
* mailing lists: sympa (mailman out of scope right now - too
difficult)
* shibboleth IDP
* content management: drupal, alfresco
* bug tracking: jira (OOI)
* revision system: Subversion (OOI)
Action item: Ken to follow up with LIGO to see if there is something else they absolutely need and if not, this will be our list of initial targets.
Suggestion: for future tools, point people to Jira and let them make requests; we can go by what's most requested for our prioritization next
Open question: what if you already have one or more of these base packages? We will need to work on comanage installation that allows for people to say "I have it, it's here" and include documentation on how to integrate it; may also want to explore data migrations; there is a lot of guidance we will need to give the world on how to work with COmanage. We also want to put effort in to making sure people can use their own infrastructure if it's possible.
Action item: Digant will be working on the documentation clean up to make the wiki the technical documentation space and the internet2 site the promotional document space.
Other contenders in this space to be aware of
* UAB - Grid
* MyWorks (Steven Carmody); uses grouper, shib; has a very different GUI
in that it approaches the world through specific projects and selecting
tools per project rather than projects per tools
Future discussions
* need to talk more with Lois in the Libraries about GUI
* who can we partner with in the larger space? Google Apps? Amazon EC2?
Heather Flanagan
Director, System Administration
- Notes from COmanage discussion @ Stanford, 5/1/2008, Heather Flanagan, 05/02/2008
Archive powered by MHonArc 2.6.16.