Collecting information on your render management workflows

[ddneilson]

Hello!
We (the team behind Open Job Description) are very interested in learning more about how you use, and want to use, your render farm and render management software. Our goal is for Open Job Description to act as a portable job description standard that can be used by anyone on any render farm, anywhere. We feel that our odds of meeting that goal are improved by learning as much as we can about how you want to use your render farm, and working with you to improve the standard to meet your needs.

We encourage you to use this discussion thread, or new discussion topics, to share whatever you can about your render farm workflows.

To seed the discussion, here are some things to think about:

• What sorts of things do your render farm workflows do?
• How are your workflows structured?
• What sorts of parallel execution patterns do you take advantage of? What would you like to take advantage of if it was available?
• Do you take advantage of an event system (e.g. automatically do X when Y happens in the farm)? Would you like to? What sorts of events are useful to you?
• Do you make use of cross-platform jobs/workflows (i.e. jobs that can run on either windows or posix/linux)? If so, what sorts of things do those cross-platform jobs do? Are parts of the workflow configured to run on any platform, or is the workflow achieved by doing different parts on different platforms in certain orders?
• Do your jobs have metadata attached to them? What form does that metadata take? How do you use that metadata?

Thank you,
Daniel