[Swift-devel] Re: Proposal for coaster service options

[Michael Wilde]

> > One other item that came up in yesterday's meeting was the set of
> > command line features to add to coaster-service (and to swift itself
> > which we didnt mention) to put the integrated coaster service into
> > passive mode and to make it save port numbers in a file for
> > integration with scripts.
> >
> > That might be a good task to do soon if its easy/feasible.
> 
> Yes. Seems like a quick and useful thing to have. Though doesn't the
> sites.xml scheme work in this case?

By "this case" do you mean the case where the coaster service is running in the Swift JVM? I.e. from jobmanager=local:something in the coaster pool entry?

I think we may need to check on that case - I cant recall how it behaves.

- Mike


----- Original Message -----
> Sounds good. These make sense.
> 
> Mihael
> 
> On Thu, 2011-03-10 at 08:27 -0600, Michael Wilde wrote:
> > Mihael,
> >
> > I want to work with Ketan to make the various coater startup scripts
> > that we've developed suitable and documented for end user use.
> >
> > As a start, can you consider something like the following
> > enhancement to coaster-service:
> >
> > -L Go into passive mode
> > -s service port
> > -S file to write service port number to
> >     (forces dynamic port selection starting with -s port number)
> > -w passive worker connection port
> > -W file to write worker port to
> >     (forces dynamic port selection starting with -s port number)
> >
> > This would make the startup scripts much simpler and cleaner: we
> > would not have to run a dummy swift script to force the service to
> > go into passive mode, and we would not have to scrape the standard
> > output for the passive port number, and we could control whether we
> > use a fixed port or a dynamically selected port.
> >
> > - Mike
> >

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory