COmanage Developers List

[Digant C Kasundra <>]

Notes from conf call on 4/25/2008:

The OOi team explained that the immediate goal was to create a core 
infrastructure to create oceanographic communities.  The infrastructure 
should be usable by different communities to share resources, including 
data, computational resources, and managed resources.  Members should be 
able to setup and maintain multiple communities, of which "public" would be 
one.

The group consists principally of Univ of Washington, Woods Hole 
Oceanographic Institution, and UC San Diego.  However, much of the work has 
been contracted out to other academic and commercial institutions, who 
would also be users and consumers of the project.

OOi was hoping to manage Confluence, Jira, Alfresco, subversion 
(web-based), and a mailing list system (mailman currently but are open to 
using Sympa).

The basic use case would be one where individuals would come from their 
primary institutions with their attributes and identity and setup a 
facility, where each facility is a virtual organization.  The individual 
would first register their lab and then build communities of use.

There was mention of needing the deployment to be scalable and fault 
tolerant (for instance, using clustered MySQL servers for redundancy).  As 
the primary deployment of COmanage is targeted to be a blackbox vmware 
appliance, there is an open question as to whether the use of VM's high 
availability to keep the vm server running will be sufficient to meet these 
requirements or whether COmanage will need to support automatic 
configuration and support for "clustering," a feature that Scotty L and 
Digant K had discussed would be an essential feature for later phases but 
not for initial release.



--
Digant C Kasundra 
<>
Technical Lead, ITS Unix Systems and Applications, Stanford University