This page is the beginning of where we can begin our discussions on the CMDBf specification.
The CMDBf specification can be found here: http://cmdbf.org/
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
- Correct the picture: In the service broker, they both should be CMDBfQuery
- Add Management Domain to picture... maybe another use case for bootstrapping
- Need sequence diagram for use case
- Add a line from the client directly to the MDRs. This is the use case where we want to bypass the federated database.
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....)
- Implement the CMDBf as a Muse capability. Bind to the CMDBf API
- Start on Binding to Ali's API
- Map CMDBf query to convenience APIs for SML repo, Stat repo, and CBE repo (this is the data set issues)
- How do we reconcile the registration of MDRs vs. the item relationship
- Do we need registration in the first round? Start with a focus on Query.
- Data Broker 197867: Need to design and implement the COSMOS DC Data Broker for i6
- WS-RC 198553: Provide an implementatin of WS Resource Catalog
- Client updates 197870: Need to design and implement the COSMOS DC client APIs
- UI work for sheldon
- Need to make sure that the IDs line up or that we have only simplistic means of aligning the different resources
- This gets into a bit of the taxonomies. May need simplistic mappings.
- MDRs look like Data Managers
- DataBroker/ProviderRegistry as MDR
Based on a discussion of the proposed DataBroker design, it appears that what is desired is a combination of an EPR registry for locating DataManagers and a repository of existing data sets that can be processed by those DataManagers. From the use case described above, it appears that the ProviderRegistry should act as an MDR to surface its knowledge of datasets and there attached metadata. If we are going to adopt the CMDBf query dialect as our lingua franca for communicating topology/metadata type information, then it makes sense to apply the CMDBf query capability to both the topology repository and the SDMX-style dataset/keyset repository of the ProviderRegistry.
The Data Broker is intended to be a simple component.
* Clarification of Registration v. Query (Push vs. Pull). * MDR Negotiation: The handshake b/t the MDR and the Broker in order to facilitate Pull