Slashdot Mirror


Open Source Batch Management?

Asgard asks: "My employer is currently running a commercial batch management platform. Unfortunately the licensing model makes it unfeasible to run it in the development / testing environments, leading to poor usage of the tool and unexpected failures in production. I'm looking for an equivalent Open Source tool and am wondering how others have approached the problem. Does Slashdot have any suggestions?" Imagine a system like cron, but with job dependencies. Are there any batch systems out there like this? "The tools I've found through web searches mostly treat 'batch management' from the cluster perspective -- a user submits an ad-hoc job and the tool figures out where and when to run it based on load and architecture requirements. Instead I am looking for something that manages daily schedules of jobs based on their dependencies with other jobs and external events, such as files arriving or time.

An example might be that every day jobs a, b, c, and d must run. Job a must not run before 9pm and requires file X to be present. Jobs b and c depend on a completing successfully. Job d must run after 2am and after b and c have completed successfully. If job c fails then an operator must fix the issue and rerun it, after which the tool will move on to job d. "

4 of 37 comments (clear)

  1. For a second there ... by one9nine · · Score: 3, Funny

    I thought it said Open Source Bath Management.

    Maybe I speak for myself, but some things are better off left proprietary.

  2. DOS by Anonymous Coward · · Score: 1, Funny

    Wouldn't FreeDOS work? I have a bunch of batch files that work in MSDOS.

  3. Re:Systems like this are handy by OldAndSlow · · Score: 2, Funny
    ... I was able to write a universal decoder for it using only vbscript and Excel.

    And you just adimtted to the world that you violated the DMCA. Pity, I was starting to like you...

  4. Re:Sounds familiar by Anonymous Coward · · Score: 1, Funny

    Complications: running on Windows 2000 platform, zero budget and a lot of the jobs will run 16 bit apps in a NTVDM.

    What, the project manager couldn't squeeze "devs must hit themselves in the balls with a hammer each hour" into the requirements list?