On Tue, Jun 21, 2011 at 08:25:21AM -0400, Chris Lalancette wrote:
On 06/21/11 - 10:58:45AM, Jan Provaznik wrote:
As condor matching process (when starting an instance) was moved to
[snip]
API requests. Any reason why not replace whole condor with some other more ruby friendly solution? There is a bunch of nice projects for running async tasks in ruby.
While I agree with you to some extent, condor does do more than that. It also monitors the jobs for health. And while we could replace it, we do have a bunch invested in it, and I don't see a compelling reason to remove it at the moment. Ruby-friendly is not a reason :).
I understand that we invested alot of effort to make it work, but condor is for something that does not really belong to us. His job can be done by a bunch of other systems. I try to explain myself better. We are using an elephant to open a peanut. With a simple queue system (even an enterprise level one, like ActiveMQ or Qpid/QMF) and simple _dumb_ agents developed in all the languages we want, we can manage, delayed jobs, the health of instances, and a bunch more of things without too many headhaches. I agree with you, the Ruby-friendly is not a reasonable reason to move from it, but increasing the complexity of the whole project just because we want to use it, even if we just use the `% (to be optimistic) of their power, gonna surely to damage the whole project since each time we have to _guess_ what is not working, dealing with state machine or other things.
Cheers, Francesco Vollero