Dagobah's features compared to chronos or azkaban? about dagobah

[thieman]

Hey there! Unfortunately, I'm not familiar with chronos or azkaban, but by a quick glance at their product pages they seem to be good examples of why other scheduling projects weren't great fits for me. Namely:

• Azkaban, like a bunch of other schedulers, was created with a specific task in mind (managing Hadoop jobs). Spotify's Luigi, and a bunch of others, also seem to target map-reduce workflows. Dagobah is meant to be pretty much a cron replacement.
• Chronos is a cron replacement! That's awesome, but it seems like total overkill for what I needed to do. I wanted something simple that I could run on one machine to manage my nightly analytics updates.

Now, to your questions:

1. Could you go into a bit more detail here? Dagobah is currently made for running on one machine, so if you want to influence other machines you'll need to do that in a different framework. Fabric, as you suggest, or something like Celery would be good for this. If I'm misunderstanding you, please let me know.
2. The task logs do get permanently stored in your backend. There's no way to examine them currently in the web app, though.
3. Yes! This is a good idea. I'll make an issue for it.

[utsengar]

Azkaban, like a bunch of other schedulers, was created with a specific task in mind (managing Hadoop jobs). Spotify's Luigi, and a bunch of others, also seem to target map-reduce workflows. Dagobah is meant to be pretty much a cron replacement. Chronos is a cron replacement! That's awesome, but it seems like total overkill for what I needed to do. I wanted something simple that I could run on one machine to manage my nightly analytics updates.

This is the exact reason why I liked dagobah. Its simple and is flexible enough to be used for other usecases. I am also looking for a cron replacement. Azkaban is meant for hadoop job automation but it can also act as a cron replacement (with retries, DAG etc). Chronos is awful and completely an overkill.

Could you go into a bit more detail here? Dagobah is currently made for running on one machine, so if you want to influence other machines you'll need to do that in a different framework. Fabric, as you suggest, or something like Celery would be good for this. If I'm misunderstanding you, please let me know.

You got it right. Dagobah currently runs on one machine. But I am trying to add fabric to Dagobah so that it can execute commands on a remote machine. Celery is good too, but the management overhead is less if I just use fabric and execute remote commands.

The task logs do get permanently stored in your backend. There's no way to examine them currently in the web app, though.

Good to know, I will try to expose this data in the web app.

[utsengar]

I have added remote task execution here: https://github.com/utkarsh2012/dagobah/blob/master/dagobah/core/core.py#L634 it works nicely with the existing stuff (UI needs some work like updating remote machine endpoint, needs tests). It uses paramiko and spawns processes for every remote request.

What do you think?

[thieman]

Hey @utkarsh2012, this looks awesome! I will review your branch when I get some time and get back to you.

[utsengar]

Looks like Travis CI build is broken, missed to add dependency for paramiko in setup.py and requirements.txt.

Also the UI might need some work, I hacked up the solution in a day to see how will it work. I might submit more fixed if I find bugs.

[rclough]

Did this ever get included? I can't seem to find remote options in the web UI

[levonk]

Just a minor correction, Azkaban can be used for anything, not just Hadoop based Map-Reduce. It can be used only as a superior cron (dependencies, transparency, partial workflows, etc...) only. You don't need hadoop at all.