Here’s my personal experience exploring how to make this setup.
Installation take place on both sides Ayon/OpenPype and deadline.
Prerequisites
you should have a running deadline server.
🛠️ Install Deadline Server and Client
The best way to start learning about deadline is from Deadline official tutorials.
The following steps are the minimal installation required for this guide:
If you are running Ayon Launcher live from source, you’d like to use the ayon_console.bat it’s in tools folder inside Ayon Launcher Repo. Note, this assumes you are running the ayon launcher in production mode. ayon dev mode is going to have its separate guide.
OpenPype Installation Directories : base folder where all openpype version are installed, (you can keep it as it is if you didn’t change installation path while openpype installation)
OpenPype executable : path of openpype_console.exe, (you don’t have to use it unless you are running OP from source)
We installed the deadline as a service client during installation and added a couple of lines in deadline.ini (C:\Users\XXXX\AppData\Local\Thinkbox\Deadline10\deadline.ini), so we don’t have to worry about opening the .exe web service
"Another approach to keep the webservice running, is to have it as a job on the farm. You can then setup a redundancy machine to pick up the webservice job if the main machine fails. "
If you push a new installation of OP, you’ll need to update OpenPype Executable in the Deadline plugin path.
I didn’t need to update OpenPype Installation Directories
It’s possible to leave OpenPype Executable empty because the GlobalJobPreLoad should retrieve the OpenPype executable path from OpenPype Installation Directories, read more.
However, it didn’t work for me so that I had to set the executable explicitly!
I’m encountering an error in Deadline for Nuke render. It’s indicating a “bad value for display & view process.” during the review render baking. Is there any known fix for this problem?
@mustafa_jafar the guide is missing the part when you need to create a new service user with API key to be entered into the Ayon plugin in the Deadline.
I scratched my head a bit with recent DL version where connection to webservice didn’t work. (It failed in my tests in browser and in it was failing with 401 in ValidateDeadlineConnection).
The issue was that newer versions of DL set Require Authentication in Web Service Settings (in Tools > Configure Repository Options...), I had to disable it.
I’m pretty sure when using ayon core 0.3.0+ this shouldn’t touch the openpype addon. Make sure to set openpype in the bundle to None.
Instead of openpype_3.18.6 it should touch ayon_core_0.3.0 or alike.
Also, are you sure you updated Deadline’s GlobalJobPreLoad.py file? It does seem like a recent version, but just checking whether you might have missed also updating that.
Also, you’d need to update the Deadline addon.
You might not hit that issue yet. but, I thought about shedding some light on it.
There’s an issue that will probably vanish when splitting the Addons into separate repos.
The issue: client code of deadline is inside ayon-core but its associated settings is in deadline addon.
and when updating ayon-core the new client code of deadline may expect new settings e.g. I got some missing key error not_verify_ssl and that key only exists in the recent deadline addon.
Hey Guys! Need some information about your deadline setups.
When we installing deadline do you copy the ceritificate (Deadline10Client.pfx) locally in each machine in C:/ drive or do you use network UNC paths and also do you connect with map drive or UNC path in repository settings.
So far we are using the UNC path and I frequently face issues with deadline webservice especially, getting authetication issues “HTTP ERROR 401”. I believe I’m loosing something.
I’m pretty sure the webservice itself should not touch UNC paths at all because it connects to just a server’s port, not a path. So UNC versus mapped drive should be irrelevant there. This sounds like it may be in the realm of Deadline support itself.
When do you get the error? And do you have a stack trace describing where AYON may be causing it?
I think this is deadline issue, I’m testing without the AYON only, I can able to connect to deadline web service using localhost but not the IP.
My port was open in the machine and IP I’m trying to access is also correct.
I believe this is more of “HTTP ERROR 401” an authentication problem, not sure how to tackle it. I get this once or twice everymonth, I basically overwrite the installation everytime, this is frustrating!
These seem like firewall issues - not sure if @Petr_Kalis or @mustafa_jafar have seen this before with Deadline but if not I think you may be better off hearing from Deadline support or their community.
I don’t know much about Deadline installation.
Basically, I only followed these three videos.
For reference, I’ve my deadline server installed on a windows virtual machine
and used main PC as deadline worker. I don’t think I touched the firewall.
Also, I didn’t need to touch the certificates.
