Skip to main content
Jump to: navigation, search

Cosmos Architecture Meeting 13-Dec-07

Revision as of 13:37, 13 December 2007 by (Talk | contribs) (Proposed Course of Action)


  • Valentina Popescu
  • Jack Devine
  • Martin Simmonds
  • John Todd
  • Paul Stratton
  • Hubert Leung
  • David Whiteman
  • Bill Muldoon
  • Ali Mehregani
  • Sheldon Lee-Loy
  • Don Ebright
  • Joel Hawkins


Notes on Error Discussion

OK... We've opened a bunch of ERs with "Error" type stuff in them. I've tried to compile the complete list below.

209227: Common Error Management System for COSMOS see also: COSMOS Design 209227

209234: Error management for the contract between the UI and DataCollection see also: COSMOS Design 209234

209242: Error Management for MDR interface to SML repository

208592: Error Handling - improve programming model

209223: Error Handling - client side

209224: Error Management for DataCollection Framework

Proposed Course of Action

First, I'd like to check in the code that is attached to [209227]. This introduces the common COSMOS exception. We can, over the course of i8 & i9, refactor to have all of our exceptions extend this one. --> +1

Second, I propose that [208592] be marked as a duplicate of [209227].

Third, I propose that [209242] be scoped to the following:

  1. The error contract between the MDR and the outside world, from a Java perspective, will be extensions of COSMOSExceptions
  2. The CMDBf specification v1.0 defines faults. These should be mapped into a set of COSMOS exceptions

Once this mapping is defined, this ER can be closed.

Sheldon and team have prepared a design document on [209234]. I propose that we review this and close the ER prior to the architecture call on 20-Dec-07 via e-mail on COSMOS-dev.

I'd propose that we review and close the forthcoming design of [209223 prior to the architecture call on 20-Dec-07 via e-mail on COSMOS-dev.

Errors vs. Logging....

There was some discussion/confusion that COSMOS Design 209227 was or was not going to cover our logging strategy. In prep for this discussion, I went back over some of my notes and trolled around on the wiki to try and assemble where I think we are. The net is, we wanted to keep the logging strategy related, but separate from, the error strategy. We established a page to capture our logging requirements COSMOS internal logging use cases. The intent was to use these use cases to open up the necessary ERs.

Looking at this page, we clearly have some work that needs to be done. Given that we are getting to the point where we need to start producing logs, we may want to ensure we get a good cut of this work done in i9.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.