Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of adanter@gmail.com designates
 209.85.210.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOiJXP7f3UjzUyfBW_=HL3inB8ZOx4Rt3jiLd75k3i2Wust6hQ@mail.gmail.com>
References: 
 <CAOiJXP6hq_9myu334XRtHh9mDb7j0dXopiO8-zN4xkH=1dY7aA@mail.gmail.com>
	<CAGUtCHq62y3mQHOrHC0Ob+2mkmxxw-6w=QTW4tgpnww7qg--oQ@mail.gmail.com>
	<CAOiJXP4cE7j9=Xz2k1NdrCChXM2b0-ex+Hj_HDBeLEX3WmnvYw@mail.gmail.com>
	<CAH-KK43e4TK-u15N5qX3Zccy=9nggna_dqTF-fC4=VQUUGa2mA@mail.gmail.com>
	<CAOiJXP7f3UjzUyfBW_=HL3inB8ZOx4Rt3jiLd75k3i2Wust6hQ@mail.gmail.com>
Date: Fri, 12 Apr 2013 17:58:30 -0400
Message-ID: 
 <CAH-KK42zXz8W_zXj0UbQOpCRZxx72QMNESTv-+aL3j4wrf6bmw@mail.gmail.com>
Subject: Re: GSOC Idea - Accumulo Control Panel
From: Andres Danter <adanter@gmail.com>
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=bcaec5186778ee3f4704da3100ba

--bcaec5186778ee3f4704da3100ba
Content-Type: text/plain; charset=ISO-8859-1

Thanks, Billie.  I'm liking this task more and more.  I would love to take
this on for GSoC.  Please run it by the Ambari PMC.  I will start drafting
the proposal this weekend.

Just to be clear, the goal would be to integrate Ambari with Accumulo in
order to achieve the following capabilities (I've expanded David's original
list of features):

1. Control (start/stop) Accumulo processes on any cluster node
2. Have the ability to edit Accumulo configuration files via a web-based
editor (I don't think Ambari provides this.  Please let me know if I'm
wrong)
3. Have the ability to schedule restart of Accumulo processes after a
configuration change
4. Push Accumulo code and configuration files to a new cluster node
5.  Gracefully remove a node from a cluster
6.  Gather system and/or application metrics that can be used to monitor
the system and perhaps create reports on usability
7.  Be able to monitor and control the Accumulo cluster from a web-based
GUI  (this kind of goes with #2 above)
8.  Allow read-only monitor sessions, as well as full-admin sessions and
have the ability to strictly manage who can access either.  (this I got
from ACCUMULO-196)
9.  Provide the ability to authenticate user sessions with SSL
(see ACCUMULO-196)

It seems like the product of this work would largely replace the current
Accumulo Monitor.  If that is the case, are there features of the monitor
which you would like to see integrated?

I will have about 3 months to complete this work (actually about 220-240
hours), so that list is doable.  Most of the work will involve the GUI
portions, unless Ambari already comes with much of the functionality.  If
the list is too short, please let me know.

I guess I should sign up to the Ambari mailing list as well, right?

Thanks again and I look forward to being your mentee and to working with
the Accumulo community.

Andres


On Fri, Apr 12, 2013 at 3:43 PM, David Medinets <david.medinets@gmail.com>wrote:

> The project is open source ... we can't stop you!
>
>
> On Fri, Apr 12, 2013 at 2:25 PM, Andres Danter <adanter@gmail.com> wrote:
>
> > Could the work of integrating Accumulo with Ambari be something that you
> > would allow a student to tackle for GSoC?  I don't want to step on
> anyone's
> > planned work, but such a task really interests me.  I want to tackle
> > something with some meat, if you know what I mean.
> >
> >
> >
> > On Fri, Apr 12, 2013 at 11:47 AM, David Medinets
> > <david.medinets@gmail.com>wrote:
> >
> > > Thanks for the reminder. I had forgotten the name of Ambari.
> > >
> > >
> > > On Fri, Apr 12, 2013 at 10:37 AM, Keith Turner <keith@deenlo.com>
> wrote:
> > >
> > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > > <david.medinets@gmail.com> wrote:
> > > > > It might be interesting to have a tool which could:
> > > > >
> > > > > a) shut down any accumulo process on any server.
> > > > > b) start any accumulo process on any server.
> > > > > c) edit the various configuration files through a web interface.
> > > > > d) automate restart accumulo processes, as needed, after
> > configuration
> > > > > change.
> > > > > e) push accumulo code and configuration to a new server.
> > > > > f) gracefully shutdown and remove a server from the cluster.
> > > > >
> > > > > Anything else? If this sounds like a good idea, let's create a JIRA
> > > > ticket
> > > > > with the right tags.
> > > >
> > > > This sounds like Apache Ambari, which we should possibly integrate
> > > > with. See ACCUMULO-136
> > > >
> > >
> >
>

--bcaec5186778ee3f4704da3100ba--