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

COSMOS Use Cases

Revision as of 10:30, 7 December 2007 by David whiteman.us.ibm.com (Talk | contribs) (Use Case: Registering an MDR with the COSMOS framework)

COSMOS Project Home > COSMOS Wiki > COSMOS Documents >

Overview

The purpose of this page is to articulate the function that COSMOS will provide. While enhancement requests are typically created, they tend to be very fine grained or very macro. We intend to use this page to describe from the user's point of view how they can interact with COSMOS.


This page as a way to capture the high level function offered by the COSMOS framework.


We would like to be able to tie back the work we are doing to a specific use case. Therefore, we will add a link to the Use Case as a comment in the enhancement request.

This has been recorded in the COSMOS Development Process

COSMOS Supported Use Cases for M2


The existing links are, in many cases quite old. Now that we have a tangible release plan, the purpose of this page is to:

  1. Consolidate all the existing links related to use cases onto a single page
  2. Sunset all of the old wiki pages
  3. Consolidate the use case information for M2 onto this page
  4. Associate enhancement requests with Use Cases. Note: It may be difficult to retroactively add the enhancements to the use cases. However, as we open new enhancements, we should map them back to a use case in this document
  5. Provide a blueprint for the system verification tests


These use cases typically span more than one COSMOS component. Therefore, we've come up with three "categories".

Federation

Related components/technologies/standards:

  • CMDBf
  • MDR

The following document outlines COSMOS commitment to the CMDBf standard: Leveraging CMDBf


Use Case: Registering an MDR with the COSMOS framework

Description: This use case describes the ability of adopters to register an internal data store as an MDR. The use case will elaborate COSMOS capabilities that will make registration, service implementation, and discovery of the MDR easier.

  1. An MDR can choose to provide an implementation of a CMDBf query service. COSMOS helps adopters by providing common libraries that makes service implementation easier
    Enhancements: 200222, 204959, 208584

User Documentation: Providing_a_CMDBf_Query_and_Registration_Service

  1. After a service implementation, an adopter can register the data store with COSMOS data broker.
    Enhancements: 197867, 192493
  2. Adopters can choose to provide customized visualizations/reports or use existing COSMOS views.
    Enhancements: 206771, 208603, 208595, 211093

Use Case: Registration of Federating CMDB

Enhancements:


Use Case: The actor queries for the complete list of MDRs

Actor: System Admin,

Enhancements:


Use Case:

Enhancements:


Collection

Related components/technologies/standards:

  • Integration with Application Logs (Based on existing work)
  • Performance Data
  • Event Consuming, WS-N, (WEF)

Use Cases:



Use Case: The user establishes a subscription to an event

Enhancements:


Use Case: The user registers a data store with operational data with COSMOS

Note: need to make sure we classify this in the proper category--question is around this b/c it's not an MDR

Enhancements:


Management

Related components/technologies/standards:

  • CMDBf Administration
  • SNMP (MIB2RDML??)
  • WSDM Tooling
  • WSDM Annotations
  • SDD
  • SML

Use Cases:


Use Case: Associate an MDR with a Federating CMDB

Enhancements:


Back to the top