Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "COSMOS Design 215267"

(''' Provide reusable modules for consumers intending to provide a registration client ''')
(''' Workload Estimation''')
Line 25: Line 25:
 
|-
 
|-
 
| align="left" | Design
 
| align="left" | Design
| unknown
+
| 1 week
 
| Ali Mehregani
 
| Ali Mehregani
 
|-
 
|-
 
| align="left" | Code
 
| align="left" | Code
| unknown
+
| 2 weeks
 
| Ali Mehregani
 
| Ali Mehregani
 
|-
 
|-
 
| align="left" | Test
 
| align="left" | Test
| unknown
+
| 1 week
| TBA
+
| Ali Mehregani/QA team
 
|-
 
|-
 
| align="left" | Documentation
 
| align="left" | Documentation
| unknown
+
| 3 days
| TBA
+
| Ali Mehregani
 
|-
 
|-
 
| align="left" | Build and infrastructure
 
| align="left" | Build and infrastructure
| unknown
+
| 0
| TBA
+
| N/A
 
|-
 
|-
 
| align="left" | Code review, etc.*
 
| align="left" | Code review, etc.*
| unknown
+
| 0
| TBA
+
| N/A
 
|-
 
|-
 
! align="right" | TOTAL
 
! align="right" | TOTAL
| unknown
+
| 4 weeks and 3 days
| TBA
+
|  
 
|}
 
|}
  

Revision as of 19:04, 18 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


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.


Back to the top