Heya
I’m just testing and trying to see how it works.
So the deadline 6 Beta have a build in amazon instancing management system. But how about deadline 5? We tried installing deadline on amazon but the instances that pop up were under 1 name(in Slave list there was only 1 node. Both nodes in deadline slave had the same name). So if we had 2 jobs then they both were rendering at the same name using 2 nodes but under 1 node name or so…
Any hints? Is it even legal actually to use deadline 5 trial/our licenses to use with amazon servers?
Thanks, bye.
Deadline 5 should run in the cloud just fine. You need to make sure your instances have unique host names though. If they don’t, they’ll all appear as the same slave, like you’re seeing.
There is nothing in our EULA that limits your ability to use your Deadline licenses in the cloud.
Cheers,
Lovely, in that case I have to find a way to automatically change EC instance name to its IP so that deadline can see my nodes. Or can I somehow tell deadline to create node per incoming connection with (0),(1) suffixes if nama repeats?
How well will deadline then manage jobs to nodes ? Will it render and assign jobs as fast as with different name/per node?
Thanks, bye.
Deadline runs under the assumption that every slave machine is uniquely named, and there really isn’t a way to hack around that. So probably best just to ensure the instances are named accordingly.
Once the slaves are uniquely named, the job management issues you saw before should go away.
Cheers,