You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by Alejandro Abdelnur <tu...@cloudera.com> on 2012/06/21 18:37:31 UTC
Fwd: Post meetup discussion
Maxime,
Thanks for taking the initiative of summarizing the meetup and get things
going.
Attached are the PDFs for the 3 presentations we had (thanks to Michelle
and Mona for sharing the slides), hope the information is useful.
Thx.
Alejandro
On Mon, Jun 18, 2012 at 7:53 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> Hi Max,
> Thanks for your email with a quick summary of oozie meetup.
>
>
> These are the action items and initial actors based on your list:
> 1(a) Eliminate redundancies in XML definitions. Britt/Mohammad
> 1(b) XML modeling tool. (Ryota/Ashish/Mohammad)
>
> 2. Visualize the Workflow current status.(Virag/Mohammad)
> 3. Deployment tools ( Max)
> 4. More to add...
>
> Please follow-up on these action items in couple of week.
> Regards,
> Mohammad
> ________________________________
> From: Maxime Petazzoni <ma...@turn.com>
> To: oozie-users@incubator.apache.org
> Sent: Monday, June 18, 2012 7:13 PM
> Subject: Post meetup discussion
>
> Hi all,
>
> Last week a bunch of us attended the Oozie Meetup prior to the Hadoop
> Summit at the San Jose Convention Center. It was really nice to be able
> to interact face-to-face with other Oozie contributors and users.
>
> At the end of the meetup we went over a few items that gathered
> consensus. I'd like to get the discussion going again on these so we can
> get to more precise requirements and use cases, and maybe inspire a few
> of us to get crackin'.
>
> I'll start first, to get the ball rolling.
>
> - one thing that was mentioned a lot is the ability to visually create
> workflows and coordinators instead of having to write XML. Although
> I personally don't rank this to be very high priority -- my use
> case is less around ad-hoc workflows -- I do see a huge value in
> this, if only to help spread Oozie.
>
> - directly related to visualization, monitoring of the running
> workflows is definitely at the top of my list. Being able to
> visualize the DAG of a workflow, with the completed actions in
> green, in progress action in yellow, failed action(s) in red would
> be a huge help for real-time monitoring and debugging.
>
> I've also written a command-line Python utility that helps managing a
> set of coordinators that need to run in various Hadoop clusters,
> exposing them as "applications" to the release manager. I'm not sure if
> this has any value for Oozie, but if anybody's interested I might be
> able to share the code for that.
>
> /Maxime
>
Re: Post meetup discussion
Posted by Harsh J <ha...@cloudera.com>.
Hey Alejandro,
The ML seems to have stripped away attachments. Can you upload them on
dropbox or so?
On Thu, Jun 21, 2012 at 10:07 PM, Alejandro Abdelnur <tu...@cloudera.com> wrote:
> Maxime,
>
> Thanks for taking the initiative of summarizing the meetup and get things
> going.
>
> Attached are the PDFs for the 3 presentations we had (thanks to Michelle and
> Mona for sharing the slides), hope the information is useful.
>
> Thx.
>
> Alejandro
>
>
>
> On Mon, Jun 18, 2012 at 7:53 PM, Mohammad Islam <mi...@yahoo.com> wrote:
>>
>> Hi Max,
>> Thanks for your email with a quick summary of oozie meetup.
>>
>>
>> These are the action items and initial actors based on your list:
>> 1(a) Eliminate redundancies in XML definitions. Britt/Mohammad
>> 1(b) XML modeling tool. (Ryota/Ashish/Mohammad)
>>
>> 2. Visualize the Workflow current status.(Virag/Mohammad)
>> 3. Deployment tools ( Max)
>> 4. More to add...
>>
>> Please follow-up on these action items in couple of week.
>> Regards,
>> Mohammad
>> ________________________________
>> From: Maxime Petazzoni <ma...@turn.com>
>> To: oozie-users@incubator.apache.org
>> Sent: Monday, June 18, 2012 7:13 PM
>> Subject: Post meetup discussion
>>
>> Hi all,
>>
>> Last week a bunch of us attended the Oozie Meetup prior to the Hadoop
>> Summit at the San Jose Convention Center. It was really nice to be able
>> to interact face-to-face with other Oozie contributors and users.
>>
>> At the end of the meetup we went over a few items that gathered
>> consensus. I'd like to get the discussion going again on these so we can
>> get to more precise requirements and use cases, and maybe inspire a few
>> of us to get crackin'.
>>
>> I'll start first, to get the ball rolling.
>>
>> - one thing that was mentioned a lot is the ability to visually create
>> workflows and coordinators instead of having to write XML. Although
>> I personally don't rank this to be very high priority -- my use
>> case is less around ad-hoc workflows -- I do see a huge value in
>> this, if only to help spread Oozie.
>>
>> - directly related to visualization, monitoring of the running
>> workflows is definitely at the top of my list. Being able to
>> visualize the DAG of a workflow, with the completed actions in
>> green, in progress action in yellow, failed action(s) in red would
>> be a huge help for real-time monitoring and debugging.
>>
>> I've also written a command-line Python utility that helps managing a
>> set of coordinators that need to run in various Hadoop clusters,
>> exposing them as "applications" to the release manager. I'm not sure if
>> this has any value for Oozie, but if anybody's interested I might be
>> able to share the code for that.
>>
>> /Maxime
--
Harsh J
Re: Post meetup discussion
Posted by Harsh J <ha...@cloudera.com>.
Hey Alejandro,
The ML seems to have stripped away attachments. Can you upload them on
dropbox or so?
On Thu, Jun 21, 2012 at 10:07 PM, Alejandro Abdelnur <tu...@cloudera.com> wrote:
> Maxime,
>
> Thanks for taking the initiative of summarizing the meetup and get things
> going.
>
> Attached are the PDFs for the 3 presentations we had (thanks to Michelle and
> Mona for sharing the slides), hope the information is useful.
>
> Thx.
>
> Alejandro
>
>
>
> On Mon, Jun 18, 2012 at 7:53 PM, Mohammad Islam <mi...@yahoo.com> wrote:
>>
>> Hi Max,
>> Thanks for your email with a quick summary of oozie meetup.
>>
>>
>> These are the action items and initial actors based on your list:
>> 1(a) Eliminate redundancies in XML definitions. Britt/Mohammad
>> 1(b) XML modeling tool. (Ryota/Ashish/Mohammad)
>>
>> 2. Visualize the Workflow current status.(Virag/Mohammad)
>> 3. Deployment tools ( Max)
>> 4. More to add...
>>
>> Please follow-up on these action items in couple of week.
>> Regards,
>> Mohammad
>> ________________________________
>> From: Maxime Petazzoni <ma...@turn.com>
>> To: oozie-users@incubator.apache.org
>> Sent: Monday, June 18, 2012 7:13 PM
>> Subject: Post meetup discussion
>>
>> Hi all,
>>
>> Last week a bunch of us attended the Oozie Meetup prior to the Hadoop
>> Summit at the San Jose Convention Center. It was really nice to be able
>> to interact face-to-face with other Oozie contributors and users.
>>
>> At the end of the meetup we went over a few items that gathered
>> consensus. I'd like to get the discussion going again on these so we can
>> get to more precise requirements and use cases, and maybe inspire a few
>> of us to get crackin'.
>>
>> I'll start first, to get the ball rolling.
>>
>> - one thing that was mentioned a lot is the ability to visually create
>> workflows and coordinators instead of having to write XML. Although
>> I personally don't rank this to be very high priority -- my use
>> case is less around ad-hoc workflows -- I do see a huge value in
>> this, if only to help spread Oozie.
>>
>> - directly related to visualization, monitoring of the running
>> workflows is definitely at the top of my list. Being able to
>> visualize the DAG of a workflow, with the completed actions in
>> green, in progress action in yellow, failed action(s) in red would
>> be a huge help for real-time monitoring and debugging.
>>
>> I've also written a command-line Python utility that helps managing a
>> set of coordinators that need to run in various Hadoop clusters,
>> exposing them as "applications" to the release manager. I'm not sure if
>> this has any value for Oozie, but if anybody's interested I might be
>> able to share the code for that.
>>
>> /Maxime
--
Harsh J