Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> GSOC Idea - Accumulo Control Panel


Copy link to this message
-
Re: GSOC Idea - Accumulo Control Panel
On Apr 12, 2013 2:25 PM, "Andres Danter" <[EMAIL PROTECTED]> 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.

Andres, I would be happy to help mentor you on that project if that's what
you'd like to work on. I am also an Ambari committer. Below is the
information I have on adding components to Ambari. If this interests you,
let me know and I will run the project by the Ambari PMC.

"To add a component to Ambari, one would do the following:
* Add the component as part of the stack definition (see
https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/stacks/HDP/1.2.0/services
)
* Write Puppet scripts for installing, starting, and testing the component
(see
https://github.com/apache/ambari/tree/trunk/ambari-agent/src/main/puppet/modules
)
* Create an RPM for the component
* Make the RPM is available via yum (or zypper) on the cluster hosts.

Unfortunately we don't have any documentation on this yet."

Billie

>
>
>
> On Fri, Apr 12, 2013 at 11:47 AM, David Medinets
> <[EMAIL PROTECTED]>wrote:
>
> > Thanks for the reminder. I had forgotten the name of Ambari.
> >
> >
> > On Fri, Apr 12, 2013 at 10:37 AM, Keith Turner <[EMAIL PROTECTED]> wrote:
> >
> > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > <[EMAIL PROTECTED]> 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
> > >
> >
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB