[kepler-dev] GlobusProxy actor

Zhijie Guan guan at sdsc.edu
Fri Feb 24 12:40:07 PST 2006

On Fri, 24 Feb 2006, Norbert Podhorszki wrote:

> Both solutions are command-line workarounds, which are to be managed outside 
> Kepler. Which is not nice for a GUI based fancy workflow system. I mean, a 
> "Now, please, open a terminal, issue the command xxx and then I can continue. 
> Thanks, Kepler" dialog would look funny during the workflow execution, 
> wouldn't it?

Well. If a "GUI based" (a.k.a. actor-oriented) workflow model is 
preferred, I'd like to try using command-line execution actor to run 
"grid-proxy-init" with username/password. Basically you need to "mimic" 
your login procedure as a sub-workflow. Check those actors in 
"Actor/External Execution Enviornment Actor" directory of a Vergil 
interface. Those names of the actors sound promising.

> Is there an actor in Kepler, that gets a proxy from a MyProxy server?

AFAIK, no. You can create one and donate it back to Kepler source.

> Eventually, humankind will end up again with as many solutions for one 
> problem as many people point their attention on solving it. So Kepler, and 
> other such front-end tools, will have to provide as many blackbox tools (i.e. 
> actors), as many projects they support.
> C'est la vie.

That's why I would like see only general enough actors (functions) be 
included in Kepler. And the other specific-purpose actors should be packed 
as plug-in packages.

> The real benefit for me would be if it were not me who has to implement an 
> actor to satisfy my needs.

I would like to get that benefit too. But as far as I can see in the near 
future, Kepler still needs both developers/programers and end users. There 
must be somebody to do the "dirty work".

> Is flexible GAMA enough to put an
> 1. existing,
> 2. DOEGrids certificate into the MyProxy component of the
> 1. existing GAMA server with
> 2. a different CACL
> and create a user/pwd for me? So that I can get the proxy easily.
> Then comes the question whether the admins of that GAMA allow us to do that 
> (planting an alien certificate in their system).
> So this is the way round: you do not need to integrate DOEGrids into the 
> authentication framework but you need to let an existing GAMA accept my 
> certificate.

I am not the right person to answer this question. I will forward it in 
another email to the GAMA team in SDSC.


More information about the Kepler-dev mailing list