Using Licenses on AWS Slaves

Deprecated Deadline 10 Discussion
1

Hi Guys,

Thank you again for your help on getting a Blender render through. Happy to report no issues with that.

Since confirming that rendering Blender jobs work now, I’ve moved onto getting Houdini with Mantra rendering working. I’ve updated my custom AMI to have houdini 15 on it and sorted out some missing lib files. Now I’m getting issues with forwarding houdini licenses to the cloud based slave.

I am receiving the following in the log file for the slave:
2017-09-01 10:23:40: 0: STDOUT: No licenses could be found to run this application.
2017-09-01 10:23:40: 0: STDOUT: Please check for a valid license server host

Our Houdini license server isn’t available to the internet (inward bound) but it can reach the internet. I’ve followed the documentation as closely as I could. Is there anything we need to do here in order to get the licenses from our server to be recognized by the cloud slave? Like configure our firewall or the deadline license forwarder?

Kind regards,
Tom

2

I believe there’s an area to configure which ports you want to have forwarded from your local network.

I’m setting things up on my side so I can go digging for a screenshot, but I’ll ask some folks to reply here in case I get distracted.

3

Hey Tom,

Did you click the add Server button in the AWS Portal Settings and add the ip and port of your houdini/mantra server? You will need to setup your render nodes licensing to point to 10.128.2.4:port. Use the port you specified in the AWS Portal Settings entry.

Regards,

Charles

4

The port forward list entries in AWS Portal Settings could really stand to have a user-set label field added, so we know what licenses we think we’re serving through which port.