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.
COSMOS Design 214903
Contents
Provide a mechanism for testing the registration service and client
This is the design for Bugzilla 214903.
Change History
| Name: | Date: | Revised Sections: |
|---|---|---|
| David Whiteman | 1/21/2008 |
|
Workload Estimation
| Process | Sizing | Names of people doing the work |
|---|---|---|
| Design | 0.5 week | Ali Mehregani |
| Code | 1.5 weeks | Ali Mehregani |
| Test | 0 | Ali Mehregani/QA team |
| Documentation | 0 | N/A |
| Build and infrastructure | 0 | N/A |
| Code review, etc.* | 0 | N/A |
| TOTAL | 2 weeks |
'* - 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
A mechanism is needed to test functionalities that require the presence of a federating CMDB. The purpose of this enhancement is to create a simple version of a federating CMDB that can be used for testing some functionalities. This will only be included in the example module and won't appear as part of COSMOS' code base.
Implementation details
fill in impl details here
Test Coverage
list test cases here.
Open Issues
This task is still being scoped.