You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deadline has a feature whereby remote commands can be issued to a Worker from a Monitor.
By default, the Deadline Worker listens on a random port for these commands. However, random ports are not compatible with AWS Security Groups & Network ACLs -- they force very wide range of ports to be open that might not otherwise be required to be open.
The ask is to provide a means by which the customer can configure the worker's remote command port during a deployment so that Security Group & Network ACL rules can be configured.
Use Case
Simply, any customer that might want to do a least privileged farm deployment and be able to use Deadline Remote Commands. e.g. Any Amazon Nimble Studio customer.
Proposed Solution
This may be tricky. Unlike the log-listening port, Deadline does not have an ini setting for configuring the Worker's remote command listening port. Instead, it is a global repository option -- see "Override Remote Command Port".
So, options include:
Adding functionality to Deadline to allow local configuration of the Worker's Remote Command Port via deadline.ini and then setting it, like we do for the Log Streaming port, when configuring a Worker via RFDK; or
Setting the 'Override Remote Command Port' during deployment via the RFDK; or
Something else working with the Thinkbox devs to rework remote commands in Deadline.
👋 I may be able to implement this feature request
⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered:
Deadline has a feature whereby remote commands can be issued to a Worker from a Monitor.
By default, the Deadline Worker listens on a random port for these commands. However, random ports are not compatible with AWS Security Groups & Network ACLs -- they force very wide range of ports to be open that might not otherwise be required to be open.
The ask is to provide a means by which the customer can configure the worker's remote command port during a deployment so that Security Group & Network ACL rules can be configured.
Use Case
Simply, any customer that might want to do a least privileged farm deployment and be able to use Deadline Remote Commands. e.g. Any Amazon Nimble Studio customer.
Proposed Solution
This may be tricky. Unlike the log-listening port, Deadline does not have an ini setting for configuring the Worker's remote command listening port. Instead, it is a global repository option -- see "Override Remote Command Port".
So, options include:
deadline.ini
and then setting it, like we do for the Log Streaming port, when configuring a Worker via RFDK; orThis is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: