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.
COSMOS Design 215267
Contents
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 |
|
Workload Estimation
| 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
In the presence of a federating CMDB, adopters need to provide a registration client that will register all items/relationships of an MDR with a federating CMDB. Given this is common to all MDRs, it should reside in the data collection as a module that is reusable by COSMOS consumers.
The module can also provide the capability of selective-registering, where only a subset of the items/relationships contained by an MDR is registered with a federating CMDB.
Requirements
list any blocking ERs here.
Implementation details
TBD
Test Coverage
list test cases here.
Open Issues
This task is still being scoped.