Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <f80a104a0910050117j337ba24duc301bb39009a8b4d@mail.gmail.com>
References: <C6EBF2BA.4881%eyang@yahoo-inc.com>
	 <c9118d4c0910041459j5735e1d8n5925cd7177728296@mail.gmail.com>
	 <f80a104a0910050117j337ba24duc301bb39009a8b4d@mail.gmail.com>
Date: Mon, 5 Oct 2009 06:12:52 -0700
Message-ID: <c9118d4c0910050612i3966485fh24de4fb7c6a3f8fe@mail.gmail.com>
Subject: Re: Cloudera Desktop
From: Jeff Hammerbacher <hammer@cloudera.com>
To: chukwa-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=00c09f90580d86545104752fdf98

--00c09f90580d86545104752fdf98
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Jiaqi,
Thanks for the questions. In the future, could you please use
http://tiny.cloudera.com/desktop-feedback for questions about the product?
Anyways, here are the answers:

On Mon, Oct 5, 2009 at 1:17 AM, Jiaqi Tan <tanjiaqi@gmail.com> wrote:

> Hi Jeff,
>
> Two questions:
>
> 1. Are there plans to open-source, or provide an API, to Cloudera Desktop=
?
>

The window manager and several other Javascript components are already open
source through MooTools More; see http://github.com/anutron/art, for
example. The Cloudera Desktop basic framework will not be open source. Ther=
e
is a rough API right now that we're polishing up for some early alpha
testers. If you'd be interested in developing on Cloudera Desktop, drop a
line to desktop-api-subscribe@cloudera.com, and we'll be in touch some time
in the next few months.


>
> 2. Will the Job Designer plug into Oozie/does it already do that right no=
w?
>

The version of Oozie available in the public domain does not work for us
after several weeks of tinkering. We have many customers running complex
workflows using similar tools already, and whatever solution we provide in
this domain we hope to make work with Oozie as well.

Thanks,
Jeff


>
> Jiaqi
>
> On Mon, Oct 5, 2009 at 5:59 AM, Jeff Hammerbacher <hammer@cloudera.com>
> wrote:
> > Hey Eric,
> > Thanks for the feedback! At Cloudera, we use Get Satisfaction for
> customer
> > comments; in the future, we'd love to have you post to
> > http://getsatisfaction.com/cloudera/products/cloudera_cloudera_desktopw=
ith
> > your feedback on the product.
> >
> > I agree that large clusters require different visualization techniques
> than
> > small clusters. The Desktop metaphor will allow anyone to build system
> > monitoring applications that target specific scenarios, e.g. very large
> > clusters. The UI design for the Cluster Health dashboard that we shippe=
d
> on
> > Friday is one take on system monitoring and is intended to provide
> increased
> > utility for the vast majority of Hadoop clusters we see in practice,
> which
> > are under 200 nodes.
> >
> > We're certainly looking forward to folks breaking Cloudera Desktop in a=
ll
> > sorts of ways and iterating on the product until we get it right.
> >
> > Regards,
> > Jeff
> >
> > On Fri, Oct 2, 2009 at 6:11 PM, Eric Yang <eyang@yahoo-inc.com> wrote:
> >
> >> This is the Cloudera Desktop demo for the Web based management UI. It =
is
> >> more into tasks oriented functions instead of system monitoring.
> >> >
> >> > http://www.cloudera.com/desktop
> >>
> >> Cloudera Desktop has similar use cases that I envisioned for chukwa.
>  The
> >> only difference is the UI model.  There are many element aren=B9t scal=
able
> in
> >> their model.  For example, the system monitoring are showing as grid o=
f
> >> green and red lights.  It probably won=B9t scale beyond 200 nodes.  Ch=
ukwa
> >> has
> >> visualization and summarization of the system state in heatmap.  Which
> >> provides much more useful visualization for large scale cluster.
>  Something
> >> to think about.
> >>
> >> Regards,
> >> Eric
> >>
> >>
> >
>

--00c09f90580d86545104752fdf98--