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

[Michael Wilde]

Mihael, I want to also bring this development task back to your attention. It may need some further discussion on swift-devel.

Can you send an update about any issues?

We should make sure that the changes you make fit into and support the evolving scripts for coaster execution, so that your effort on this is directly useful to the end user tools.

Justin and Ketan have both looked at those tools lately and may want to comment.

- Mike

----- Forwarded Message -----
From: "Michael Wilde" <wilde at mcs.anl.gov>
To: "Mihael Hategan" <hategan at mcs.anl.gov>
Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>
Sent: Friday, March 18, 2011 9:58:47 AM
Subject: Re: Proposal for coaster service options

----- Original Message -----
> On Thu, 2011-03-17 at 23:43 -0500, Michael Wilde wrote:
> > > > 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 I'm misunderstanding the issue.
> 
> Are you referring to having the standalone service configured for
> passive mode?

Yes. The original mail I sent, proposing new command line options, was referring entirely to the coaster-service command.

In a later email, I realized that some of those issues might apply to the coaster service when running within the swift command's jvm as well.

- it seems that some or all of port management options (for setting and reporting port numbers) may apply to swift as well

- its likely that the option to set passive *does not* apply, as it already works. I think I was confused on the various combinations when I brought that up. Since currently we get the standalone service to enter passive mode by running a swift script that has passive mode set in the sites entry for that service, I realized on reflection that setting the passive option when the coaster service is running with the swift command JVM *must* be working correctly. It would be good to verify and create tests for this, but that is my current assumption.

Related to all this: I think that to do this job fully, we need to complete the set of wrapper commands that make manually run coasters an end-user-ready feature. And then to create scripts in the test framework to verify that they work. That will take more discussion, specification work, and devel time. But I feel we need to now get this feature completed and working, as there is user need for it.

Mihael, if you can get the changes into coaster-service and the swift command, I think others can get the wrapper scripts done and tested.

There is I think a prototype for this command support somewhere (Justin, you reminded me of these a few days ago: can you point out where they are?)

- Mike

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