[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cosmos-dev] Oliver Action Item - Elevator Pitch
|
+1
Chris Craddock
SVP, Principal Technology Strategist
Office of the CTO
Cell 281-770-1950
> -----Original Message-----
> From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Ebright, Don
> Sent: Monday, March 19, 2007 12:12 PM
> To: Cosmos Dev
> Cc: Judy Schramm
> Subject: RE: [cosmos-dev] Oliver Action Item - Elevator Pitch
>
> Oliver,
>
> 2PM Wednesday (half hour before the architecture call) works for me.
>
> Don
>
> -----Original Message-----
> From: cosmos-dev-bounces@xxxxxxxxxxx
> [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Oliver E Cole
> Sent: Monday, March 19, 2007 1:03 PM
> To: Cosmos Dev
> Cc: Judy Schramm
> Subject: Re: [cosmos-dev] Oliver Action Item - Elevator Pitch
>
> So far, it looks like Wed Mar 21 at 2PM EDT. Chris? Don?
>
> This is an excellent start. Thanks. We still have to distill into
an
>
> elevator speech and I will drive towards that in the conference call.
I
>
> notice how you cleverly avoided the subject of an elevator pitch by
> saying "and a roadmap toward the remaining work" ;)
>
> Excellent go at the slides other than your cowardly ducking of that
> one subject.
>
> In the following, I sound certain because it is faster to make
> progress for the elevator pitch. Feel free to take constructive
> objection to any particular statement either privately or to the
mailing
>
> list. This discussion will continue on the phone call.......
>
> 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.....
>
> 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.
>
> 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....
>
> 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.
>
> ??
>
> 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
