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 <[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 > > >
