oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Multiple Processing Paradigms at Once
Date Wed, 06 Aug 2014 16:08:10 GMT
See OODT-215 and OODT-491 the functionality is not absent it is present and those issues are
the  current status

Sent from my iPhone

> On Aug 6, 2014, at 8:53 AM, "Michael Starch" <starchmd@umich.edu> wrote:
> 
> Chris,
> 
> I believe I am working on the truck of OODT.  The WEngine branch already
> does what I need it to, however; the absence of this functionality in trunk
> led me to wonder if this approach is undesired...hence this question.
> 
> -Michael
> 
> 
> On Wed, Aug 6, 2014 at 8:50 AM, Chris Mattmann <chris.mattmann@gmail.com>
> wrote:
> 
>> Hi Mike,
>> 
>> I think you are using the wengine branch of Apache OODT.
>> That is unmaintained. I would sincerely urge you to get
>> this working in trunk, that's where the developers are working
>> right now.
>> 
>> Cheers,
>> Chris
>> 
>> P.S. Let me think more about the below I have some ideas there.
>> 
>> ------------------------
>> Chris Mattmann
>> chris.mattmann@gmail.com
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: Michael Starch <starchmd@umich.edu>
>> Reply-To: <dev@oodt.apache.org>
>> Date: Wednesday, August 6, 2014 8:29 AM
>> To: <dev@oodt.apache.org>
>> Subject: Multiple Processing Paradigms at Once
>> 
>>> All,
>>> 
>>> I am working on upgrading OODT to allow it to process streaming data,
>>> alongside traditional non-streaming jobs.  This means that some jobs need
>>> to be run by the resource manager, and other jobs need to be submitted to
>>> the stream-processing.  Therefore, processing needs to be forked or
>>> multiplexed at some point in the life-cycle.
>>> 
>>> There are two places where this can be done: workflow manager runners, and
>>> the resource manager.  Currently, I am  working on building workflow
>>> runners, and doing the job-multiplexing there because this cuts out one
>>> superfluous step for the streaming jobs (namely going to the resource
>>> manager before being routed).
>>> 
>>> Are there any comments on this approach or does this approach make sense?
>>> 
>>> -Michael Starch
>> 
>> 
>> 

Mime
View raw message