[Swift-devel] give name to PBS job

[Sarah Kenny]

apparently this didn't get implemented because i *think* what was happening
is that when mihael added in my fix it then caused problems in gram2 if you
tried to submit something and failed/forgot to set that parameter:

On Tue, 2010-10-05 at 14:31 -0500, Sarah Kenny wrote:
> On Tue, Oct 5, 2010 at 12:58 PM, Mihael Hategan <hategan at mcs.anl.gov>
> wrote:
>         I think I committed some changes based on your patch. One
>         problem was
>         that gram2 doesn't seem to support a job name. Did you find a
>         way around
>         that?
>
> hmm, it is working on abe (gram2) and queenbee (gram5)...were you
> getting an error running it elsewhere or did it just not pick up the
> name? i'm thinking if it works for some gram versions and not others
> it might be ok to commit unless it actually causes an error in
> versions where the name is not passed (?)

That was the problem. It caused an error.

On Wed, Jun 29, 2011 at 12:14 PM, Michael Wilde <wilde at mcs.anl.gov> wrote:

> I was referring to this enhancement from Sarah:
> ---
> From: "Sarah Kenny" <skenny at uchicago.edu>
> To: "Swift Devel" <swift-devel at ci.uchicago.edu>
> Sent: Tuesday, October 5, 2010 12:26:18 PM
> Subject: [Swift-devel] new commits
>
> hi all, i have a fix to swift that allows the jobName parameter to be
> passed to GRAM (so the job name actually shows up in the queue). this will
> be my first commit to the cog/swift source so i want to know where the best
> place is to do this? i'd like it to be in the stable release so that it's
> there when we update. my user group (HNL) has been using the stable branch
> with this fix added for several months so it's pretty well-tested.
>
> i guess the question is would it be best to commit this to the development
> code (which as i understand is cogkit/trunk/current) to be migrated to the
> stable code (cogkit/branches/4.1.7) in the near future when we decide to
> update the stable branch?
>
>
> ----- Original Message -----
> > I'll take a look at that method then. Mike just mentioned that he
> > thought the ability to name your coaster workers was already
> > implemented so I emailed the list.
> >
> > On Jun 29, 2011, at 1:56 PM, Justin M Wozniak wrote:
> >
> > >
> > > I looked at this a little bit. One thing is that Coasters generates
> > > its own block names when it decides to get an allocation, and these
> > > names correspond to useful Coasters identifiers. Another is that
> > > there is a 15-character limit. However, it still could be done by
> > > modifying PBSExecutor.makeName().
> > >     Justin
> > >
> > > On Wed, 29 Jun 2011, Jonathan Monette wrote:
> > >
> > >> Hello,
> > >
> > >>  I think I mentioned this before but is there a way to assign a
> > >>  name to a PBS job in Swift? Something like:
> > >>
> > >> <profile namespace="globus" key="job-name">some.name</profile>
> > >>
> > >> and then some.name would show up on qstat? This would be useful to
> > >> see which workers are from what Swift run when checking qstat.
> > >> _______________________________________________
> > >> Swift-devel mailing list
> > >> Swift-devel at ci.uchicago.edu
> > >> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
> > >>
> > >
> > > --
> > > Justin M Wozniak
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20110629/62f2f7ca/attachment.html>