On 06/01/11 - 09:37:20PM, Tomas Von Veschler wrote: > Hi Chris, > > One point that doesn't convince me too much is to use the condor id > as instance name. If for example using rhev, a sys admin will prefer > to have the VMs named like the user named it in Aelous, not really a > bunch of numbers/hash.
Actually, I agree with you to a large extent. However, I have not been able to convince upstream condor (where I have to get condor patches accepted) about this. The reasoning is that the condor name is used as a unique handle to the instance. Consider: 1) Aeolus submits the job to condor. 2) Condor generates the name (something like Condor_<hostname>_uniquejobid). 3) Condor writes the name to the internal database; note that it does *not* have an ID yet, because we haven't submitted the job to deltacloudd yet. 4) Condor submits the job to deltacloudd. 5) Before it can get the status back from deltacloudd, condor crashes. 6) On restart, condor can find the job again by looking up the unique name that it generated. It can then start monitoring the job again. It's not possible to do 6) if you use the user-generated name, because it is not necessarily unique enough. I haven't yet come up with an alternate way to handle the above scenario, although I am definitely up for ideas. -- Chris Lalancette
