I’m wondering if you can elaborate a bit on the impact of the Proxy on our kind of network (eg. 14 studios spread across all regions).
We had originally hoped to use one database / repository per geographic region, to overcome latency concerns, but have had to abandon this idea until such time as we can get a global namespace working. At the moment we are pursuing a ‘one database / repository per studio’ typology, which is more complex and harder to maintain.
Would the Proxy allow us to run one database / repository globally, with a proxy in each region instead, or am I misunderstanding?
The Proxy Server acts as a middle man between the Deadline applications and the Database/Repository. It allows workstations and render nodes to connect to a remote Deadline farm without the need of a VPN, or if a VPN is in place, they don’t need direct file share access to the Repository, or a direct connection to the Database.
So in your case, the Proxy Server would run in the same location as the Database/Repository, and each region would connect to it instead of connecting to the Database/Repository directly. Systems like Nginx could be used to handle load balancing, and even SSL security if required.
I’ve attached a PDF that shows how the Proxy fits in in the case where remote render nodes are connecting to an on-premise render farm.
Hope this helps! Let me know if you have any questions.