Setup guide

rendering nodes are connected over a dedicated background TCP/IP network. Render nodes can access media
through NFS mount points, or by using the faster and recommended BrowseD service. See Configure Lustre
BrowseD (page 151).
You can have up to eight render nodes on the background rendering network.
Background rendering components
Lustre The client. Lustre rendering jobs are submitted for background rendering through the Render >
Backburner menu.
Backburner Manager The hub of the background rendering workgroup. It can reside on a master station
or Lustre station, or can be installed on a dedicated machine in your network. When jobs are submitted
from Lustre to Backburner Manager, Backburner Manager breaks each submitted job into tasks and distributes
the tasks to the rendering servers on the network. To view the progress of the tasks, use Backburner Monitor.
Backburner Web Monitor The user interface for the Backburner rendering network. It is installed with
Backburner Manager. It allows you to view and control jobs currently being processed.
Backburner Server A server that runs on render nodes. It is installed with Burn for Lustre. Backburner Server
accepts commands from Backburner Manager to start and stop rendering tasks. Backburner Server
communicates through a plug-in to execute rendering tasks. See the Backburner documentation webpage.
Burn for Lustre The Linux rendering engine that renders one or more frames from Lustre render jobs. Burn
for Lustre is a different software than Burn for Creative Finishing software. While they can co-exist on the
same node, the installation and configuration procedures are different. For information about how to set
up Burn for Creative Finishing software, consult the Autodesk Burn Installation and User Guide.
Shared storage mount point This is the mount point on each Linux server that allows Burn for Lustre to
transfer rendered frames/files to the Lustre storage system. The storage does not have to be mounted on the
Lustre Background Rendering | 153