You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Mohammad Islam <mi...@yahoo.com> on 2012/06/28 06:50:49 UTC
Workflow Modeling tool: please comment
Hi,
At last, the Oozie team at Yahoo has taken concrete steps to implement the most expected feature of Oozie: Workflow modeling tool to generate XML.
Ryota is evaluating different UI tools and opened a JIRA (https://issues.apache.org/jira/browse/OOZIE-884).
Ashish is designing a mock UI and also created another JIRA to track. (https://issues.apache.org/jira/browse/OOZIE-883)
Please give your suggestions/comments into those JIRAs.
Regards,
Mohammad
Re: Workflow Modeling tool: please comment
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Ventakesh,
This is the first step of designing a tool using GWT (w/o extJS) in Oozie. it is the first step towards replacing the extJS from current UI.
Regards,
Mohammad
________________________________
From: Seetharam Venkatesh <ve...@innerzeal.com>
To: oozie-users@incubator.apache.org
Cc: Mohammad Islam <mi...@yahoo.com>
Sent: Friday, June 29, 2012 2:21 PM
Subject: Re: Workflow Modeling tool: please comment
Hi Mohammad,
Great initiative! Will this also encompass replacing the current Web
Console using ExtJS to Apache-licence compatible UI framework?
On Thu, Jun 28, 2012 at 12:52 PM, Senthilvel Rangaswamy <
senthilvel@gmail.com> wrote:
> This is great. IMHO, the runtime visualization of WF is more needed than
> visual modelling tools.
>
>
> On Thu, Jun 28, 2012 at 12:30 PM, Mohammad Islam <mi...@yahoo.com>
> wrote:
>
> > Hi Alejandro,
> > OOZIE-884 and 883 are for the same modeling tool to generate/view
> > workflow.xml.
> > We splitted the task into two JIRAs because two persons are driving these
> > related issue.=
> >
> > 884 is to finalize the look and feel design. Not the implementation.
> > 883 is to evaluate different technology such as GWT to implement the
> > design decided on 884.
> >
> > However, we need to create another JIRA for runtime visualization of WF.
> >
> > Regards,
> > Mohammad
> >
> > ----- Original Message -----
> > From: Alejandro Abdelnur <tu...@cloudera.com>
> > To: oozie-users@incubator.apache.org
> > Cc:
> > Sent: Thursday, June 28, 2012 9:29 AM
> > Subject: Re: Workflow Modeling tool: please comment
> >
> > Great that you guys are bootstrapping this.
> >
> > Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic
> > representation of a WF and OOZIE-883 is for WYSIWYG authoring a
> > workflow.....
> >
> > * OOZIE-884 would belong to the web UI where the user would see
> graphically
> > where the processing is for the WF
> > * The web UI needs a revamp to be able to see detailed info of
> coord/bundle
> > jobs
> > * The web UI needs to be rewritten using a UI framework other than ExtJS
> > for licensing issues
> > * A problem we always had the Oozie developers is the lack of Javascript
> > skills to improve the web UI
> > * What I really like about Oozie-883 mock up is the 'load WF' button,
> this
> > is a critical feature, being able to suck and edit an existing WF
> > * Using GWT seems like a good choice as it would allow IDE development
> and
> > Java skills
> > * As GWT converts things to JS we could still deploy the console as we do
> > today (part of the WAR) (this is a big plus over things like PHP, Phyton
> > backend solutions)
> > * IMO we should open an new JIRA to port the existing web UI to GWT as
> > well.
> >
> > An maybe we should model a couple of screen of the existing web UI in GWT
> > to see that it will work.
> >
> > Thx.
> >
> >
> > On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <mi...@yahoo.com>
> > wrote:
> >
> > > Hi,
> > > At last, the Oozie team at Yahoo has taken concrete steps to implement
> > the
> > > most expected feature of Oozie: Workflow modeling tool to generate
> XML.
> > > Ryota is evaluating different UI tools and opened a JIRA (
> > > https://issues.apache.org/jira/browse/OOZIE-884).
> > > Ashish is designing a mock UI and also created another JIRA to track. (
> > > https://issues.apache.org/jira/browse/OOZIE-883)
> > >
> > > Please give your suggestions/comments into those JIRAs.
> > >
> > > Regards,
> > > Mohammad
> > >
> >
> >
> >
> > --
> > Alejandro
> >
> >
>
>
> --
> ..Senthil
>
> "If there's anything more important than my ego around, I want it
> caught and shot now."
> - Douglas Adams.
>
--
Regards,
Venkatesh
Phone: (408) 658-8368
EMail: Venkatesh@InnerZeal.com
http://in.linkedin.com/in/seetharamvenkatesh
http://about.me/SeetharamVenkatesh
“Perfection (in design) is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.”
- Antoine de Saint-Exupéry
Re: Workflow Modeling tool: please comment
Posted by Seetharam Venkatesh <ve...@innerzeal.com>.
Hi Mohammad,
Great initiative! Will this also encompass replacing the current Web
Console using ExtJS to Apache-licence compatible UI framework?
On Thu, Jun 28, 2012 at 12:52 PM, Senthilvel Rangaswamy <
senthilvel@gmail.com> wrote:
> This is great. IMHO, the runtime visualization of WF is more needed than
> visual modelling tools.
>
>
> On Thu, Jun 28, 2012 at 12:30 PM, Mohammad Islam <mi...@yahoo.com>
> wrote:
>
> > Hi Alejandro,
> > OOZIE-884 and 883 are for the same modeling tool to generate/view
> > workflow.xml.
> > We splitted the task into two JIRAs because two persons are driving these
> > related issue.=
> >
> > 884 is to finalize the look and feel design. Not the implementation.
> > 883 is to evaluate different technology such as GWT to implement the
> > design decided on 884.
> >
> > However, we need to create another JIRA for runtime visualization of WF.
> >
> > Regards,
> > Mohammad
> >
> > ----- Original Message -----
> > From: Alejandro Abdelnur <tu...@cloudera.com>
> > To: oozie-users@incubator.apache.org
> > Cc:
> > Sent: Thursday, June 28, 2012 9:29 AM
> > Subject: Re: Workflow Modeling tool: please comment
> >
> > Great that you guys are bootstrapping this.
> >
> > Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic
> > representation of a WF and OOZIE-883 is for WYSIWYG authoring a
> > workflow.....
> >
> > * OOZIE-884 would belong to the web UI where the user would see
> graphically
> > where the processing is for the WF
> > * The web UI needs a revamp to be able to see detailed info of
> coord/bundle
> > jobs
> > * The web UI needs to be rewritten using a UI framework other than ExtJS
> > for licensing issues
> > * A problem we always had the Oozie developers is the lack of Javascript
> > skills to improve the web UI
> > * What I really like about Oozie-883 mock up is the 'load WF' button,
> this
> > is a critical feature, being able to suck and edit an existing WF
> > * Using GWT seems like a good choice as it would allow IDE development
> and
> > Java skills
> > * As GWT converts things to JS we could still deploy the console as we do
> > today (part of the WAR) (this is a big plus over things like PHP, Phyton
> > backend solutions)
> > * IMO we should open an new JIRA to port the existing web UI to GWT as
> > well.
> >
> > An maybe we should model a couple of screen of the existing web UI in GWT
> > to see that it will work.
> >
> > Thx.
> >
> >
> > On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <mi...@yahoo.com>
> > wrote:
> >
> > > Hi,
> > > At last, the Oozie team at Yahoo has taken concrete steps to implement
> > the
> > > most expected feature of Oozie: Workflow modeling tool to generate
> XML.
> > > Ryota is evaluating different UI tools and opened a JIRA (
> > > https://issues.apache.org/jira/browse/OOZIE-884).
> > > Ashish is designing a mock UI and also created another JIRA to track. (
> > > https://issues.apache.org/jira/browse/OOZIE-883)
> > >
> > > Please give your suggestions/comments into those JIRAs.
> > >
> > > Regards,
> > > Mohammad
> > >
> >
> >
> >
> > --
> > Alejandro
> >
> >
>
>
> --
> ..Senthil
>
> "If there's anything more important than my ego around, I want it
> caught and shot now."
> - Douglas Adams.
>
--
Regards,
Venkatesh
Phone: (408) 658-8368
EMail: Venkatesh@InnerZeal.com
http://in.linkedin.com/in/seetharamvenkatesh
http://about.me/SeetharamVenkatesh
“Perfection (in design) is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.”
- Antoine de Saint-Exupéry
Re: Workflow Modeling tool: please comment
Posted by Senthilvel Rangaswamy <se...@gmail.com>.
This is great. IMHO, the runtime visualization of WF is more needed than
visual modelling tools.
On Thu, Jun 28, 2012 at 12:30 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> Hi Alejandro,
> OOZIE-884 and 883 are for the same modeling tool to generate/view
> workflow.xml.
> We splitted the task into two JIRAs because two persons are driving these
> related issue.=
>
> 884 is to finalize the look and feel design. Not the implementation.
> 883 is to evaluate different technology such as GWT to implement the
> design decided on 884.
>
> However, we need to create another JIRA for runtime visualization of WF.
>
> Regards,
> Mohammad
>
> ----- Original Message -----
> From: Alejandro Abdelnur <tu...@cloudera.com>
> To: oozie-users@incubator.apache.org
> Cc:
> Sent: Thursday, June 28, 2012 9:29 AM
> Subject: Re: Workflow Modeling tool: please comment
>
> Great that you guys are bootstrapping this.
>
> Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic
> representation of a WF and OOZIE-883 is for WYSIWYG authoring a
> workflow.....
>
> * OOZIE-884 would belong to the web UI where the user would see graphically
> where the processing is for the WF
> * The web UI needs a revamp to be able to see detailed info of coord/bundle
> jobs
> * The web UI needs to be rewritten using a UI framework other than ExtJS
> for licensing issues
> * A problem we always had the Oozie developers is the lack of Javascript
> skills to improve the web UI
> * What I really like about Oozie-883 mock up is the 'load WF' button, this
> is a critical feature, being able to suck and edit an existing WF
> * Using GWT seems like a good choice as it would allow IDE development and
> Java skills
> * As GWT converts things to JS we could still deploy the console as we do
> today (part of the WAR) (this is a big plus over things like PHP, Phyton
> backend solutions)
> * IMO we should open an new JIRA to port the existing web UI to GWT as
> well.
>
> An maybe we should model a couple of screen of the existing web UI in GWT
> to see that it will work.
>
> Thx.
>
>
> On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <mi...@yahoo.com>
> wrote:
>
> > Hi,
> > At last, the Oozie team at Yahoo has taken concrete steps to implement
> the
> > most expected feature of Oozie: Workflow modeling tool to generate XML.
> > Ryota is evaluating different UI tools and opened a JIRA (
> > https://issues.apache.org/jira/browse/OOZIE-884).
> > Ashish is designing a mock UI and also created another JIRA to track. (
> > https://issues.apache.org/jira/browse/OOZIE-883)
> >
> > Please give your suggestions/comments into those JIRAs.
> >
> > Regards,
> > Mohammad
> >
>
>
>
> --
> Alejandro
>
>
--
..Senthil
"If there's anything more important than my ego around, I want it
caught and shot now."
- Douglas Adams.
Re: Workflow Modeling tool: please comment
Posted by Mohammad Islam <mi...@yahoo.com>.
Hi Alejandro,
OOZIE-884 and 883 are for the same modeling tool to generate/view workflow.xml.
We splitted the task into two JIRAs because two persons are driving these related issue.=
884 is to finalize the look and feel design. Not the implementation.
883 is to evaluate different technology such as GWT to implement the design decided on 884.
However, we need to create another JIRA for runtime visualization of WF.
Regards,
Mohammad
----- Original Message -----
From: Alejandro Abdelnur <tu...@cloudera.com>
To: oozie-users@incubator.apache.org
Cc:
Sent: Thursday, June 28, 2012 9:29 AM
Subject: Re: Workflow Modeling tool: please comment
Great that you guys are bootstrapping this.
Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic
representation of a WF and OOZIE-883 is for WYSIWYG authoring a
workflow.....
* OOZIE-884 would belong to the web UI where the user would see graphically
where the processing is for the WF
* The web UI needs a revamp to be able to see detailed info of coord/bundle
jobs
* The web UI needs to be rewritten using a UI framework other than ExtJS
for licensing issues
* A problem we always had the Oozie developers is the lack of Javascript
skills to improve the web UI
* What I really like about Oozie-883 mock up is the 'load WF' button, this
is a critical feature, being able to suck and edit an existing WF
* Using GWT seems like a good choice as it would allow IDE development and
Java skills
* As GWT converts things to JS we could still deploy the console as we do
today (part of the WAR) (this is a big plus over things like PHP, Phyton
backend solutions)
* IMO we should open an new JIRA to port the existing web UI to GWT as well.
An maybe we should model a couple of screen of the existing web UI in GWT
to see that it will work.
Thx.
On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> Hi,
> At last, the Oozie team at Yahoo has taken concrete steps to implement the
> most expected feature of Oozie: Workflow modeling tool to generate XML.
> Ryota is evaluating different UI tools and opened a JIRA (
> https://issues.apache.org/jira/browse/OOZIE-884).
> Ashish is designing a mock UI and also created another JIRA to track. (
> https://issues.apache.org/jira/browse/OOZIE-883)
>
> Please give your suggestions/comments into those JIRAs.
>
> Regards,
> Mohammad
>
--
Alejandro
Re: Workflow Modeling tool: please comment
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
Great that you guys are bootstrapping this.
Assuming I understand correctly these 2 JIRAs: OOZIE-884 is for graphic
representation of a WF and OOZIE-883 is for WYSIWYG authoring a
workflow.....
* OOZIE-884 would belong to the web UI where the user would see graphically
where the processing is for the WF
* The web UI needs a revamp to be able to see detailed info of coord/bundle
jobs
* The web UI needs to be rewritten using a UI framework other than ExtJS
for licensing issues
* A problem we always had the Oozie developers is the lack of Javascript
skills to improve the web UI
* What I really like about Oozie-883 mock up is the 'load WF' button, this
is a critical feature, being able to suck and edit an existing WF
* Using GWT seems like a good choice as it would allow IDE development and
Java skills
* As GWT converts things to JS we could still deploy the console as we do
today (part of the WAR) (this is a big plus over things like PHP, Phyton
backend solutions)
* IMO we should open an new JIRA to port the existing web UI to GWT as well.
An maybe we should model a couple of screen of the existing web UI in GWT
to see that it will work.
Thx.
On Wed, Jun 27, 2012 at 9:50 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> Hi,
> At last, the Oozie team at Yahoo has taken concrete steps to implement the
> most expected feature of Oozie: Workflow modeling tool to generate XML.
> Ryota is evaluating different UI tools and opened a JIRA (
> https://issues.apache.org/jira/browse/OOZIE-884).
> Ashish is designing a mock UI and also created another JIRA to track. (
> https://issues.apache.org/jira/browse/OOZIE-883)
>
> Please give your suggestions/comments into those JIRAs.
>
> Regards,
> Mohammad
>
--
Alejandro