Difference between revisions of "Leveraging CMDBf"

From Eclipsepedia

Jump to: navigation, search
(Basic Use Case)
(Requirements)
Line 21: Line 21:
 
* Query
 
* Query
 
* Registration
 
* Registration
 +
** How do we reconcile the registration of MDRs vs. the item relationship
 
* Data Broker [https://bugs.eclipse.org/bugs/show_bug.cgi?id=197867 197867: Need to design and implement the COSMOS DC Data Broker for i6]
 
* Data Broker [https://bugs.eclipse.org/bugs/show_bug.cgi?id=197867 197867: Need to design and implement the COSMOS DC Data Broker for i6]
 
* WS-RC [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198553 198553: Provide an implementatin of WS Resource Catalog]
 
* WS-RC [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198553 198553: Provide an implementatin of WS Resource Catalog]

Revision as of 14:57, 8 August 2007

This page is the beginning of where we can begin our discussions on the CMDBf specification.

Contents

Specification

The CMDBf specification can be found here: http://cmdbf.org/


Overview

The COSMOS project intends to produce a reference implementation of a CMDBf Management Data Repository (MDR). The project will demonstrate how a client can use multiple MDRs through the CMDBf query interfaces and registration services to display information from multiple management systems. COSMOS will also create any additional infrastructure required to support the basic use case.

Basic Use Case

The image below is an overview of the most basic use case. Cosmos-cmdbf-overview.gif

  • Correct the picture: In the service broker, they both should be CMDBfQuery
  • Add Management Domain to picture... maybe another use case for bootstrapping

Requirements

These are the high level requirements necessary to complete the implementation of CMDBf. We will break these down into bugzilla enhancement requests.

(Needs to be expanded on during the call... this is just a start....)