Billie, I'm a newbie at creating tickets on JIRA. I want to make sure I have the right information for each of the fields:
Project: Ambari Issue Type: Task (or Wish?) Summary: Integrate Ambari with Accumulo Priority: Minor (?) Components: build (?) Affects Versions: <blank> Fix Versions: <blank> Environment: <blank> Description: This task is for Google Summer of Code 2013. The goal is to integrate Ambari with Accumulo to provide a more robust and extensible management layer for Accumulo clusters. The Accumulo tickets related to this Ambari task are the following: ACCUMULO-136 ACCUMULO-196 Original Estimate: <blank> Labels: gsoc2013, Accumulo Is the description enough, or should I add more information? Once I get your blessing, I'll create the ticket. Thanks, Andres On Sun, Apr 14, 2013 at 12:22 AM, Billie Rinaldi <[email protected]>wrote: > On Apr 13, 2013 3:17 PM, "Andres Danter" <[email protected]> wrote: > > > > Hi Billie, > > > > Thanks for passing the information onto the Ambari group. I'm glad that > > they were receptive. I will subscribe to the Ambari dev group later > > today. Do you need me to create the Ambari ticket? > > Yes, that would be great. Thanks, Andres. > > Billie > > > > > Andres > > > > > > On Sat, Apr 13, 2013 at 10:29 AM, Billie Rinaldi > > <[email protected]>wrote: > > > > > Andres, > > > > > > I approached the Ambari PMC and they responded positively. In > particular, > > > Yusaku had the following comment about your outline: > > > > > > "That sounds like a great idea, Billie. > > > Adding Accumulo support will provide an excellent example on how to > extend > > > the stack and plug it into Ambari for installation, management, and > > > monitoring. > > > This will help future effort by the community to add additional service > > > component to be Ambari-compatible. Also this project will help > discover > > > any improvements that need to be made in order to ease such stack > extension > > > effort. > > > BTW, Ambari has the framework to support 2 and 7 as it does with other > > > service components." > > > > > > Go ahead and subscribe to the Ambari dev list, if you haven't already. > We > > > should also open an Ambari ticket for the project and link it to > relevant > > > Accumulo ticket(s). > > > > > > Additional monitoring features will be a good thing to add if you get > done > > > the other goals and still have some time left. Ambari is currently > doing > > > the same thing for HBase, so hopefully we can learn from them. > > > > > > Looking forward to working with you! > > > Billie > > > On Apr 12, 2013 5:58 PM, "Andres Danter" <[email protected]> wrote: > > > > > >> 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 < > [email protected] > > >> >wrote: > > >> > > >> > The project is open source ... we can't stop you! > > >> > > > >> > > > >> > On Fri, Apr 12, 2013 at 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. > > >> > > > > >> > > > > >> > > > > >> > > 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 > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > > >
