[Swift-devel] persistent coaster service

Mihael Hategan hategan at mcs.anl.gov
Mon Sep 20 18:23:51 CDT 2010


On Mon, 2010-09-20 at 15:27 -0500, Allan Espinosa wrote:
> If the workers have a head node different from the coaster service,
> then we only have option (b) right?

Yes and no. The coaster service cannot right now start workers on a
different machine, but I don't see why that couldn't be possible in
theory (and therefore in some future version of the code).

As usual, virtual cookies for the actual code.

Mihael

> 
> -Allan
> 
> 2010/8/26 Mihael Hategan <hategan at mcs.anl.gov>:
> 
> >> 2) Following up on Allan's last question, can you clarify:
> >>
> >> When you start a persistent coaster service do you have the option of either:
> >>
> >> (a) the Swift client starts workers per the sites.xml profile settings or
> >>
> >> (b) the user starts the workers manually, connecting to the persisten server, when you specify workerManager passive in the Globus profile tag:
> >>
> >>   <profile namespace="globus"> key="workerManager">passive</profile>
> 
> 
> 





More information about the Swift-devel mailing list