Re: [cosmos-dev] COSMOS / MR 2 architecture presentation

[Mark D Weitzel <weitzelm@xxxxxxxxxx>]

Jimmy,

Here are some thoughts on the slides
you've submitted....

Slides 5 & 15 show the client.  I
think we will need to have a reference implementation of client libraries
as well.  This should be what the data visualization layer uses.
Slide 8: There should be lifecycle events
that the management domain issues, e.g. i've added a new broker, i'm alive,
etc... we need to list those
Slide 9: Assuming the domain is essentially
a service group, how do the classifications align with content rules?

Other general question....

When we talk about the management domain,
we need to define it's WSDM interface, e.g. properties, operations, and
events.  In my head, these three things will make up a "Domain
Capability".  We could start working this into our vocabulary.

Also, there is no real mention of WS-MEX.
 For example, slide 13 talks about metadata queries from the client.
 We should specify that these will be done using MEX, which will give
us the framework for what we are doing.

Also, there is no mention of how the
Data Managers/Data Adapters fit into the query assembly parts of cosmos.
 An example assembly here would be good.

-mw



Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing
| (919) 543 0625 | weitzelm@xxxxxxxxxx

"Mohsin, Jimmy" <Jimmy.Mohsin@xxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

06/26/2007 10:23 AM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	<cosmos-dev@xxxxxxxxxxx>
cc	"Craddock, Chris" <Chris.Craddock@xxxxxx>
Subject	[cosmos-dev] COSMOS / MR 2 architecture presentation

Dear All,
  
1.        Please find
attached a PPT that describes the understanding of the COSMOS AND its relationship
to MR 2; at least as we in the MR 2 team understand it.
2.        Please note
that this is based on the premise that the MR 2 implementation will be
based upon and extend the current COSMOS DC codebase
  
There are a few objectives I wanted to fulfill with this PPT:
1.        The team
at large has a consistent picture of the COSMOS DC architecture (as it
develops further) and the corporate implementation architectures (as THEY
develop further).
2.        Ensure that
we use the SAME terminology / nomenclature going forward.
3.        As we move
forward, continually define the boundary between what will be in the COSMOS
DC and what will be part of the “corporate implementations”
4.        The team
at large has a common understanding
  
To this effect, I would like to solicit your feedback / comments / criticisms
/ corrections / enhancements.
  
Thanks, 
Jimmy Mohsin 
609-635-1703 
 [attachment "COSMOS DC and  MR 2 Architecture.ppt" deleted
by Mark D Weitzel/Raleigh/IBM] _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev