COSMOS

From Eclipsepedia

Jump to: navigation, search

Welcome to COSMOS!


Contents

Overview

Historically, managing systems and applications is an afterthought and generally left to post-test, and sometimes post-deployment. The link between management tools and the applications they manage are usually very weak resulting in management tools that appear at best to be bolted or glued on to the applications and at worst, have little to no application knowledge and merely work with the artifacts of the applications and the systems from which they are built.

Increasingly, these applications are made up of many components, many providing or consuming services to other applications and their components. The relationships amongst these components represent dependencies that are important to properly manage and maintain these complex systems. Systems management tools attempt to monitor and manage these systems, but it is extremely challenging given that many of the underlying assumptions, dependencies, and expectations of the original architects are seldom communicated to or through these tools.

Over the last five years, there have been many advances in areas of application instrumentation for testing, performance analysis, and configuration. Many underlying platforms as well as applications are well instrumented. However, there is still a large knowledge gap between defining points of instrumentation by the developers and the tools that IT specialists use to manage these systems once they have been deployed.

Service Modeling Language (SML) was recently introduced to enable architects, developers, and systems designers to describe complex services. These models typically describe information necessary to enable automation of many of the management tasks that span the lifecycle of the applications and systems that make up a service.

COSMOS is proposing to close the knowledge gap between the development of applications and their management by providing SML-based frameworks and tools within Eclipse. Leveraging work from the build-to-manage workgroups and standard resource models being defined in SML, COSMOS will provide tools for the developers and architects to create models for their applications and services and link them to the instrumentation provided by their application components. COSMOS will also provide working management tools for use by developers and IT management specialists along with a tools framework that consumes these models and underlying instrumentation.


Follow this link to the COSMOS Proposal

This is the link for the COSMOS Newsgroup


Working Sessions

We are working towards the COSMOS Project Creation Review. Look here for more information.

Look at the Minutes of Community Calls for the details of our meetings as well as the upcoming agendas.


Because participation of systems management vendors are a key part of the success of the project, we need to articuate how COSMOS differentiates itself from the commercial offerings. The discussion is here->Commercial Differentiation

Use Cases

During the community call on October 19, we agreed to articulate some high level use cases for COSMOS. We broke those down by each of the topical areas of the project.


Proposed Working Session 4-Dec-06 A F2F was held on December 4, 2006. Click here for more minutes.

Architecture

Here is a start at the high level architecture for COSMOS.

Each of the major components has a wiki area at the following links:

- Data Reporting

- Data Collection and Normalization

- Build to manage

- Resource Modeling


To better understand and comment on how COSMOS relates to other projects look here Project Relationships

Additional Resources

Look here for information on how COSMOS relates to other projects.

Look here for the topics/presentations/etc... for Eclipse Con

Here are some FAQs about COSMOS.

The Glossary is here.