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.
Difference between revisions of "COSMOS Reconciliation Taxonomy"
(→Terminologies/Acronyms) |
m |
||
Line 1: | Line 1: | ||
= Reconciliation Taxonomy = | = Reconciliation Taxonomy = | ||
− | + | The reconciliation taxonomy defines a basic set of resource types and the properties typically used to identify instances of each resource type. The purpose of the taxonomy is to describe enough information about a resource (e.g., a computer system) to determine whether two management data repositories have data about the same resource, even given that each repository uses a different data model. For example, some identifying properties about a computer system are manufacturer, model, serial number, system board UUID, and primary MAC address. Such a taxonomy could be used in different contexts, including implementations of the CMDB Federation specification and launch in context scenarios. | |
+ | |||
+ | The use of a reconciliation taxonomy is a compromise between trying to get the entire IT industry to adopt a single data model (considered to be impractical) and defining no common data at all, which would require a bespoke model mapping for each pairwise integration of management data repositories. | ||
=== '''Change History''' === | === '''Change History''' === |
Revision as of 16:23, 7 November 2008
Contents
Reconciliation Taxonomy
The reconciliation taxonomy defines a basic set of resource types and the properties typically used to identify instances of each resource type. The purpose of the taxonomy is to describe enough information about a resource (e.g., a computer system) to determine whether two management data repositories have data about the same resource, even given that each repository uses a different data model. For example, some identifying properties about a computer system are manufacturer, model, serial number, system board UUID, and primary MAC address. Such a taxonomy could be used in different contexts, including implementations of the CMDB Federation specification and launch in context scenarios.
The use of a reconciliation taxonomy is a compromise between trying to get the entire IT industry to adopt a single data model (considered to be impractical) and defining no common data at all, which would require a bespoke model mapping for each pairwise integration of management data repositories.
Change History
Name: | Date: | Revised Sections: |
---|---|---|
Mark Johnson | 11/7/2008 |
|
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: note to MJ: change this however you like, I included as an example
Term | Definition |
---|---|
MDR | management data repository |
CMDBf | CMDB Federated is a specification for a CMDB that federates between multiple MDRs |
federating CMDB | the CMDB that federates between MDRs, offering a common access point to clients and correlating identifying record data |
CMDB | configuration management database |
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. |
Purpose
Development Process
to MJ: I can fill in some of this if you like since I can include the parts that are fixed due to the Eclipse process
I can also provide info as to where to find it in CVS