From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Mark D Weitzel
Sent: Monday, August 06, 2007
10:54 AM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] Management
Enablement
Joel, et al
I
was working on the following enhancement....
183377:
Complete Part 1, Project Overview of Management Enablement: https://bugs.eclipse.org/bugs/show_bug.cgi?id=183377
In
my head, management enablement is about components that make things able to be
managed. In the case of WSDM enablement, this would be any adapters that
we build to have resources expose WSDM interfaces. In general, we'd have
a well defined management API, then we'd "wrap" that with WSDM.
So
this got me thinking about....
195292:
Support for native MUSE (WSDM) managed components: https://bugs.eclipse.org/bugs/show_bug.cgi?id=195292
This
enhancement was to provide the Muse interface classes for the WSDM
capabilities. This seems like the work we do here should really be in the
management enablement component b/c these would be the "wrappers" for
the management APIs that the DC components expose. This thought led me to
thinking about the management annotation work that we have already in
org.eclipse.cosmos.management.wsdm. It seems this should really be under
ME. Perhaps when we move the WSDM tooling in, we should refactor this as
well.
What
do you think?
-mw
Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing | (919)
543 0625 | weitzelm@xxxxxxxxxx