System Requirements
Qube! Requirements Checklist
If you are having installation or usage problems, make sure these items are present:
- All computers with OS installed, licensed, and networked.
- Hostname resolution (DNS) working properly on all computers.
- Authentication infrastructure installed and working:
- NIS / YP / LDAP for Linux
- OpenDirectory for macOS
- ActiveDirectory for Windows
- Network filesystem reachable by Client and Worker machines. Alternatively if no authentication infrastructure is in place please ensure open read and write privileges are set.
- While not strictly necessary, the Supervisor can also benefit from access to the network file system to allow Writing Job Logs to a Network Filesystem
- All applications (Maya, AfterEffects, etc.) already installed on the clients and workers and licensed.
- Appropriate versions of Python and Perl are installed on the supervisor and workers.
Python3 (3.6 to 3.10) is a prerequisite for all installations. It should be installed on each system prior to running the Qube! Installer.
-
Ideally a Qube! Local repository has been pre-populated for all operating systems that will need to be installed. Please watch this YouTube video on how this is done.
-
If a network account is to be used for the worker proxy_account, this account should already have been created and granted permission to the shared file system.
-
You must have administration privileges to install the software.
- For Windows users, you may want to right-click > "Run as Administrator" or just log in as the Administrator.
- For Linux users, you must run as root or a sudoer.
- macOS users will be prompted to enter an admin password before installation begins.
-
Supervisor must have a consistent IP address, either via a static IP address or DHCP reservation.
-
Current Qube! Supervisor license issued for the correct MAC address.
Supervisor Specifications
Below is a recommendation of minimum specifications for optimal operation of Qube! Supervisor.
| 1 - 25 workers | 26 - 75 workers | 75 - 150 workers | 150 - 300 workers |
|---|---|---|---|
|
|
|
|
Please note that beyond 30 render nodes you will need to alter qb.conf to optimize performance.
1-25 workers
#================================================================================
# Example qb.conf settings for a supervisor managing between 1-25 workers
#================================================================================
# This is not meant as a complete qb.conf, these are only the settings which
# should ~differ~ from the defaults.
#================================================================================
# the upper bound on the number of supervisor processes
supervisor_max_threads = 100
# the lower bound on the number of supervisor processes
supervisor_idle_threads = 10
# the number of transactions a single supervisor process will handle before it retires
supervisor_max_clients = 256
# global supervisor configuration parameters
#
# "host_recontact" (enable supervisor to recontact host marked DOWN)
# "heartbeat_monitor" (enable supervisor to track hosts using worker heartbeat packets)
# "remove_logs" (enable log removal after job removed)
# "running_monitor" (enable the Supervisor to track running jobs more actively)
#
supervisor_flags = host_recontact,heartbeat_monitor,running_monitor,remove_logs
26-75 workers
#================================================================================
# Example qb.conf settings for a supervisor managing between 26-75 workers
#================================================================================
# This is not meant as a complete qb.conf, these are only the settings which
# should ~differ~ from the defaults.
#================================================================================
# the upper bound on the number of supervisor processes
supervisor_max_threads = 100
# the lower bound on the number of supervisor processes
supervisor_idle_threads = 25
# the number of transactions a single supervisor process will handle before it retires
supervisor_max_clients = 256
# global supervisor configuration parameters
#
# "host_recontact" (enable supervisor to recontact host marked DOWN)
# "heartbeat_monitor" (enable supervisor to track hosts using worker heartbeat packets)
# "remove_logs" (enable log removal after job removed)
# "running_monitor" (enable the Supervisor to track running jobs more actively)
#
supervisor_flags = host_recontact,heartbeat_monitor,running_monitor
76-150 workers
#================================================================================
# Example qb.conf settings for a supervisor managing between 76-150 workers
#================================================================================
# This is not meant as a complete qb.conf, these are only the settings which
# should ~differ~ from the defaults.
#
# As well, please contact PipelineFX technical support if you need help tuning
# your MySQL server to support a farm of this size.
#================================================================================
# the upper bound on the number of supervisor processes
supervisor_max_threads = 200
# the lower bound on the number of supervisor processes
supervisor_idle_threads = 30
# the number of transactions a single supervisor process will handle before it retires
supervisor_max_clients = 256
# global supervisor configuration parameters
#
# "host_recontact" (enable supervisor to recontact host marked DOWN)
# "heartbeat_monitor" (enable supervisor to track hosts using worker heartbeat packets)
# "remove_logs" (enable log removal after job removed)
# "running_monitor" (enable the Supervisor to track running jobs more actively)
#
supervisor_flags = host_recontact,heartbeat_monitor,running_monitor
151-300 workers
#================================================================================
# Example qb.conf settings for a supervisor managing between 151-300 workers
#================================================================================
# This is not meant as a complete qb.conf, these are only the settings which
# should ~differ~ from the defaults.
#
# As well, please contact PipelineFX technical support if you need help tuning
# your MySQL server to support a farm of this size.
#================================================================================
# the upper bound on the number of supervisor processes
supervisor_max_threads = 250
# the lower bound on the number of supervisor processes
supervisor_idle_threads = 50
# the number of transactions a single supervisor process will handle before it retires
supervisor_max_clients = 256
# global supervisor configuration parameters
#
# "host_recontact" (enable supervisor to recontact host marked DOWN)
# "heartbeat_monitor" (enable supervisor to track hosts using worker heartbeat packets)
# "remove_logs" (enable log removal after job removed)
# "running_monitor" (enable the Supervisor to track running jobs more actively)
#
supervisor_flags = host_recontact,heartbeat_monitor,running_monitor