[Swift-devel] Configuring standalone active coasters service

Tim Armstrong tim.g.armstrong at gmail.com
Sat Aug 16 22:10:07 CDT 2014


Thanks, that helps.  CC'ing list again since I dropped it earlier.

 - Tim


On Fri, Aug 15, 2014 at 9:45 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> On Fri, 2014-08-15 at 19:32 -0500, Tim Armstrong wrote:
> > Just checking my understanding...  Do the coaster options you send over
> the
> > wire correspond directly to the options {} dict here:
> >
> http://swift-lang.org/guides/trunk/userguide/userguide.html#_configuration_file_structure
> >
> > I.e. options in:
> >
> > execution {
> >     type: "coaster"
> >     jobManager: "local:local"
> >     options {
> >         maxJobs: 1
> >         tasksPerNode: 2
> >         workerLoggingLevel: TRACE
> >     }
> > }
>
> Yes, except the jobOptions are also flattened and sent along with the
> other ones.
>
> >
> >
> > Also, how do you set parameters specific to the jobManager, e.g. if
> you're
> > submitting through pbs:local, how do you set the PBS queue?
>
> Those are attributes. So everything that isn't specifically a coaster
> setting will be passed to the job.
>
> Mihael
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140816/903b3d1e/attachment.html>


More information about the Swift-devel mailing list