oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheryl John <shery...@gmail.com>
Subject Re: Staging CAS-PGE config file...
Date Wed, 02 May 2012 04:49:52 GMT
Hi Brian,

I'm still going through the wmgr -2 & wengine branch CAS-PGE, but are you
suggesting to always use resource manager to support the configuration?

Actually, we've not yet used resource manager with workflow and CAS-PGE in
the VPICU project (currently in the process of learning and setting it up )
and, so I have little knowledge of how the resource manager can support
this. But if it does support, does that imply that I have to use PGEs and
workflows with resource mgr?

I agree that setting the *ConfigFilePath* to the temporary dir where the
task executes on, within the config itself to generate the object is kind
of confusing and should be given before it runs.

On Tue, May 1, 2012 at 5:20 PM, Brian Foster <holenoter@mac.com> wrote:

> hey guys,
> in the wengine branched CAS-PGE, it supported staging the CAS-PGE's XML
> config file to tmp directory so it could be parsed and then processed and
> then the staged config file was copied CAS-PGE's working directory (had to
> be copied later since the working directory information is in the config
> file).  I think this should be something the resource manager should
> instead support... staging job binaries and config that is need to run the
> jobs would be a cleaner implementation than what wengine CAS-PGE does...
> CAS-PGE would still stage Products and ingest them itself (that is a
> CAS-PGE specified task), however the knowledge of getting CAS-PGE's
> configuration file which configures it should already be there when it
> runs... otherwise you kinda need configuration for CAS-PGE configuration
> (chicken and egg problem)... what you guys think?
> -brian


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message