Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS Design 215267"

(Implementation details)
(''' Terminologies/Acronyms''')
Line 69: Line 69:
 
|-
 
|-
 
|CMDBf
 
|CMDBf
|specification for a CMDB that federates between multiple MDRs[http://cmdbf.org/CMDBf-v0.95.pdf]  
+
|specification for a CMDB that federates between multiple MDRs [http://cmdbf.org/schema/1-0-0/CMDBf%20v1.0.pdf]  
 
|-
 
|-
 
|federating CMDB
 
|federating CMDB

Revision as of 11:17, 21 January 2008

Provide support for adding a federating CMDB to COSMOS framework

This is the design for Bugzilla 215267.

Change History

Name: Date: Revised Sections:
David Whiteman 1/18/2008
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design 1 week Ali Mehregani
Code 2 weeks Ali Mehregani
Test 1 week Ali Mehregani/QA team
Documentation 3 days Ali Mehregani
Build and infrastructure 0 N/A
Code review, etc.* 0 N/A
TOTAL 4 weeks and 3 days

'* - includes other committer work (e.g. check-in, contribution tracking)

Terminologies/Acronyms

The terminologies/acronyms below are commonly used throughout this document. The list below defines each term regarding how it is used in this document:


Term Definition
MDR management data repository
CMDBf specification for a CMDB that federates between multiple MDRs [1]
federating CMDB the CMDB that federates between MDRs, offering a common access point to clients and correlating identifying record data
CMDB configuration management database

Purpose

We needs to add support for adopters intending to register a federating CMDB with COSMOS framework. This enhancement will include reusable code for adopters intending to provide a server/client side implementation of a federating CMDB.

Implementation details

There is already code in place for adopters to use when implementing an MDR. The following MDR plug-ins will be extended to provide support for a federating CMDB:

org.eclipse.cosmos.dc.mdr
org.eclipse.cosmos.dc.mdr.client
org.eclipse.cosmos.dc.mdr.common

Three additional plug-ins will be introduced, each of which will be an extension of its MDR counterpart:

org.eclipse.cosmos.dc.federating.cmdb
org.eclipse.cosmos.dc.federating.cmdb.client
org.eclipse.cosmos.dc.federating.cmdb.common

On server side two operations will be introduced:

  • Register
  • Deregister

On client side few variations of registration. All variations will also apply to deregistration:

  • Registration based on a request
  • Registration of all items/relationships of a set of MDRs
  • Selective registration based on a CMDBf query on a set of MDRs

Test Coverage

list test cases here.

Open Issues

This task is still being scoped.


Back to the top