Re: [Condor-users] Running a persistent, common 'initialization' job: possible?

["Jason Stowe" <jstowe@xxxxxxxxxxxxxxxxxx>]

Mark,
There are many different ways to accomplish this initialization,
depending upon the specifics of what kind and the reasons for your
initialization, . You could use the STARTD_CRON functionality. Create
a STARTD_CRON job that runs with a very large period, a couple of
billion seconds should do, so that it effectively it only runs when
the STARTD starts up .This wouldn't be a "Job" per se, but you could
put the slots in an "Owner" state while it ran. Once the STARTD_CRON
runs you could set your START expression to True.

Depending upon the topology of your pool, you could also create jobs
for an accounting group with very good priority, and have the jobs run
first with on_exit_remove to false. Using this method, it might be
somewhat difficult to *guarantee* that these jobs runs first,
depending upon the other jobs/policies in your pool.

There are other ways of guaranteeing initialization, including
wrapping the condor_master or the condor_startd, using the
USER_JOB_WRAPPER to verify the node is initialized before processing a
job, etc. etc. What are the specifics of your use case? Those will
determine which one of these you use.

Hope this helps,
Jason


-- 
===================================
Jason A. Stowe
cell: 607.227.9686
main: 888.292.5320

Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools

http://www.cyclecomputing.com
http://www.cyclecloud.com

On Tue, Jul 1, 2008 at 4:26 AM, Mark V <mvyver@xxxxxxxxx> wrote:
> Hi Group,
> I'd appreciate if anyone can indicate if the following is feasible,
> and how it might be acheived most elegantly:
>
> Scenario:
> A computer starts as a work-only machine, connects to the Condor
> master and runs a generic 'initialization' job.
> This job should be persistent, that is, it is not removed so that if N
> workers commence at or a round the same time they all run the same
> initalization job.
>
> Appreciate any comments or insights.
>
>  Mark
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>