Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

COSMOSInitalPrototype

Revision as of 12:30, 21 December 2006 by Sluiman.ca.ibm.com (Talk | contribs) (Initial Prototype Proposal)

COSMOS Main Page

Proposal

The purpose of this prototype is to flush out technical details and issues as well as provide something usable that moves toward the kind of capabilities COSMOS intends to provide. The desire is also to do this quickly and iteratively so there is continuous value.

TPTP provides some basic similar uses cases but does not have a robust and scalable data storage systems or a web orient user interface. This is why TPTP has committed to resolve it's scalabiltiy issues in the 4.4 release (part of Europa in June 07) and do it in collaboration with COSMOS. The end goal is to make the data and data collectors sharable between the projects in order to support life cycle use cases that span the target user types of each project.

The proposal for the first step is to leverage the TPTP data collectors for statistical, trace and log data (in that order) and store the data via a COSMOS isolation API layer. Storage can in fact initially be in the existing TPTP EMF models, although clearly this is not the end game for COSMOS. BIRT and web based UI can access this data via a new COSMOS api, thus maintaining storage system isolation and driving the COSMOS architectural intent.

One key part of COSMOS is to be able to observe the "Data Center" and initially via user interaction select nodes in the system for observation. In TPTP this would be done by acting on the "hierarchy" model which captures a group of machines with processes and data collectors on them. In this prototype the hierarchy model could be replaced by a data center model that eventually would be SML based. Initially this could simply be reuse of the SML-IF sample we have seen.

This prototype would let COSMOS quickly string together all of it's sub-components along with TPTP use cases and begin to show it's unique value add as well as places for collaboration with TPTP etc.. Once this proof of concept is working each of the architectural areas of COSMOS Can begin to evolve in parallel.

In order to protect the user community COSMOS would not provide any "API" in Eclipse terms at this time, in order that everything can be replaced as needed going forward.

A few iterations of this prototype could be demo ready by EclipseCon time frame.

Back to the top