Difference between revisions of "COSMOS Use Cases"

Revision as of 14:40, 7 December 2007

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.

The emphasis of this page is for us to focus on the value delivered to the community by COSMOS.

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

• Use case actors
• End-to-End use cases (out of date-->needs to be updated)

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

(led by Jimmy M.)

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
   
2. After a service implementation, an adopter can register the data store with COSMOS data broker.
   Enhancements: 197867, 192493
   User Documentation: COSMOS Programming Model
   
3. 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: Submitting a CMDBf query to an MDR

This use case should elaborate on adopter's ability to associate customized visualization to specific query response (see 208603)
Enhancements:

Collection

(led by Ali & Hubert)

Related components/technologies/standards:

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

Use Case: Client subscription to events

Description: This use case elaborates COSMOS efforts around WS-Notification. There will be a notification broker provided in COSMOS where notification producers and consumers can publish or subscribe to events in the context of web services.

1. Client contacts the management domain
2. Client queries for the notification broker associated with the management domain
3. Using the end point reference of the notification broker, the client queries for topics published by notification producers
4. Client subscribes to one or more published topic. Subscribing to a topic will cause a notification every time an event associated with the topic is raised.

Enhancements: 197868,

Use Case: Registration of proprietary data stores with operational data

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

Enhancements:

Use Case: Report generation on incidents

Enhancements:

Use Case: Log or performance data collection and report generation

Enhancements:

Use Case: Generation and consumption of internal COSMOS errors

Enhancements:

Use Case: Use of notification events in a CMDBf environment

Enhancements:

Management

(led by Bill)

Note: There should at least be one use case for each one of the topics below:
* Security enhancements planned for i8
* Any SDD work planned for i8/i9
* SNMP work planned for i8/i9
* Management of data managers via WSDM

Related components/technologies/standards:

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

Use Cases:

• Resource Modeling use cases
• Build to Manage use cases (Needs to be cleaned up)
• Plug and Manage (needs to be updated to reflect WSDM notification receipt and updating MDR)

Use Case: Associate an MDR with a Federating CMDB

Enhancements:

Use Case: Broadcasting MDR query/registration capabilities via service metadata

Enhancements: