[snips]
The June software delivery is a toy monitoring system that people
can
hook up their own data collector, repository and user interface. The
toy is not planned to mature to a usable solution. The charter says
that we can't mature it. Do we accept this or do we want to change
the
charter? Sorry about the word toy and we certainly wouldn't call
it
that in public.....
<mdw>
Good thing we didn't
use
the word "toy" on a public mailing list....
Toy wasn't the right word..... We have been using words like
"example, exemplery, etc and those are murky with respect to whether
the software is intended to be useable. I wanted to be blunt in our
understanding (once we agree on one).
Because we
are still incubating,
we don't have a charter, only a proposal. We put the proposal in place
to provide initial structure and scope to the project. As a community
we will need to ensure that we stick to our guiding principles of
advancing
and leveraging standards, providing exemplar implementations, and
fostering
innovation. COSMOS has always been about more than just
monitoring--which
is why we proposed it as a top level project. This was just the first,
most logical place to start.
Agreed. The question still stands: does the proposal stand, with
it's admonisions to not do stuff that commercial offerings do?
</mdw>
So, it isn't going to be a monitoring solution without some adopter
putting in lot's of effort and noone anticipates an adopter doing that
as far as our headlights go (or do one of you plan on doing that?).
So, the raison d'etre for COSMOS is either
i) some software parts of COSMOS that you all are thinking
of
using, or
ii) the specifications developed during COSMOS.
Craig has been pretty clear that he is interested in where SML/CML
intersects with monitoring and doesn't have specific plans to use any
software. I *think* Chris likes the overall architecture, so can
leverage the expertise in COSMOS for internal product development. I
*think* that Don is kinda the same.
I *think* that IBM is aware that
open source is coming to "monitoring" over time, and wants to
be part of
the "crew" that gets this done, but has no specific plans to
incorporate
any of the results of COSMOS into the IBM product line.
<mdw>
We have stated that
COSMOS
does not intend to create another set of agents. We would like to
add frameworks around existing infrastructure that helps facilitate
integration.
In addition to the integration framework, there are other aspects
that, over time, can be adopted commercially--potentially at a
different
rate and pace. For example, as the set of exemplar reports &
report templates etc., based on standards (e.g. WSDM Operational
Status)
expands, these can be consumed directly by commercial products. As
our thinking of integration and loosely coupled services continues to
be
refined, this should include Web 2.0 gadgets/widgets etc... The key is
that these are driven by/based on standards, and not yet another one
off
representation.
It seems to be obvious that COSMOS is more than just the software
that we deliver. Let's focus on the software that we deliver for a
moment.
No agents (reuse existing ones).
Can we do list of what we think is "re-usable" and which is not?
GroundWork mentioned data collector interface, you mention reports.
I think it is ok to let this lie and just see what is reuseable as
time progresses, but if we did know, that would help focus our efforts.
Onward to non-software deliveries:
You say: "facilitate integration" - integrate what things
together? Different commercial products?
Will COSMOS make new standards? Or just implement existing ones?
</mdw>
OCS has some monitoring initiatives going on that we are trying
to
leverage to a business case, and will take bits and pieces of eclipse
(mostly tptp and cosmos) when (?) we can solidify the business case.
I
am hoping that this solidification occurs in the next couple of
months....
<mdw>
The framework we are
putting
in place should facilitate the incorporation of OCS' monitoring
initiatives.
It would be good to get the operational status report based upon
OCS monitored resources.
Wish me luck. Like I say, our first run at this business case got
stalled because of a massive slip in the customers schedule. We now
have even more glorious plans....
</mdw>
If the above is true, then the major "benefit" for COSMOS
is to
distill industry experience and "best practices" into an actual
executable example/testbed. There are two aspects to this:
i) COSMOS is starting from "scratch" so that compatibility
and reuse
of IBM/CA/Compuware/GroundWork code does not impede doing "the right
thing", and
ii) having participation from many different vendors, many divergent
brains are good.
The purpose of the COSMOS developed software, then, is to
demonstrate a monitoring architecture of the future.
<mdw>
....provide a framework
that
demonstrate the value and benefits of a standards based SOA management
infrastructure
Can we list the standards?
</mdw>
??
Chris, Don, can you make the call on the 21st?
--oec
Craig Thomas wrote:
> Hi Oliver,
>
> Thanks for pulling this together.
>
> With regard to meeting logistics, here are my preferences:
>
> 1. Mon, 19-Mar, 2pm EDT/11am PDT
> 2. Wed, 21-Mar, 2pm EDT/11am PDT
> 3. Wed, 21-Mar, 4pm EDT/1pm PDT
>
> Here's a start at the elevator pitch requirements from my end...
>
> As a constituent of the users of the June delivery of COSMOS, here
is
> what I would like to be able to present to the executives here at
> GroundWork (in no particular order):
>
> * Explanation of the state of implementation in June,
and a roadmap
> toward the remaining work.
> * Overview of the Eclipse COSMOS community, including
an
> understanding of the level of resource commitment
from the
> participants.
> * Status of SML and CML standards, including an understanding
of
the
> ways (in addition to Eclipse COSMOS) that these
standards are
> being adopted.
> * Adopter's guide for the June release. This would include
just
> enough documentation to allow GroundWork to estimate
the work
> needed to integrate a new data collector, a new
repository, and a
> simplistic user interface.
>
> With this information, I could inform the executive team of
progress,
> let them understand how other companies in the community have
> supported the work, and propose continued or increased commitment
to
> the community.
>
> The first bullet, the "state of implementation", could be
served by
> pictures, one with some boxes grayed out to indicate work beyond
June,
> and one or more showing the gray boxes gaining color over
subsequent
> release points.
>
> That last bullet, the "Adopter's guide", would just be a
set of
> references to the documentation we are already planning for the
> components in the release. I'm not picturing anything extensive or
> fancy here.
>
> Hope that's the kind of thing you were looking for. If not, please
let
> me know.
>
> Thanks,
> Craig.
>
> _______________________________________________
> cosmos-dev mailing list
> cosmos-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cosmos-dev
>
--
--
--------------------------------------------------------------------
Oliver E Cole
oec@xxxxxxxxxxxxx
OC Systems
www.ocsystems.com
9990 Lee Hwy, Suite 270
(v) 703.359.8160 x160
Fairfax, VA, 22030
(f) 703.359.8161
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it.
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
--
--
--------------------------------------------------------------------
Oliver E Cole oec@xxxxxxxxxxxxx
OC Systems www.ocsystems.com
9990 Lee Hwy, Suite 270 (v) 703.359.8160 x160
Fairfax, VA, 22030 (f) 703.359.8161
|
