Hi,
Got a request to configure a mapped path on the local farm to do a find’n’replace on the render output paths, which is fine to do in combination with RegEx/Case Sensitivity. However, they would also like to ‘only’ affect the transfer jobs (jobs dropped) from one of our satellite offices. So, I need to check if the job was one that was transferred instead of being locally submitted.
Thoughts on best way to achieve this? (in v5.2 but also in v6 if possible!)
Thanks,
Mik
We are adding an extra info attribute to each job with the “submission office ID” in it, and use that in scripts that need to handle transferring of results, wrangling of paths etc.
One thing that might also help but is probably not an easy option, is to unify the central server names. We did that at frantic (and also here at scanline), with the local dns servers always pointing to the local data server when asking for the central name. So something like:
dataserv would point to dataserv.facilityA.com in facilityA, but to dataserv.facilityB.com in facilityB.
Then you just have to make sure that you wrangle the external references to only use the shortname (dataserv), and not the fully qualified name. And also, make sure the dependencies / output folders etc actually exist in each location 
cheers,
l
Thanks Laszlo.
I was thinking the same thing…add an extra info KEY=VALUE pair and track the office ID, then use a preLoad.py to handle the path wrangling if it identifies the job as being ‘foreign’ to the local repository.
I’m just wondering if this is something which Deadline core should be supporting (tracking) for us…as we all seem to be slowly moving towards a very distributed business model, whether it be satellite offices or a cloud office…it might even be time to overhaul the TransferJob plugin system as well, so it supports this shift in working as well…
Thanks,
Mike
Yeah would be nice actually… We have our own transfer api with a complicated backend infrastructure / services etc, so would probably want something where we could leave that, but use deadline’s base functionalities to hook into it somehow.
lets get back to this topic after Siggraph 2013!