You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by David Medinets <da...@gmail.com> on 2013/04/12 16:29:35 UTC
GSOC Idea - Accumulo Control Panel
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.
Re: GSOC Idea - Accumulo Control Panel
Posted by Eric Newton <er...@gmail.com>.
Can you open a ticket and upload the patch to it?
-Eric
On Fri, Apr 12, 2013 at 2:51 PM, John Vines <vi...@apache.org> wrote:
> On that note, I have a patch for Accumulo for bigtop that needs some more
> work. Ambari uses bigtop for generating rpms.
>
> Sent from my phone, please pardon the typos and brevity.
> On Apr 12, 2013 2:48 PM, "Billie Rinaldi" <bi...@gmail.com>
> wrote:
>
> > On Apr 12, 2013 2:25 PM, "Andres Danter" <ad...@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.
> >
> > 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
> > > <da...@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 <ke...@deenlo.com>
> > wrote:
> > > >
> > > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > > > <da...@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
> > > > >
> > > >
> >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by John Vines <vi...@apache.org>.
On that note, I have a patch for Accumulo for bigtop that needs some more
work. Ambari uses bigtop for generating rpms.
Sent from my phone, please pardon the typos and brevity.
On Apr 12, 2013 2:48 PM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> On Apr 12, 2013 2:25 PM, "Andres Danter" <ad...@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.
>
> 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
> > <da...@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 <ke...@deenlo.com>
> wrote:
> > >
> > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > > <da...@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
> > > >
> > >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Billie Rinaldi <bi...@gmail.com>.
On Apr 12, 2013 2:25 PM, "Andres Danter" <ad...@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.
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
> <da...@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 <ke...@deenlo.com> wrote:
> >
> > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > <da...@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
> > >
> >
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
Thanks for the suggestion, David. I'm not familiar with Yammer's metrics
libraries. I would like to keep this project limited to Ambari and
Accumulo, but I will look at the links you included and learn more about
that library, for future consideration.
Thanks again,
Andres
On Sat, Apr 13, 2013 at 1:44 PM, David Schlosnagle <sc...@gmail.com>wrote:
> In regards to #6, I'm curious if you've considered using Yammer's Apache
> licensed metrics library [1] for capturing stats as it offers many
> different options for consuming and monitoring produced metrics. Coda Hale
> gives a good overview in this talk [2].
>
> [1]: http://metrics.codahale.com/
> [2]: http://pivotallabs.com/139-metrics-metrics-everywhere/
>
> - Dave
>
> On Apr 13, 2013, at 12:15 PM, Andres Danter <ad...@gmail.com> wrote:
>
> > Awesome suggestions! Thank you, Josh.
> > On Apr 12, 2013 10:01 PM, "Josh Elser" <jo...@gmail.com> wrote:
> >
> >> Andres,
> >>
> >> Looks good. Glad to see a lot of good ideas here already. I have a
> couple
> >> of refinements if you don't mind.
> >>
> >> 3. Have the ability to schedule /graceful/ restart of Accumulo...
> >>
> >> It would be really cool to have the option of bringing down an entire
> >> cluster or do a rolling-restart (iteratively bring down a node, let
> things
> >> quiesce, then restart that node) to try to ensure 100% availability.
> >> Accumulo handles most of this for you -- it's more a matter of waiting
> for
> >> any unhosted tablets to be re-assigned after a tabletserver is stopped.
> >>
> >> 4. Push Accumulo code ...
> >>
> >> With 1.5 releases, there's a VFS classloader built in which allows for
> >> various types of file systems to be used to load files onto the
> classpath.
> >> The most interesting of which probably include HDFS, HTTP(S), and
> (S)FTP.
> >> It would be neat to support not only loading classes from the local
> >> filesystem but also by a variety of other means.
> >>
> >> 6. Gather system and/or application metrics..
> >>
> >> Just be aware that this is a very open-ended subject and, most likely,
> >> could be a full GSOC task on its own. You probably want to think about
> what
> >> might be best for Accumulo (starting with what the monitor and master
> >> already supply) and how best you can integrate with Ambari.
> >>
> >> Again, overall, sounds awesome. I look forward to working with you.
> >>
> >>
> >> On 04/12/2013 05:58 PM, Andres Danter 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 <
> 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 <ad...@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
> >>>>> <da...@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 <ke...@deenlo.com>
> >>>>> wrote:
> >>>>
> >>>>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> >>>>>>> <da...@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
> >>
>
Re: GSOC Idea - Accumulo Control Panel
Posted by David Schlosnagle <sc...@gmail.com>.
In regards to #6, I'm curious if you've considered using Yammer's Apache licensed metrics library [1] for capturing stats as it offers many different options for consuming and monitoring produced metrics. Coda Hale gives a good overview in this talk [2].
[1]: http://metrics.codahale.com/
[2]: http://pivotallabs.com/139-metrics-metrics-everywhere/
- Dave
On Apr 13, 2013, at 12:15 PM, Andres Danter <ad...@gmail.com> wrote:
> Awesome suggestions! Thank you, Josh.
> On Apr 12, 2013 10:01 PM, "Josh Elser" <jo...@gmail.com> wrote:
>
>> Andres,
>>
>> Looks good. Glad to see a lot of good ideas here already. I have a couple
>> of refinements if you don't mind.
>>
>> 3. Have the ability to schedule /graceful/ restart of Accumulo...
>>
>> It would be really cool to have the option of bringing down an entire
>> cluster or do a rolling-restart (iteratively bring down a node, let things
>> quiesce, then restart that node) to try to ensure 100% availability.
>> Accumulo handles most of this for you -- it's more a matter of waiting for
>> any unhosted tablets to be re-assigned after a tabletserver is stopped.
>>
>> 4. Push Accumulo code ...
>>
>> With 1.5 releases, there's a VFS classloader built in which allows for
>> various types of file systems to be used to load files onto the classpath.
>> The most interesting of which probably include HDFS, HTTP(S), and (S)FTP.
>> It would be neat to support not only loading classes from the local
>> filesystem but also by a variety of other means.
>>
>> 6. Gather system and/or application metrics..
>>
>> Just be aware that this is a very open-ended subject and, most likely,
>> could be a full GSOC task on its own. You probably want to think about what
>> might be best for Accumulo (starting with what the monitor and master
>> already supply) and how best you can integrate with Ambari.
>>
>> Again, overall, sounds awesome. I look forward to working with you.
>>
>>
>> On 04/12/2013 05:58 PM, Andres Danter 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 <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 <ad...@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
>>>>> <da...@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 <ke...@deenlo.com>
>>>>> wrote:
>>>>
>>>>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>>>>>>> <da...@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
>>
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
Awesome suggestions! Thank you, Josh.
On Apr 12, 2013 10:01 PM, "Josh Elser" <jo...@gmail.com> wrote:
> Andres,
>
> Looks good. Glad to see a lot of good ideas here already. I have a couple
> of refinements if you don't mind.
>
> 3. Have the ability to schedule /graceful/ restart of Accumulo...
>
> It would be really cool to have the option of bringing down an entire
> cluster or do a rolling-restart (iteratively bring down a node, let things
> quiesce, then restart that node) to try to ensure 100% availability.
> Accumulo handles most of this for you -- it's more a matter of waiting for
> any unhosted tablets to be re-assigned after a tabletserver is stopped.
>
> 4. Push Accumulo code ...
>
> With 1.5 releases, there's a VFS classloader built in which allows for
> various types of file systems to be used to load files onto the classpath.
> The most interesting of which probably include HDFS, HTTP(S), and (S)FTP.
> It would be neat to support not only loading classes from the local
> filesystem but also by a variety of other means.
>
> 6. Gather system and/or application metrics..
>
> Just be aware that this is a very open-ended subject and, most likely,
> could be a full GSOC task on its own. You probably want to think about what
> might be best for Accumulo (starting with what the monitor and master
> already supply) and how best you can integrate with Ambari.
>
> Again, overall, sounds awesome. I look forward to working with you.
>
>
> On 04/12/2013 05:58 PM, Andres Danter 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 <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 <ad...@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
>>>> <da...@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 <ke...@deenlo.com>
>>>>>
>>>> wrote:
>>>
>>>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>>>>>> <da...@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
>>>>>>
>>>>>>
>
Re: GSOC Idea - Accumulo Control Panel
Posted by David Medinets <da...@gmail.com>.
I hijacked ACCUMULO-136 and added some details from this email thread.
On Fri, Apr 12, 2013 at 10:01 PM, Josh Elser <jo...@gmail.com> wrote:
> Andres,
>
> Looks good. Glad to see a lot of good ideas here already. I have a couple
> of refinements if you don't mind.
>
> 3. Have the ability to schedule /graceful/ restart of Accumulo...
>
> It would be really cool to have the option of bringing down an entire
> cluster or do a rolling-restart (iteratively bring down a node, let things
> quiesce, then restart that node) to try to ensure 100% availability.
> Accumulo handles most of this for you -- it's more a matter of waiting for
> any unhosted tablets to be re-assigned after a tabletserver is stopped.
>
> 4. Push Accumulo code ...
>
> With 1.5 releases, there's a VFS classloader built in which allows for
> various types of file systems to be used to load files onto the classpath.
> The most interesting of which probably include HDFS, HTTP(S), and (S)FTP.
> It would be neat to support not only loading classes from the local
> filesystem but also by a variety of other means.
>
> 6. Gather system and/or application metrics..
>
> Just be aware that this is a very open-ended subject and, most likely,
> could be a full GSOC task on its own. You probably want to think about what
> might be best for Accumulo (starting with what the monitor and master
> already supply) and how best you can integrate with Ambari.
>
> Again, overall, sounds awesome. I look forward to working with you.
>
>
>
> On 04/12/2013 05:58 PM, Andres Danter 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 <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 <ad...@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
>>>> <da...@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 <ke...@deenlo.com>
>>>>>
>>>> wrote:
>>>
>>>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>>>>>> <da...@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
>>>>>>
>>>>>>
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Josh Elser <jo...@gmail.com>.
Andres,
Looks good. Glad to see a lot of good ideas here already. I have a
couple of refinements if you don't mind.
3. Have the ability to schedule /graceful/ restart of Accumulo...
It would be really cool to have the option of bringing down an entire
cluster or do a rolling-restart (iteratively bring down a node, let
things quiesce, then restart that node) to try to ensure 100%
availability. Accumulo handles most of this for you -- it's more a
matter of waiting for any unhosted tablets to be re-assigned after a
tabletserver is stopped.
4. Push Accumulo code ...
With 1.5 releases, there's a VFS classloader built in which allows for
various types of file systems to be used to load files onto the
classpath. The most interesting of which probably include HDFS, HTTP(S),
and (S)FTP. It would be neat to support not only loading classes from
the local filesystem but also by a variety of other means.
6. Gather system and/or application metrics..
Just be aware that this is a very open-ended subject and, most likely,
could be a full GSOC task on its own. You probably want to think about
what might be best for Accumulo (starting with what the monitor and
master already supply) and how best you can integrate with Ambari.
Again, overall, sounds awesome. I look forward to working with you.
On 04/12/2013 05:58 PM, Andres Danter 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 <da...@gmail.com>wrote:
>
>> The project is open source ... we can't stop you!
>>
>>
>> On Fri, Apr 12, 2013 at 2:25 PM, Andres Danter <ad...@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
>>> <da...@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 <ke...@deenlo.com>
>> wrote:
>>>>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>>>>> <da...@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
>>>>>
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
Keith,
Thanks for the tip. I went ahead and made the change. I'm not sure if
there are any BigTop tickets that need to be linked. I'll do a search for
that later.
Thanks again,
Andres
On Mon, Apr 15, 2013 at 12:46 PM, Keith Turner <ke...@deenlo.com> wrote:
> Andres,
>
> You can link tickets in Jira. Go to "More Actions->Link" on the
> ticket page. This is a little better than putting tickets in
> comments, the link will automatically show up in both tickets.
>
> Are there any BigTop tickets that should be linked to these tickets?
>
> Keith
>
> On Sun, Apr 14, 2013 at 7:49 PM, Andres Danter <ad...@gmail.com> wrote:
> > Billie,
> > Thanks. I have created the ticket for Ambari (AMBARI-1930). I started
> > putting together the proposal, but I need to do a lot of research and
> > thinking before I can finish it. I'll keep working on that this week.
> >
> > Take care,
> >
> > Andres
> > <https://issues.apache.org/jira/browse/AMBARI-1930>
> >
> >
> > On Sun, Apr 14, 2013 at 7:04 PM, Billie Rinaldi <
> billie.rinaldi@gmail.com>wrote:
> >
> >> Andres,
> >>
> >> I would go with issue type "improvement," leave the priority major, and
> the
> >> component blank for now. The rest looks great.
> >>
> >> Billie
> >>
> >> On Apr 14, 2013 4:23 PM, "Andres Danter" <ad...@gmail.com> wrote:
> >> >
> >> > 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
> >> > <bi...@gmail.com>wrote:
> >> >
> >> > > On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
> >> > > > <bi...@gmail.com>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" <ad...@gmail.com>
> >> 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 <
> >> > > 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
> >> > > > >> > > <da...@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
> >> > > > >> > > > > <da...@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
> >> > > > >> > > > >
> >> > > > >> > > >
> >> > > > >> > >
> >> > > > >> >
> >> > > > >>
> >> > > > >
> >> > >
> >>
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Keith Turner <ke...@deenlo.com>.
Andres,
You can link tickets in Jira. Go to "More Actions->Link" on the
ticket page. This is a little better than putting tickets in
comments, the link will automatically show up in both tickets.
Are there any BigTop tickets that should be linked to these tickets?
Keith
On Sun, Apr 14, 2013 at 7:49 PM, Andres Danter <ad...@gmail.com> wrote:
> Billie,
> Thanks. I have created the ticket for Ambari (AMBARI-1930). I started
> putting together the proposal, but I need to do a lot of research and
> thinking before I can finish it. I'll keep working on that this week.
>
> Take care,
>
> Andres
> <https://issues.apache.org/jira/browse/AMBARI-1930>
>
>
> On Sun, Apr 14, 2013 at 7:04 PM, Billie Rinaldi <bi...@gmail.com>wrote:
>
>> Andres,
>>
>> I would go with issue type "improvement," leave the priority major, and the
>> component blank for now. The rest looks great.
>>
>> Billie
>>
>> On Apr 14, 2013 4:23 PM, "Andres Danter" <ad...@gmail.com> wrote:
>> >
>> > 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
>> > <bi...@gmail.com>wrote:
>> >
>> > > On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
>> > > > <bi...@gmail.com>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" <ad...@gmail.com>
>> 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 <
>> > > 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
>> > > > >> > > <da...@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
>> > > > >> > > > > <da...@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
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > >
>> > > > >> >
>> > > > >>
>> > > > >
>> > >
>>
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
Billie,
Thanks. I have created the ticket for Ambari (AMBARI-1930). I started
putting together the proposal, but I need to do a lot of research and
thinking before I can finish it. I'll keep working on that this week.
Take care,
Andres
<https://issues.apache.org/jira/browse/AMBARI-1930>
On Sun, Apr 14, 2013 at 7:04 PM, Billie Rinaldi <bi...@gmail.com>wrote:
> Andres,
>
> I would go with issue type "improvement," leave the priority major, and the
> component blank for now. The rest looks great.
>
> Billie
>
> On Apr 14, 2013 4:23 PM, "Andres Danter" <ad...@gmail.com> wrote:
> >
> > 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
> > <bi...@gmail.com>wrote:
> >
> > > On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
> > > > <bi...@gmail.com>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" <ad...@gmail.com>
> 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 <
> > > 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
> > > > >> > > <da...@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
> > > > >> > > > > <da...@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
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >
> > >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Billie Rinaldi <bi...@gmail.com>.
Andres,
I would go with issue type "improvement," leave the priority major, and the
component blank for now. The rest looks great.
Billie
On Apr 14, 2013 4:23 PM, "Andres Danter" <ad...@gmail.com> wrote:
>
> 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
> <bi...@gmail.com>wrote:
>
> > On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
> > > <bi...@gmail.com>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" <ad...@gmail.com> 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 <
> > 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
> > > >> > > <da...@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
> > > >> > > > > <da...@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
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> >
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
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
<bi...@gmail.com>wrote:
> On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
> > <bi...@gmail.com>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" <ad...@gmail.com> 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 <
> 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 <ad...@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
> > >> > > <da...@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
> > >> > > > > <da...@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
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Billie Rinaldi <bi...@gmail.com>.
On Apr 13, 2013 3:17 PM, "Andres Danter" <ad...@gmail.com> 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
> <bi...@gmail.com>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" <ad...@gmail.com> 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 <
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 <ad...@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
> >> > > <da...@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 <ke...@deenlo.com>
> >> > wrote:
> >> > > >
> >> > > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> >> > > > > <da...@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
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
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?
Andres
On Sat, Apr 13, 2013 at 10:29 AM, Billie Rinaldi
<bi...@gmail.com>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" <ad...@gmail.com> 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 <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 <ad...@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
>> > > <da...@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 <ke...@deenlo.com>
>> > wrote:
>> > > >
>> > > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>> > > > > <da...@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
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
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 <da...@gmail.com>wrote:
> The project is open source ... we can't stop you!
>
>
> On Fri, Apr 12, 2013 at 2:25 PM, Andres Danter <ad...@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
> > <da...@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 <ke...@deenlo.com>
> wrote:
> > >
> > > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > > <da...@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
> > > >
> > >
> >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by David Medinets <da...@gmail.com>.
The project is open source ... we can't stop you!
On Fri, Apr 12, 2013 at 2:25 PM, Andres Danter <ad...@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
> <da...@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 <ke...@deenlo.com> wrote:
> >
> > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > <da...@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
> > >
> >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Keith Turner <ke...@deenlo.com>.
On Fri, Apr 12, 2013 at 2:25 PM, Andres Danter <ad...@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.
That would be great. You would need to ensure the Ambari project is receptive.
>
>
>
> On Fri, Apr 12, 2013 at 11:47 AM, David Medinets
> <da...@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 <ke...@deenlo.com> wrote:
>>
>> > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>> > <da...@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
>> >
>>
Re: GSOC Idea - Accumulo Control Panel
Posted by John Vines <jv...@gmail.com>.
I think that would be awesome!
Sent from my phone, please pardon the typos and brevity.
On Apr 12, 2013 2:25 PM, "Andres Danter" <ad...@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
> <da...@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 <ke...@deenlo.com> wrote:
> >
> > > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > > <da...@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
> > >
> >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Andres Danter <ad...@gmail.com>.
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
<da...@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 <ke...@deenlo.com> wrote:
>
> > On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> > <da...@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
> >
>
Re: GSOC Idea - Accumulo Control Panel
Posted by David Medinets <da...@gmail.com>.
Thanks for the reminder. I had forgotten the name of Ambari.
On Fri, Apr 12, 2013 at 10:37 AM, Keith Turner <ke...@deenlo.com> wrote:
> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> <da...@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
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Christopher <ct...@apache.org>.
I think it should be a separate ticket, because the shell integration
into the monitor was the main work for ACCUMULO-196, and the only
thing remaining for that is testing. (At least, that was my
understanding when Billie reassigned the ticket to me). If there's
more work to be done, for a,c, and f, the other ticket can link to
196, I think.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Fri, Apr 12, 2013 at 11:31 AM, John Vines <vi...@apache.org> wrote:
> a,c, and f sound like the scope I originally planned for
> https://issues.apache.org/jira/browse/ACCUMULO-196
>
> And like Keith said, the entire thing could also be wrapped up in Ambari.
>
>
> On Fri, Apr 12, 2013 at 10:37 AM, Keith Turner <ke...@deenlo.com> wrote:
>
>> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
>> <da...@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
>>
Re: GSOC Idea - Accumulo Control Panel
Posted by John Vines <vi...@apache.org>.
a,c, and f sound like the scope I originally planned for
https://issues.apache.org/jira/browse/ACCUMULO-196
And like Keith said, the entire thing could also be wrapped up in Ambari.
On Fri, Apr 12, 2013 at 10:37 AM, Keith Turner <ke...@deenlo.com> wrote:
> On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
> <da...@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
>
Re: GSOC Idea - Accumulo Control Panel
Posted by Keith Turner <ke...@deenlo.com>.
On Fri, Apr 12, 2013 at 10:29 AM, David Medinets
<da...@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