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 Design 200222

Revision as of 13:16, 22 August 2007 by David whiteman.us.ibm.com (Talk | contribs) (''' Terminologies/Acronyms (required)''')

Adding support for the CMDBf query service on top of the SML repository

Change History:

Name: Date: Revised Sections:
David Whiteman 8/21/2007 Initial version

Overview

In order to act as an MDR per the CMDBf spec, the SML repository needs to support the CMDBf query service. This enhancement is tracked as bugzilla 200222.

Workload Estimation (required)

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design 1 David/Ali
Code 2
Test 1
Documentation 0.4
Build and infrastructure 0.2
Code review, etc.* 0.2
TOTAL 4.8
  • - includes other committer work (e.g. check-in, contribution tracking)

Terminologies/Acronyms (required)

The terminologies/acronyms below are commonly used throughout this document. The list below defines each term:

Term Definition
MDR management data repository
CMDBf federating CMDB
CMDB configuration management database
SML Repository repository of SML documents hosted in COSMOS with an established API (see bugzilla 179828)
Query service MDRs make data available to Clients via a Query service. Queries may select and return items, relationships, and/or graphs containing items and relationships.[1]

Stuff to do

Purpose (required)

This design document addresses COSMOS Bugzilla enhancement request 200222.

Requirements (required)

Use Cases (required)

Graphical Layout (optional)

Class Diagram and Implementation Details

Class Diagrams (optional)

<This section is only required for features that are introducing APIs that will be leveraged by other components>

Extension Points (optional)

<This section should only be included if new extension points are being introduced>


<Include any additional topics that will help in completing the implementation>

<Content related to the topic above>

Test Coverage (required)

<Include a description of the unit, functional, and system test cases that will be required to test the overall quality of the feature>

Task Breakdown (required)

Open Issues/Questions


Back to the top