COmanage Product Roadmap (Functional)

Include logo
Make sure items from grant are appropriately included
consider splitting/organizing based on thing being delivered (service/platform/VM) (specifics versus generalization issues here)
Side-by-side comparison, or "related to" link to technical roadmap

Primary Market = Large interinstitutional research groups and collaborative organizations
Secondary Markets = education and research-related committees, small interinstitutional research groups and collaborative organizations

Already completed:

• Creation and demonstration of prototype instances
• Evaluation of possible downloadable/VM instance
• Initial collaboration with international groups
• NSF grant approval (Award 1032468)

Committed deliverables:

Year one (2010-2011)

• The User-driven Provisioning/de-provisioning library
• Using the federated SSH toolset, a comprehensive federated SSH service will be installed in LIGO and iPlant, including provisioning and de-provisoning capabilities
• Within the primary CO (LIGO, iPlant, OOI, NEON), COmanage will be implemented with appropriate UI for the CO
• A pilot COmanage instance within InCommon
• Web services presentation of COmanage services for use by other applications, gateways, portals, etc.
• Presentations will be made at Internet2 member meetings and the LIGO, iPlant, OOI and NEON all-hands meetings.

Year two (2011-2012)

• Additional federated SSH architectures and implementations will be added to the toolkit, leveraging work within IETF and in Project Moonshot
• Install COmanage instance in Azure and Amazon
• Develop OpenSocial toolkit for other VOs and tools to present COmanage

Year three (2012-2013

• Privilege management basics within Grouper for leveraging within COmanage.
• A toolkit for CO

Business needs

• Creation of a Business model for service instance(to charge or not to charge for CO's outside those identified in the NSF grant?)
• Determine service location
• Complete requirements gathering from participating collaborative research organizations as directed by the NSF grant (LIGO, iPlant, OOI, NEON)
• Determinations around levels of support with/for the participating CO
• Extensive coordination, planning and development with other collaborative platform efforts (keep international cooperation at top of list)

Functional needs

• Provide a model for groups to stand up their own instance, based on the work done with COmanage
  • COmanage Gears (console, connector, documentation)
• Registry of Domesticated Applications
• Service instance where smaller CO can actively use (and help test) COmanage features (it is expected the larger CO will stand up their own instances)

Out of initial scope (but still on the list)

• Customizations based on secondary markets
• Support of domain-specific tools within a COmanage instance