Jump to: navigation, search

Difference between revisions of "Cosmos Architecture Meeting 13-Dec-07"

(Notes on Error Discussion)
 
(5 intermediate revisions by the same user not shown)
Line 14: Line 14:
  
 
== Minutes ==
 
== Minutes ==
*
 
  
 
+
=== Notes on Error Discussion ===
== 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.   
 
OK... We've opened a bunch of ERs with "Error" type stuff in them.  I've tried to compile the complete list below.   
Line 44: Line 42:
 
208592: Error Handling - improve programming model
 
208592: Error Handling - improve programming model
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592
 +
 +
This is really error handling for the server components that drive the UI.
  
  
Line 52: Line 52:
 
=== Proposed Course of Action ===
 
=== Proposed Course of Action ===
 
First, I'd like to check in the code that is attached to [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209227 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.  
 
First, I'd like to check in the code that is attached to [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209227 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  
 
--> +1  
  
  
Second, I propose that [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592 208592]] be marked as a duplicate of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209227 209227]].  [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592 208592]] also overlaps with [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209223 209223]].
+
Second:
 +
Close 242 and 234 as dupes of 224.
  
 +
--> +1
  
Third, I propose that [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209242 209242]] be scoped to the following:
 
# The error contract between the MDR and the outside world, from a Java perspective, will be extensions of COSMOSExceptions
 
# 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.
+
Third, Sheldon and team have prepared a design document on [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209234 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 [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209223 209223] 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
 +
[[https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592 208592]] prior to the architecture call on 20-Dec-07 via e-mail on COSMOS-dev.
 +
 +
--> +1
  
  
Sheldon and team have prepared a design document on [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209234 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 [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209223 209223] prior to the architecture call on 20-Dec-07 via e-mail on COSMOS-dev.
 
  
  
227 (overall guidelines)
 
  
--> 224 (DC)
 
  
 +
----
  
 
=== Errors vs. Logging.... ===
 
=== Errors vs. Logging.... ===

Latest revision as of 10:03, 20 December 2007

Attendees

  • 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

Minutes

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 https://bugs.eclipse.org/bugs/show_bug.cgi?id=209227 see also: COSMOS Design 209227


209224: Error Management for DataCollection Framework https://bugs.eclipse.org/bugs/show_bug.cgi?id=209224


209242: Error Management for MDR interface to SML repository https://bugs.eclipse.org/bugs/show_bug.cgi?id=209242

(close 209242 and make part of 224)


209234: Error management for the contract between the UI and DataCollection https://bugs.eclipse.org/bugs/show_bug.cgi?id=209234 see also: COSMOS Design 209234

(close 209234 and make part of 224, UI part of 223)


208592: Error Handling - improve programming model https://bugs.eclipse.org/bugs/show_bug.cgi?id=208592

This is really error handling for the server components that drive the UI.


209223: Error Handling - client side https://bugs.eclipse.org/bugs/show_bug.cgi?id=209223


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: Close 242 and 234 as dupes of 224.

--> +1


Third, 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.

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

--> +1





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.