Setup guide

Lustre Background Rendering
During background rendering, a shot on the timeline is rendered by a background rendering network. This
is different from Shot Reactor, which renders shots on a shot-by-shot basis as they are colour graded to
enable improved playback performance.
Background rendering in Lustre is done with Burn for Lustre, also known as the Lustre Background Renderer.
This application is specific to Lustre and provides asynchronous background processing of Lustre render
jobs. By off-loading rendering activities to remote Linux servers, Lustre stations are freed up for interactive
colour grading, while background rendering is sped up by splitting the task amongst multiple hosts.
General workflow for installing and configuring background rendering:
1 If you are not using BrowseD, Share the storage for rw access from background render nodes (page 154).
2 Install Backburner Manager (page 107) and Backburner Monitor (page 86)
3 Configue Lustre to detect Backburner Manager (page 157).
4 Set up render nodes (page 154).
5 Specify the Background Rendering path in Lustre (page 157).
Configure Lustre BrowseD
About BrowseD
BrowseD is a Lustre file server with its own high level protocols that optimize network transfers. BrowseD
provides Lustre workstations, Slave Renderers, and background render nodes with high-speed access to
centralized storage, especially if your network uses InfiniBand, without mounting the storage on the render
nodes.
Consider using BrowseD if your facility uses a storage area network (SAN), network attached storage (NAS),
or a network file server. In these configurations, you install and configure BrowseD on the computer that
is connected to the centralized storage and configure all workstations to use the BrowseD server to access
Lustre project files.
The recommended Lustre configuration in a digital film or high-resolution workflow is to store the
full-resolution images on a SAN, NAS, or file server, and the proxies locally.
You can run BrowseD on the Lustre Master Station to provide render nodes or Slave Renderers high-speed
access to local storage for background rendering. However, this is not recommended. The BrowseD process
requires extra bandwidth from the storage and adds extra load on the host system's CPU. Real-time
functionality cannot be guaranteed with this setup—2K playback speed and video input and output will
not function correctly when BrowseD is running on the Lustre workstation, and is serving client requests.
If you are working with StandardFS DPX or Cineon footage coming from the local Wiretap Server, you must
mount your storage on the render nodes.
BrowseD startup and configuration:
1 The BrowseD service starts automatically after you install it. You can manually start the service using
the command line interface. The service starts automatically whenever the computer running BrowseD
restarts.
/etc/init.d/browsed_ <version> stop Stops BrowseD.
/etc/init.d/browsed_ <version> start Starts BrowseD.
/etc/init.d/browsed_ <version> restart Restarts BrowseD if it is not currently running.
Lustre Background Rendering | 151