Date: | Thu, 16 Jun 2016 13:31:33 -0400 |
---|---|
From: | Nick Ton <linusbeagle@xxxxxxxxx> |
Subject: | Re: [HTCondor-devel] condor_startd protocol... |
Thank you Brian and TJ for your inputs. To Brian, at the moment I am not planning to have the android devices as submitting clients. My understanding of HTCondor may be very elementary so I apologize in advance but I think that condor_schedd is for managing job submission. For job submission, I think I could use HTCondor SOAP protocol? To TJ, I don't know mind slogging through code, especially if I can get some guidance from the community. I'm happy to share what I have learn. Based on your suggestion, I'll start digging into the code. I've done a little digging around already. So in the condor_daemon_core.V6 directory, it seems that the condor_startd has a notion of Starter (extends Service), and StarterMgr, which manages multiple Starters? So condor_startd represents the executing node, and a Starter is represents a specific resource? In this case is a Starter represent 1 CPU core on the executing machine? Thanks Again! Nick On Thu, Jun 16, 2016 at 1:03 PM, Brian Bockelman <bbockelm@xxxxxxxxxxx> wrote: Hi Nick, |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [HTCondor-devel] condor_startd protocol..., Luca Rei |
---|---|
Next by Date: | Re: [HTCondor-devel] condor_startd protocol..., Nick Ton |
Previous by Thread: | Re: [HTCondor-devel] condor_startd protocol..., Nick Ton |
Next by Thread: | Re: [HTCondor-devel] condor_startd protocol..., Nick Ton |
Indexes: | [Date] [Thread] |