Subject: Re: [Condor-users] DAG submission using Condor SOAP webservice
unsubscribe
From: "Belai Beshah"belai.beshah@xxxxxxxxx Sent:Mon, 18 Jun 2012 06:50:59 +0530 To: Matthew Farrellee matt@xxxxxxxxxx, Condor-Users Mail List condor-users@xxxxxxxxxxx Subject: Re: [Condor-users] DAG submission using Condor SOAP webservice Thanks Matt for the suggestion. Tried it using simple ping job and the result are as follows:
>
> 1. If done using out of the box windows install with the dynamic " condor-reuse-slot1" user, it fails when it tries to submit with the same error as the SAOP("ERROR: No credential stored for condor-reuse-slot1@..."). It looks like the problem is with the submitter machine being able to use the dynamic credentials of " condor-reuse-slot1"
>
> 2. If we change the submitter and node to run with a specific domain user by adding the following configuration to the "condor_config.local" to map the slots as " SLOT1_user = <domain user>" and made sure that this domain user has its credentials stored using " condor_store_cred add" on both the submit and runner nodes. We get a different error as " Failed to initialize user log to C:\condor\execute\dir_3680\ping-A-141.log " . Don't know why it can't create the log since we have verified that domain user has full read/write permission on the condor execution directory.
>
> Got the same error as above with or without "-remote". As always submitting Job B by hand on the submitter machine works ok in both configuration. We have been trying different ideas for a Job submitting another Job problem and are wondering if this problem is specific to clipped windows version or a not supported use case in general ? Any solution or suggestion to try is highly appreciated since we have exhausted all the options we can think of.
> Subject: Re: [Condor-users] DAG submission using Condor SOAP webservice
>
> If you condor_submit Job A (no SOAP), can Job A submit Job B?
>
> Try with and without -remote.
>
> Best,
>
>
> matt
>
> On 06/15/2012 06:24 PM, Belai Beshah wrote:
> > Looks like the problem is not DAG, it is actually any kind of job submission from another Job. So submitting Job A using SOAP Web Service and having it run on a Submitter machine and try to submit another Job B fails with "ERROR: No credential stored for condor-reuse-slot1@...".
> > Is there something fundamental we are missing or Is it that Condor Job submitting another Job is not supported in windows ?
> > Subject: RE: [Condor-users] DAG submission using Condor SOAP
> > webservice
> >
> > The problem is with automatic running of the DAG on the submit machine. The SOAP is working as expected and does submit and start Job A correctly.
> >
> > I will like to try your suggestion but there are a couple of hurdles we have not yet built a means of submitting a DAG using SOAP and also the modification to the application that submits the dag will require changes by another group. I am still not sure it will work though since it will still require being able to submit a DAG Job from the submitter machine without a human being logged into that machine.
> > Subject: Re: [Condor-users] DAG submission using Condor SOAP
> > webservice
> >
> > On Thu, Jun 14, 2012 at 08:39:53AM -0400, Belai Beshah wrote:
> >> Thanks Todd for the suggestion but looking at the two pointer
> >> carefully our problem seems different. What we have is we submit let
> >> say Job A using SOAP and when Job A runs it calculates the
> >> dependencies required based on the input dataset and tries to submit
> >> a DAG let say Job B. From the outside java client that uses the SOAP
> >> API we don't know what the DAG dependencies are and cannot directly
> >> generate the DAG for Job B, so we have to submit the Vanilla Universe
> >> Job A to figure the dependencies out and submit a DAG job using not
> >> the SOAP api but directly calling "condor_submit_dag" when it runs.
> >> The problem we are facing is a Vanilla universe job running
> >> successfully on a submitter machine is not able to submit a DAG. We
> >> can see that the DAG files get created correctly, it is only the
> >> "condor_submit_dag" that is failing. If we log to the submit machine
> >> we can manually submit the DAG file created by Job B successfully.
> >>
> >
> > It seems like what you want to do is have a dag as follows JOB A
> > create_analysis.cmd SUBDAG EXTERNAL B analysis.dag PARENT A CHILD B
> >
> > If a pre script is appropriate here, use:
> > SUBDAG EXTERNAL B analysis.dag
> > SCRIPT PRE B create_analysis
> >
> > A will compute the necessary dependencies and prepare the analysis dag for B.
> >
> > I am confused whether this is a SOAP problem or a DAG problem.
> >
> > Nathan Panike
> >
> >> We tried forcing condor to use a specific user all the time on the submit machines by adding " SLOT1_user =<UID domain user>" for a domain user that has its cred stored but still no luck.
> >> Subject: Re: [Condor-users] DAG submission using Condor SOAP
> >> webservice
> >>
> >> After a quick read of the below, it sounds as if you are submitting DAGMan as a vanilla universe job and therefore having it run under the starter on an execute node. Typically DAGMan is run as a scheduler universe job under the schedd, no startd involved.
> >>
> >> Essentially your soap submission should submit a scheduler universe job to a schedd, the executable should be dagman, and you should move all files (dagman input file, all the node submit files, and all the files referenced in those submit files) via the SOAP file staging calls.
> >> Also perhaps helpful is this URL, which talks about how to submit dagman into a grid universe (you'll want to use SOAP to the scheduler universe, but several of the concepts/ideas are the same):
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}