installation and conﬁ guration guide for linux...

Installation and Confi gurationGuide for Linux Workstations

Autodesk® Lustre® 2011A Discreet® systems product

®

Autodesk® Lustre® 2011

© 2010 Autodesk, Inc. All rights reserved. Except as otherwise permitted by Autodesk, Inc., this publication, orparts thereof, may not be reproduced in any form, by any method, for any purpose.

Certain materials included in this publication are reprinted with the permission of the copyright holder.

TrademarksThe following are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and other countries:3DEC (design/logo), 3December, 3December.com, 3ds Max, Algor, Alias, Alias (swirl design/logo), AliasStudio, Alias|Wavefront (design/logo),ATC, AUGI, AutoCAD, AutoCAD Learning Assistance, AutoCAD LT, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface,Autodesk, Autodesk Envision, Autodesk Intent, Autodesk Inventor, Autodesk Map, Autodesk MapGuide, Autodesk Streamline, AutoLISP, AutoSnap,AutoSketch, AutoTrack, Backburner, Backdraft, Built with ObjectARX (logo), Burn, Buzzsaw, CAiCE, Civil 3D, Cleaner, Cleaner Central, ClearScale,Colour Warper, Combustion, Communication Specification, Constructware, Content Explorer, Dancing Baby (image), DesignCenter, DesignDoctor, Designer's Toolkit, DesignKids, DesignProf, DesignServer, DesignStudio, Design Web Format, Discreet, DWF, DWG, DWG (logo), DWGExtreme, DWG TrueConvert, DWG TrueView, DXF, Ecotect, Exposure, Extending the Design Team, Face Robot, FBX, Fempro, Fire, Flame, Flare,Flint, FMDesktop, Freewheel, GDX Driver, Green Building Studio, Heads-up Design, Heidi, HumanIK, IDEA Server, i-drop, ImageModeler, iMOUT,Incinerator, Inferno, Inventor, Inventor LT, Kaydara, Kaydara (design/logo), Kynapse, Kynogon, LandXplorer, Lustre, MatchMover, Maya,Mechanical Desktop, Moldflow, Moonbox, MotionBuilder, Movimento, MPA, MPA (design/logo), Moldflow Plastics Advisers, MPI, MoldflowPlastics Insight, MPX, MPX (design/logo), Moldflow Plastics Xpert, Mudbox, Multi-Master Editing, Navisworks, ObjectARX, ObjectDBX, OpenReality, Opticore, Opticore Opus, Pipeplus, PolarSnap, PortfolioWall, Powered with Autodesk Technology, Productstream, ProjectPoint, ProMaterials,RasterDWG, RealDWG, Real-time Roto, Recognize, Render Queue, Retimer, Reveal, Revit, Showcase, ShowMotion, SketchBook, Smoke, Softimage,Softimage|XSI (design/logo), Sparks, SteeringWheels, Stitcher, Stone, StudioTools, ToolClip, Topobase, Toxik, TrustedDWG, ViewCube, Visual,Visual LISP, Volo, Vtour, Wire, Wiretap, WiretapCentral, XSI, and XSI (design/logo).FFmpeg is a trademark of Fabrice Bellard, originator of the FFmpeg project.All other brand names, product names or trademarks belong to their respective holders.

DisclaimerTHIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AUTODESK, INC. “AS IS.” AUTODESK, INC. DISCLAIMSALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE REGARDING THESE MATERIALS. Published by: Autodesk, Inc.111 Mclnnis ParkwaySan Rafael, CA 94903, USA Title: Autodesk Lustre 2011 Installation and Configuration Guide for Linux WorkstationsDocument Version: 1Date: April 1, 2010

Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 Installation Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Workflow for Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Workflow for Installing from Scratch or Upgrading Linux . . . . . . . . . . . . . . . . . . . . . . . . . 4Workflow for Connecting New Stone Direct Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3 Setting Up Your Workstation Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Typical Configuration Overview for Autodesk Lustre . . . . . . . . . . . . . . . . . . . . . . . . 8Lustre Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Overview of Peripheral Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Connecting the Autodesk Control Surface to a Lustre Workstation . . . . . . . . . . . . . . . . . . . 11Connecting Video Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Connecting Audio Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ?Wiring Audio Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Connecting Media Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Connecting the Fibre Channel Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Connecting Stone Direct Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Connecting XR 6500 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Connecting XR 6412 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Connecting XR 5402 and XR 5412 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Connecting the Slave Renderer to a Lustre Workstation . . . . . . . . . . . . . . . . . . . . . . . . . 21Configuring your System BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Checking the BIOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4 Installing Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Do I Need to Reinstall Linux? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Linux Installation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Linux Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring Basic Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Assigning an IP Address to the Autodesk Control Surface . . . . . . . . . . . . . . . . . . . . . 30

Chapter 5 Installing the DKU and the AJA OEM-2K Firmware . . . . . . . . . . . . . . . . . . . . . . 33Installing the DKU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Upgrading the AJA OEM-2K Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 6 Configuring Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

iii

Do I Need to Perform these Procedures? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Powering Up Your Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Partitioning the Storage and Creating the XFS Filesystem . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 7 Installing Lustre on the Linux Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . 43Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Installing Lustre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 8 Licensing and Starting the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Licensing Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Determining the Licenses You Require . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Obtaining the Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Requesting License Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Entering License Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Starting the Application for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 9 Configuring Slave Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Workflow for Configuring Slave Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Configuring the Slave Renderer Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Installing the Slave Renderer Software and License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Configuring Read/Write Access to Storage from the Slave Renderer . . . . . . . . . . . . . . . . . . . 51Mounting the Storage on the Slave Renderer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Setting Up Lustre Projects to Use Slave Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 10 Configuring Background Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55About Background Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Background Rendering Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Workflow for Setting Up Background Rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Sharing the Storage for Read/Write Access from Background Render Nodes . . . . . . . . . . . . . . . 57Installing Backburner Manager and Backburner Web Monitor . . . . . . . . . . . . . . . . . . . . . . 58Setting Up Render Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Render Node Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . 59Installing Linux on Render Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Mounting the Storage on the Render Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installing and Configuring Burn for Lustre on Render Nodes . . . . . . . . . . . . . . . . . . . 62

Configuring Lustre to Detect Backburner Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Specifying the Background Rendering Path in Lustre . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 11 Configuring BrowseD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67About BrowseD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Workflow for Configuring BrowseD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Starting and Stopping the BrowseD Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring Workstations to Use the BrowseD Server . . . . . . . . . . . . . . . . . . . . . . . . . . 68Making BrowseD Directories Accessible from the Lustre Browser . . . . . . . . . . . . . . . . . . . . 69Using BrowseD for Rendering with Burn for Lustre . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Using BrowseD with the Slave Renderer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Appendix A Uninstalling the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Uninstalling your Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Appendix B Software, Project, and User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . 73Configuration File Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Appendix C Manually Configuring Media Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Creating Hardware LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Partitioning Disks or LUN devices as Primary Partitions . . . . . . . . . . . . . . . . . . . . . . . . . 82Assembling the Disk or LUN Devices into a Logical Volume . . . . . . . . . . . . . . . . . . . . . . . 84

iv | Contents

Creating the XFS Filesystem on the Logical Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Manually Creating a Mount Point and Mounting the Storage . . . . . . . . . . . . . . . . . . . . . . 87

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Contents | v

Introduction

Topics in this chapter:

■ About This Guide on page 1■ Intended Audience on page 1■ Related Documentation on page 2■ Notation Conventions on page 2■ Contacting Customer Support on page 2

About This GuideThis guide provides information about installing Autodesk® Lustre® 2011 software on the hardwarecomponents in your Lustre system. Use this guide in conjunction with the Hardware Setup Guide for yourplatform to install and configure the hardware and software components of your Lustre system.

NOTE In most cases, both hardware setup and application installation is done on delivery by an authorizedtechnician, so you may not need to perform all of the procedures in these guides.

Intended AudienceThis guide assumes you have knowledge of the Linux® operating system, preferably a distribution from RedHat® Linux. It also assumes familiarity with Linux networking terms, tools, and procedures.

If you plan to reconfigure your workstation or your storage, knowledge of computer hardware, storage andnetworking in a professional video/film production environment is recommended.

Do not attempt to carry out the procedures in this guide if you are not familiar with the concepts theypresent. Contact Autodesk Media and Entertainment Customer Support if you require further assistance.

1

1

If you are upgrading an existing workstation without reinstalling the operating system, this documentassumes you have root access to your system. If you do not have root access, contact your system administrator.The default root account password on an Autodesk workstation is password.

Related DocumentationThe complete documentation set is available in PDF (Portable Document Format). You can access the PDFfiles from the Documentation folder of the Lustre software disc, or fromhttp://www.autodesk.com/lustre-documentation.

NOTE For the best results viewing and printing PDF files, use Adobe® Acrobat® Reader™ 6 or later. You candownload a free copy of Acrobat Reader from the Adobe Web site (http://www.adobe.com).

Notation ConventionsA number of style conventions are used throughout your documentation. These conventions and examplesof their use are shown as follows.

ExampleConvention

install rpm -qaText that you enter in a command line or shell appearsin Courier bold. Press the Enter key after each com-mand.

<filename>Variable names appear in Courier, enclosed in anglebrackets.

limit coredumpsizeFeedback from the command line or shell appears inCourier.

/usr/discreetDirectory names, filenames, URLs, and command lineutilities appear in italics.

Contacting Customer SupportFor Autodesk Media and Entertainment Customer Support, visit http://www.autodesk.com/support.

Customer support is also available through your Autodesk reseller. To find a reseller near you, consult thereseller look-up database at http://www.autodesk.com/resellers.

2 | Chapter 1 Introduction

http://www.autodesk.com/lustre-documentation

http://www.adobe.com

http://www.autodesk.com/support

http://www.autodesk.com/resellers

Installation Workflows


■ Overview on page 3■ Workflow for Upgrading the Software on page 3■ Workflow for Installing from Scratch or Upgrading Linux on page 4■ Workflow for Connecting New Stone Direct Storage on page 6

OverviewYour system is shipped with the operating system and the software already installed.

This chapter highlights three common installation workflows that you may need to perform:

■ Workflow for Upgrading the Software on page 3

■ Workflow for Installing from Scratch or Upgrading Linux on page 4

■ Workflow for Connecting New Stone Direct Storage on page 6

For details on the workstation hardware setup, it is recommended that you visitwww.autodesk.com/lustre-documentation, select your application and version, and download the HardwareSetup Guide for your workstation model.

Workflow for Upgrading the SoftwareFollow this workflow to upgrade your software to a new version, service pack, or extension withoutreconfiguring your hardware or reinstalling your operating system.

To determine whether you need to install a new version of Linux® for a new software version or hardwareplatform, see Do I Need to Reinstall Linux? on page 25. If you do need to upgrade Linux, follow the stepsin the Workflow for Installing from Scratch or Upgrading Linux on page 4 rather than this workflow.

2

3

www.autodesk.com/lustre-documentation

To upgrade the software:

1 Gather the following materials and documentation for your installation:

■ The Discreet Kernel Utilities (DKU) installation package. For major releases, the DKU is available onthe application DVD. If you are installing a service pack or an extension, download the DKU tar filefrom the link provided in the Release Announcement you received from Autodesk. The DKU alsocontain the files needed to upgrade your system BIOS and the firmware of the AJA OEM-2K card.

■ The Lustre software installation package. For major releases, the application is available on DVD. Ifyou are installing a service pack or an extension, download the application tar file from the linkprovided in the Release Announcement you received from Autodesk.

■ The Release Notes for the software version or service pack you plan to install. The Release Notescontain important procedures that you might need to perform before upgrading your software, aswell as information on supported hardware, required system memory, BIOS version, Linuxdistribution, DKU version and AJA OEM-2K firmware version.To download the latest Release Notes, go to www.autodesk.com/lustre-documentation, then select theversion or service pack you plan to install.

2 Make sure the hardware still meets all the system requirements for the new software version or servicepack, as specified in the Release Notes for the version you plan to install.

3 Upgrade the Discreet® Kernel Utilities (DKU) to the required version. Refer to the latest Release Notesfor the required DKU version and for update instructions. DKU update instructions are also availablein Installing the DKU on page 33.

4 Update the AJA OEM-2K card firmware if necessary. Refer to the latest Release Notes for the requiredfirmware version and for update instructions. Firmware update instructions are also available in Upgradingthe AJA OEM-2K Firmware on page 34.

5 Install the software. See Installing Lustre on the Linux Workstation on page 43.

6 License your software, and start it for the first time. See Licensing and Starting the Application on page45.

NOTE Re-licensing is not necessary if you are upgrading to a service pack of the same software version or toa service pack of the same extension.

Workflow for Installing from Scratch or Upgrading LinuxFollow this workflow when you need to completely rebuild your system: from connecting the hardwareperipherals and storage arrays, to installing the operating system, and installing, licensing, and configuringthe software components.

Most of this workflow also applies when you need to reinstall or upgrade the operating system withoutchanging your hardware or storage setup. A new distribution of Linux may sometimes be required for a newversion or service pack of the software, or for newer hardware platforms. To determine whether you needto upgrade Linux for a new application version or hardware platform, see Do I Need to Reinstall Linux? onpage 25.

To install your system from scratch or upgrade Linux:

1 Gather the following materials and documentation for your installation:

■ The installation disc of the Red Hat® Enterprise Linux operating system. Visual Effects, Finishingand Colour Grading workstations ship with the custom Autodesk distribution of Red Hat EnterpriseLinux on DVD. For information on the version of Linux required for your hardware platform, seeDo I Need to Reinstall Linux? on page 25.

4 | Chapter 2 Installation Workflows


■ The Discreet Kernel Utilities (DKU) installation package. For major releases, the DKU is available onthe application DVD. If you are installing a service pack or an extension, download the DKU tar filefrom the link provided in the Release Announcement you received from Autodesk. The DKU alsocontain the files needed to upgrade your workstation BIOS and the firmware of the AJA OEM-2Kcard.

■ The Lustre software installation package. For major releases, the application is available on DVD. Ifyou are installing a service pack or an extension, download the application tar file from the linkprovided in the Release Announcement you received from Autodesk.

■ The Release Notes for the software version or service pack you plan to install. The Release Notescontain important procedures that you might need to perform before upgrading your software, aswell as information on supported hardware, required system memory, BIOS version, Linuxdistribution, DKU version and AJA OEM-2K firmware version.

■ The Hardware Setup Guide for your workstation. This document contains detailed information onsetting up your workstation.

To download documentation, go to www.autodesk.com/lustre-documentation, then select the version orservice pack you plan to install.

2 Make sure the hardware meets all the system requirements.

3 If you are installing your hardware perform the following tasks:

■ Verify your hardware shipment, and make sure your facility meets the documented power and airconditioning requirements for the hardware components.

■ Connect all peripherals (mouse, keyboard, graphics monitor, house network) to the proper portson the workstation.

■ Connect the Control Surface to the proper ethernet and USB ports on the workstation.

■ Connect a VTR and a broadcast monitor to your workstation.

■ Connect and configure the audio hardware for your workstation.

■ Connect your storage arrays to the workstation, but DO NOT power them on before having installedLinux, to prevent the Linux installer from attempting to format the arrays and use them as systemdrives.

NOTE Instructions and wiring diagrams for each of these steps can be found in Setting Up Your WorkstationHardware on page 7.

4 If necessary, update and configure the BIOS of your workstation. See Configuring your System BIOS onpage 21.

NOTE The BIOS settings must be properly configured before installing Linux.

5 Install the required Autodesk distribution of Red Hat® Enterprise Linux. See Installing Red Hat EnterpriseLinux on page 25.

6 Perform the tasks in Linux Post-Installation Tasks on page 28 to configure your operating system.

7 Install the required version of the Discreet Kernel Utility (DKU). Refer to the latest Release Notes forthe required version and for update instructions. DKU update instructions are also available in Installingthe DKU on page 33.

8 Update the AJA OEM-2K card firmware on your workstation if necessary. Refer to the latest ReleaseNotes for the required firmware version and for update instructions. Firmware update instructions arealso available in Upgrading the AJA OEM-2K Firmware on page 34.

Workflow for Installing from Scratch or Upgrading Linux | 5


9 If you are using a new Stone® Direct storage array, configure the RAID volumes, mount the storage,and format it. See Configuring Storage on page 37 for LUN creation instructions and XFS filesystemcreation instructions.

10 Install the software. See Installing Lustre on the Linux Workstation on page 43.

11 License your software, and start it for the first time. See Licensing and Starting the Application on page45.

NOTE Re-licensing is not necessary if you are upgrading to a service pack of the same software version or toa service pack of the same extension.

Workflow for Connecting New Stone Direct StorageFollow this workflow when you need to rebuild your Stone Direct storage array. For instance, this may berequired when you purchase supplementary storage enclosures to expand available disk space.

NOTE You do not need to reinstall or re-license the software after changing your storage configuration.

To connect new or expanded Stone Direct storage:

1 Connect your storage enclosures to the workstation. See Connecting Media Storage on page 15.

2 Configure the RAID volumes and mount the storage. See Configuring Storage on page 37 .

3 Your new storage is now ready to use.

6 | Chapter 2 Installation Workflows

Setting Up YourWorkstation Hardware


■ Overview on page 7■ Overview of Peripheral Connections on page 11■ Connecting the Autodesk Control Surface to a Lustre Workstation on page 11■ Connecting Video Components on page 13■ Connecting Audio Components on page 13■ Connecting Media Storage on page 15■ Connecting the Slave Renderer to a Lustre Workstation on page 21■ Configuring your System BIOS on page 21

OverviewThis section contains wiring diagrams for HP® Z800 workstation peripherals, video hardware, and storage,as well as BIOS settings. For detailed information about the workstation, including power consumption, airconditionning requirements, rack mount requirements, and BIOS upgrade procedures, consult the latestversion of the Autodesk Visual Effects and Finishing HP Z800 Workstation Hardware Setup Guide.

NOTE If you are only upgrading an existing application, you do not need to reconfigure your hardware.

This section does not contain information and diagrams for the older workstations supported in this version.For detailed information about setting up each workstation, see the Hardware Setup Guide for the respectiveworkstation.

WARNING Before working with hardware components, make sure to read the safety guidelines in the HardwareSetup Guide. Hardware setup should only be performed by an experienced technician.

3

7

Typical Configuration Overview for Autodesk LustreA Lustre system consists of a number of different hardware and software components. This section describeseach of the hardware components in a Lustre installation, and the software associated with each component.You may or may not have all of the components listed here in your Lustre setup. The type of workgroup,as well as the feature set you purchase for each of the workstations in that workgroup, determine thecomponents in your installation.

Lustre WorkstationsThere are three kinds of Lustre workstations: the Master Station, the HD Station, and the Lustre Station.Every Lustre installation is built around either a Master Station or an HD Station. The optional Lustre Stationoffers a way to improve the efficiency and cost-effectiveness of a pipeline by offloading tasks that do notrequire the full feature set of the Master Station or HD Station.

Master Station

The Master Station is designed for GPU-accelerated sessions where the colorist works together with thecinematographer. It includes an extensive creative toolset for elaborate visual design and grading, using upto 4K resolution and 16-bit files and for completing tasks like dust busting, conforming, rotoscoping, andcapture/playout. It also includes SD and HD I/O, dual link and HSDL video formats, and the film workflowfeatures, which consist of infrared channel dust removal and support for all standard input and outputresolutions and bit-depths.

The Master Station can support up to three panels of the Autodesk Control Surface and, with an additionallicense, a Slave Renderer.

HD Station

The HD Station is a cost-effective GPU workstation for conforming, preparing, grading, and masteringshort-form and long-form HDTV projects, as well as HD film projects, and mastering to different formats.It does not include the film workflow features. File input is limited to 10-bit 2K resolution, and file outputis limited to SD and 10-bit HD resolution.

The HD Station can support up to three panels of the Autodesk Control Surface and, with an additionallicense, a Slave Renderer. Dual link and HSDL video formats are available with the purchase of a separatevideo I/O license.

Lustre Station

Tasks that do not require the direct intervention or supervision of the colorist can be efficiently handled bya Lustre Station. Multiple Lustre Stations can work in parallel to increase throughput and can be used fortasks such as dust-busting, preparatory work, fine-tuning creative sessions, conforming data from EDLs,updating editorial changes, and mastering to different formats using the real-time deliverables function.The Lustre Station includes the film workflow features, and the ability to create geometries and masks.

Primary colour grading on the Lustre Station requires a separate license. The following features also requirean additional license: SD and HD I/O, dual link and HSDL video formats.

The Lustre Station does not support the Slave Renderer.

Other ComponentsYou can expand the features of your Lustre system and improve the efficiency of your workflow by addingany of the following components.

8 | Chapter 3 Setting Up Your Workstation Hardware

Control Surface The Autodesk Control Surface provides improved interactivity when colour grading filmand video footage. You can perform many of the same tasks you do in the Lustre user interface using theControl Surface.

You connect the Autodesk Control Surface to a Master Station or HD Station, and configure the ControlSurface on the workstation to which it is connected.

Video I/O Card and Breakout Box On the HP Z800 workstation, video I/O is provided by the AJA card.The video I/O card consists of an HD/SD card and a breakout box. This configuration provides real-time SDIinput and output of uncompressed 8- or 10-bit HD or SD video in both YUV (4:2:2) and RGB formats (4:4:4or 4:2:2). For a list of supported video formats, see the Autodesk Lustre User Guide.

The drivers for the video card and breakout box are installed by the Discreet® Kernel Utility (DKU).

Slave Renderer The Slave Renderer is a rack-mounted server that frees system resources by automaticallyoff-loading render tasks, thus ensuring real-time interaction on the Lustre system.

Connect the Slave Renderer to a switch on your house network. Note that only one Lustre Master stationor HD station can use it.

You install the Slave Renderer software package on the Slave Renderer.

Background Renderer Background rendering frees up Lustre workstations for colour grading. You can useup to eight background rendering machines to process your final frames.

You install background rendering software on each background render node.

Typical Configuration Overview for Autodesk Lustre | 9

The following illustration shows a typical Lustre workgroup configuration built around a Master Station. Itincludes a Lustre Station, and other optional components.

Lustre Station

Control Surface

Slave Renderer

Video I/O

Background Rendering (Burn)

Lustre Master Workstation

Lustre Storage

Peripheral Options

Network Options

HighHue Brightness Satur ation

G+ B+R+R G B Sh MidBrightBright

+G - B -R - -

Multi

Matt e O/P Stil l ALT

Wipe Spli t Proxy

.

Curve K eyP&SInside

MiscOutside

#0001.000019

InPr OutPrGeom

Grade

GRADE C URVESKEY G EOM P &S MISC MORE

MOREOUTIN

1

+/-

4

7

5 6

98

2

0

3

ALT

ENTER

CURSORREVERT

COMPUNDO

REDODO

RECALLOFFSET

GRADE

CLIPA/B

CUE

F1 F2F3 F4 F5

F6

F7 F8F9

ShadowContrast

Brightness

SAN options

Ref Loop

RS-422

SDI 1/A SDI 2/B

InOut

Ch.1(L) Ch.2(R)

Y/G/CVBS Pb/B/Y Pr/R/CVideo MonitorOut

Ch. 1/2 Ch. 3/4

InOut

Ch. 5/6

InOut

InOut

Ch. 1/2 Out Ch. 3/4 Out Ch. 5/6 Out Ch. 7/8 OutCh. 1/2 In Ch. 3/4 In Ch. 5/6 In Ch. 7/8 In

AES/EBUAudio

Ch. 7/8

AJA BOB (Front)

AJA BOB (breakout box)

Ref Loop

RS-422

SDI 1/A SDI 2/B

InOut

Ch.1(L) Ch.2(R)


Ch. 1/2 Ch. 3/4

InOut

Ch. 5/6

InOut

InOut


AES/EBUAudio

Ch. 7/8


Overview of Peripheral ConnectionsThe following diagram provides an overview of the adapter card positions, and illustrates how to connectperipherals, such as the graphics monitor, keyboard, mouse, Wacom® Intuos® pen tablet, and house network,to the HP Z800 workstation.

It is recommended you connect all hardware peripherals, as instructed in this chapter, before booting theworkstation for the first time.

HP Z800 Workstation

To keyboard, mouse,tablet, monitor calibrator

To house network

GigE Adapterto SAN and/or privatenetwork, Incinerator node

Atto Celerity FC84-ENto direct attached storage

Nvidia Quadro FX 5800

AJA OEM-2Kto video/audio i/o, VTR

Nvidia Quadro SDI Outputto reference monitor, Real-Time Deliverables VTR,sync generator

Power

InfiniBand / 10-GigE Adapterto Wire network (optional)

To graphics monitor

To Lustre control surface

Connecting the Autodesk Control Surface to a LustreWorkstationThe Autodesk Control Surface consists of three panels connected to the workstation’s on-board GigE port 1by way of the supplied network switch. The central panel requires an additional connection to the remoteunit of the USB extender kit.

Overview of Peripheral Connections | 11

This section provides information on making the physical connections needed to operate the AutodeskControl Surface. For information on using the Control Surface, see the Autodesk Control Surface User Guide.

1 3 4 5 6 7 8PWR

NETGEAR

2

Autodesk Control Surface

5V DC 4A Ethernet

Autodesk

Tablet

System

Power

Link Activity

-+

Network Switch

To USB extender

Ports 3 and 4 toadditional panels

To port 1 on USB Extender

HP Z800 Workstation

NOTE The illustration shows the central panel only (the Colour Grading panel). This panel is easily identified,since it has both an Ethernet network port and a USB connector. It is also the panel with the built-in tablet.

To connect the Autodesk Control Surface:

1 Connect each panel to a power supply using the AC power adapter cables.

2 Use network cables to connect each panel to the available ports in the network switch.

3 Additionally, connect the Colour Grading panel to the remote unit of the USB extender kit.

4 Use a network cable to connect an available port on the Netgear network switch to the workstation, asillustrated.

5 Refer to the application installation and configuration guide for instructions on assigning an IP addressto the Autodesk Control Surface.


Connecting Video ComponentsThe following diagram illustrates how to connect the video hardware components included in your shipment.The only video hardware you must provide are a sync generator, VTR, HD/SDI-ready broadcast monitor andpatch panel (if desired).

Ref Loop

RS-422

SDI 1/A SDI 2/B

InOut

Ch.1(L) Ch.2(R)


Ch. 1/2 Ch. 3/4

InOut

Ch. 5/6

InOut

InOut


AES/EBUAudio

Ch. 7/8

AJAwww.aja.com 102053

K3-Box

J1 In 1/A In 2/B Out 1/AConnect to Host

Out 2/B

AJA BOB (Front)AJA BOB (Back)

HD-SDI Out 1/A to 4:2:2 VTR (or 4:4:4 dual link)

HD-SDI In 2/B to 4:4:4 VTR (dual link 0:2:2)

HD-SDI In 1/A to 4:2:2 VTR (or 4:4:4 dual link)

HD-SDI Out 2/B to 4:4:4 VTR (dual link 0:2:2)

VGA DVIVGA

(not included)

SD/HD SDI IN 2

Graphics Monitor

SD/HD/SDI MonitorSD/HD SDI IN 1 AJA HD5DA

OUT 1 INPUT

OUT 2

Real-Time Deliverables or Stereo Output

To SD/HD SDILink A onVTR

"Key" to SD/HD SDI Link B,on VTR (for dual link)

cn

yS

ne

Gcn

yS

ne

G

from house sync generation(Trilevel/NTSC/PAL not included)

SD/HD SDI In / Out

SD/HD SDI In / Out

to RS-422 VTRmachine control

HP Z800 Video I/O

Sync loop out toNVIDIA Input

Control cable and power

"Fill" to Input

Connecting Audio ComponentsYour application uses the Discreet Native Audio subsystem. Discreet Native Audio uses the following hardwarecomponents, shipped with your system.

Connecting Video Components | 13

Lucid ADA 88192 Audio Converter Converts signals between the workstation and all digital or analogaudio I/O devices.

AJA Balanced Audio breakout box and AJA OEM-2K adapter card The Balanced Audio breakout box is theaudio component of the AJA breakout box. It provides connections for audio I/O. This breakout box connectsto the AJA OEM-2K adapter on your workstation. The OEM-2K adapter provides real-time input and outputof uncompressed SD and HD video signals as well as audio data at 24-bit resolution. The OEM-2K adapterhandles balanced AES/EBU audio signals from the Balanced Audio breakout box.

Wiring Audio ComponentsThe following diagram illustrates how to connect the Discreet Native Audio hardware components to theAJA breakout box.

Analog Inputs

AES/EBU Digital Outputs Analog Outputs3-4

1-2

1-25-67-8

3-45-67-8

12345678

12345678

AES/EBU Digital Inputs

RS-232

ADAT IN 1-8ADAT OUT 1-8

WORD CLOCKINPUT

OUTPUT

88192 A/D D/A CONVERTER

IN IN

OUT OUT

IN IN

OUT O UT

VTR

AUDIO

GPIIN OUT

IN DIGITAL AUDIO OUT

1/2 3/4 7/85/6 1/2 3/4 5/6 7/8

WClk CVBS RS.422D LTC

RS 422C

RS.422B

RS 422A

Ref Loop

RS-422

SDI 1/A SDI 2/B

InOut

Ch.1(L) Ch.2(R)


Ch. 1/2 Ch. 3/4

InOut

Ch. 5/6

InOut

InOut


AES/EBUAudio

Ch. 7/8

AJA

AJA BOB (Front)

Lucid ADA 88192Converter

to serial port 1 onLinux workstation

Required for remotecontrol of converter

Digitaloutputs

Input fromanalog source

Output toanalog destination

Digitaloutputs

Alternative setupconverted fromanalog source


Connecting Media StorageThe workstation can be connected to two types of media storage.

■ Stone Direct XR-series disk arrays Autodesk's high-performance direct-attached storage (DAS) solutiondesigned to address the different real-time playback requirements of various workflows. Direct attachedstorage devices provide storage to individual workstations.

NOTE A Lustre workstation equipped with Incinerator does not use DAS storage. Incinerator storage is attachedto the Lustre Media Server, accessed by way of the InfiniBand network.

■ A SAN A storage infrastructure that allows multiple workstations to share simultaneous access to acentral storage enclosure.

Connecting the Fibre Channel AdapterOn HP Z800 workstations, connections to media storage are made using the ATTO Celerity FC84-EN fibrechannel adapter, located in slot five (top to bottom).

NOTE If you need more storage connections, you can also have your HP Z800 workstation configured with asecond ATTO fibre channel adapter in slot 1, instead of the GigE adapter.

The fibre channel adapter is equipped with four ports, called loops. You can connect your storage enclosureto the fibre channel cards using either 2 loops or 4 loops. A 2-loop device can be connected to either theinner pair of ports or the outer pair of ports. A 4-loop device requires both the inner pair and the outer pair.

FC loop 2

FC loop 3To storage assembly

FC loop 4

FC loop 1To archiving device or SAN

FC Adapter

NOTE If you are not using all the ports of a fibre channel adapter, terminate the two unused ports with the FCloopback couplers that shipped with your system. Terminating these ports significantly decreases the time requiredto boot the system.

Connecting Stone Direct StorageThe diagrams in this section illustrate how to connect the fibre channel loops to the Stone Direct storageenclosures supported with your workstation. For technical details on each storage model, see the Storagechapter in the hardware setup guide.

Connecting XR 6500 StorageThe following diagrams illustrate 2-loop and 4-loops connections for XR 6500 series storage assemblies.Cable your storage exactly as illustrated to ensure proper functionality.

Connecting Media Storage | 15

A XR 6500 RAID enclosure supports a maximum of seven XE expansion enclosures. Configurations withtwo XR RAID enclosures are not supported.

WARNING Do not power on your storage before installing Linux®, otherwise the Red Hat® installer might attemptto format the storage array and use it as the system disk.

I0 I 0

0

00

0

00

I0 I 0

HOST 1

841/2

HOST 0

841/2

CAS

HOST1

841/2

HOST0

841/2

CAS

I0 I 0

0

00

0

00

I0 I 0

0

00

0

00

I0 I 0

0

00

0

00

XR RAID Enclosure

XE (EBOD)_Expansion Enclosure

XE (EBOD) Expansion Enclosure



Single XR 6500 RAID enclosure, 2 loopsTo FC adapter on workstation / LMS (port 1)

To FC adapter (port 2)

Cabling for additional enclosures


I0 I 0

0

00

0

00

I0 I 0

HOST 1

841/2

HOST 0

841/2

CAS

HOST1

841/2

HOST0

841/2

CAS

I0 I 0

0

00

0

00

I0 I 0

0

00

0

00

XR RAID Enclosure




Single XR 6500 RAID enclosure, 4 loops




To FC adapter on workstation / LMS (port 0)


NOTES:

■ In a 4-loop configuration, you need a minimum of one XE expansion enclosure attached to the XR 6500RAID enclosure.

■ The total number of enlcosures must be an even number.

Connecting Stone Direct Storage | 17

Connecting XR 6412 StorageThe following diagrams illustrate 2-loop and 4-loop connections for XR 6412 series storage assemblies.

A XR 6412 RAID enclosure supports a maximum of seven XE expansion enclosures. Configurations withtwo XR RAID enclosures are not supported.

WARNING Do not power on your storage before installing Linux, otherwise the Red Hat installer might attemptto format the storage array and use it as the system disk.



0 10

ID

0 10

ID

XR RAID Enclosure

0 !

0 !

FACTORYUSE ONLY

FACTORYUSE ONLY


0 10

ID

0 10

ID


0 10

ID

0 10

ID


0 10

ID

0 10

ID







0 10

ID

0 10

ID

XR RAID Enclosure

0 !

0 !

FACTORYUSE ONLY

FACTORYUSE ONLY


0 10

ID

0 10

ID


0 10

ID

0 10

ID


0 10

ID

0 10

ID






NOTE In a 4-loop configuration with a XR 6412 RAID enclosure, you need a minimum of one XE expansionenclosure attached to the XR RAID enclosure.

Connecting Stone Direct Storage | 19

Connecting XR 5402 and XR 5412 StorageThe following digrams illustrate 2-loop and 4-loop connections for XR 5402 and XR 5412 series storageassemblies.

XR 5402 and XR 5412 series storage assemblies support 2-loop configurations with one XR RAID enclosure,and 4-loop configurations with two XR RAID enclosures.

WARNING Do not power on your storage before installing Linux, otherwise the Red Hat installer might attemptto format the storage array and use it as the system disk.

To FC adapter on workstation / LMS (port 1)To FC adapter (port 2)

XR RAID Enclosure






Single XR 5402 / 5412 RAID enclosure, 2 loops


NOTE The XR 5402 and XR 5412 RAID enclosures support a maximum of four XE expansion enclosures.

XR RAID Enclosure XR RAID Enclosure

XE (EBOD) Expansion Enclosure XE (EBOD) Expansion Enclosure

XE (EBOD) Expansion EnclosureXE (EBOD) Expansion Enclosure




First storage assembly Second storage assembly

Two XR 5402 / 5412 RAID enclosures, 4 loops

NOTE In a configuration with two XR RAID enclosures, the number of XE extension enclosures per XR RAIDenclosure must be the same. The total number of enclosures in the storage assembly must be an even number.

Connecting the Slave Renderer to a Lustre WorkstationThe Lustre Slave Renderer is a single render node that provides automatic background rendering on ashot-by-shot basis. It is available for the Lustre Master Station, the Station, and the HD Station.

NOTE In comparison, Autodesk Incinerator provides “in-line” processing by several nodes at once. For moreinformation, see the Autodesk Incinerator Installation and User Guide.

Connect the Slave Renderer to a switch on your GigE house network. Note that the Slave Renderer can onlybe used by one Lustre workstation.

Although the Lustre Slave Renderer uses a standard GigE network connection, it requires the higher-bandwidthCat-6 cable, to accommodate the increased data that is transmitted.

To connect the Slave Renderer:

1 Connect one end of the Cat-6 cable to an available GigE port on your house network switch.

2 Connect the other end of the cable to one of the on-board GigE ports of the Slave Renderer machine.

Configuring your System BIOSThis section contains information on the certified BIOS settings for the HP Z800 workstation, as well asinstructions on updating your BIOS and restoring it to the default factory settings. For information onupdating your BIOS version, or reverting the BIOS to factory defaults, consult the Hardware Setup Guide.

Connecting the Slave Renderer to a Lustre Workstation | 21

NOTE The BIOS of your workstation is correctly configured prior to shipping, so you normally do not need toperform the procedures in this section.

Checking the BIOS SettingsAfter wiring the workstation and before installing Linux, turn the workstation on and check the BIOS versionand BIOS settings.

WARNING If BIOS settings are not set up correctly before installing Linux, you will need to reinstall the OS.

The certified BIOS version for your workstation is 3.07.

Make sure the BIOS version number that appears on screen while booting the workstation matches thecertified version. If the versions do not match, update the BIOS to the certified version, after configuringBIOS settings. BIOS update instructions are at the end of this chapter.

To adjust system BIOS settings, press F10 while booting the workstation.

The following table lists the Autodesk certified BIOS settings. Items not listed are set to their default factorysettings.

ValueItemSubmenuBIOS Menu

RAID+AHCISATA EmulationStorage OptionsStorage

Optical DriveBoot Order

USB Device

<hard drive model>Hard Drive

Integrated SATA

DisableRuntime Power ManagementOS Power ManagementPower

NormalIdle Power Saving

DisableMWAIT Aware OS

DisableACPI S3 Hard Disk Reset

DisableSATA Power ManagementHardware Power Management

DisableIntel Turbo Boost Technology

EnableHyper-ThreadingProcessorsAdvanced

EnableMemory Node InterleaveChipset/Memory

DisableNUMA Split Mode

DisableS5 Wake on LANDevice Options

DisableInternal Speaker

DisableNIC PXE Option ROM Download

DisableOption ROM DownloadSlot 1 PCIe2 x8(4)



ValueItemSubmenuBIOS Menu


DisableOption ROM DownloadSlot 6 PCI32

Checking the BIOS Settings | 23

Installing Red HatEnterprise Linux


■ Do I Need to Reinstall Linux? on page 25■ Linux Installation Workflow on page 26■ Linux Post-Installation Tasks on page 28

Do I Need to Reinstall Linux?Visual Effects, Finishing and Colour Grading workstations ship with the correct Autodesk distribution ofRed Hat Enterprise Linux already installed and configured. Thus, you should only need to install Linux inthe following situations:

■ You plan to upgrade your software on an older supported hardware platform running a version of RedHat Enterprise Linux no longer supported by the current version of the software. In this case, you mustperform a fresh install of the required Red Hat Enterprise Linux version.

■ Your system experienced an unrecoverable hard disk failure and you had to replace the system disk.

NOTE If you must replace the hard disk of your workstation, you need to obtain a new license. ContactCustomer Support for assistance.

Use the following table to determine the correct version of Red Hat Enterprise Linux required for yourhardware platform.

Linux VersionHardware Platform

Custom Autodesk distribution of Red Hat Enterprise Linux Desktop 5.3 withWorkstation Option

HP Z800

4

25

Linux VersionHardware Platform

Custom Autodesk distribution of Red Hat Enterprise Linux WS 4, Update 3HP xw8400, HP xw8600

To determine the version of Red Hat Enterprise Linux your system is currently running, open a terminaland type:

cat /etc/redhat-release

The Linux version appears. For example:

Red Hat Enterprise Linux Client release 5.3 (Tikanga)

If your system is not currently running the correct version of Red Hat Enterprise Linux, install the requiredversion of the operating system.

Linux Installation WorkflowPerform the following procedure to prepare your system and perform a fresh install of the customizeddistribution of Red Hat Enterprise Linux.

To install Linux:

1 Locate the installation media.

The DVD containing the customized Autodesk distribution of Red Hat Enterprise Linux is includedwith your shipment. The customized Autodesk distribution installs certain Linux packages that arerequired by Autodesk applications but are not installed by the commercial distribution of Red HatEnterprise Linux.

WARNING Even though your shipment may also include the disc set for the commercial distribution of RedHat Enterprise Linux, DO NOT install the commercial distribution. Autodesk Visual Effects, Finishing andColour Grading software only works on the custom Autodesk distribution of Red Hat Enterprise Linux.

2 Power off all storage enclosures connected to the system, to prevent the Red Hat installer from attemptingto reformat them as part of the installation process.

WARNING Do not skip this step. Failure to power off or disconnect your storage before installing Linux mayresult in data loss.

NOTE Turn off the XR RAID controllers first, then the XE expansion enclosures.

3 If you are reinstalling Linux on an existing system, back up all user settings, project settings, and mediafrom the system to another system or to a removable drive. The Linux installation erases and formatsthe system disk, so this information is lost if it is not backed up. In addition, back up the followingdirectories:

■ /usr/autodesk (for software setup and configuration files)

■ /etc (for Linux configuration files, networking, etc)

■ /usr/lib/DPS (for fonts)

■ /usr/local/flexlm/licenses (for the license file)

4 Make sure your system is in the following state:

■ Mouse, keyboard and graphics monitor are connected, and the graphics monitor is powered on.

26 | Chapter 4 Installing Red Hat Enterprise Linux

■ Other peripherals, such as the tablet and video breakout box are connected and powered on.

■ If you are using a KVM switch, it is switched to the system on which you want to install Linux.

■ The storage array is powered off.

■ The Lustre control surface is disconnected from the workstation.

5 Insert the DVD of the custom Autodesk distribution of Red Hat Enterprise Linux in the DVD-ROMdrive, and power off the system.

WARNING If your system is equipped with internal media storage, after turning the system off, open theside panel and disconnect the main connector for the internal storage drives. Make sure you do not disconnectthe system drive!

6 Restart the system.

7 When the system starts to boot, press F10 to enter the BIOS and make sure the BIOS settings reflect therecommended values in Setting Up Your Workstation Hardware on page 7. The BIOS must be correctlyconfigured before installing Linux.

NOTE If the keyboard is connected to the system through a KVM switch, you may have to press F10 repeatedlyor hold it down to enter the BIOS.

8 Save the correct BIOS settings and reboot the system.

The system should boot to the Linux installation disc. If it does not, review your BIOS settings to makesure the DVD / CDROM drive is set as the primary boot device.

9 When the Red Hat Linux installation screen appears, press F8 to display the Autodesk Red Hat Linuxinstallation menu.

10 At the boot prompt in the Red Hat Linux installation menu, type one of the following commands andthen press Enter to launch the Linux installation.

To install on:Type:

A Lustre workstation.lustrews

A Lustre Slave Renderer.lustreslave

A Burn® for Lustre node using the Autodesk custom DVD of Red Hat En-terprise Linux.

burnlustre

A Burn for Lustre node using the commercial CD/DVD of Red Hat Enter-prise Linux with the Autodesk kickstart file.

linux ks=cdrom

WARNING You must use this exact command to start the Linux installation. If you use the default optionspresented by the Linux installation prompt, the installation proceeds, but some important packages requiredby Autodesk software are not installed.

The command launches the Linux installation. The system spends several minutes loading drivers. Theinstaller guides you through the rest of the process.

11 The installation process may ask you to initialize the system disk. Follow the prompts to initialize thedisk, if necessary.

12 The remainder of the installation process is automated.

When the installation completes, you are prompted with “Congratulations, the installation is complete”.

Linux Installation Workflow | 27

13 Eject the disc and click Reboot to reboot the system. After the system reboots, perform thepost-installation tasks in the following section.

NOTE After the system reboots, you may be prompted by the Kudzu hardware setup utility to set up newhardware detected for your system. You can ignore these prompts and allow the utility's count-down toexpire since the hardware for the system is unchanged.

Linux Post-Installation TasksAfter booting into your new Linux installation, perform the following post-installation tasks:

1 Change the default root password to secure the system.

■ Log into your system as root, using the default password password.

■ Open a terminal and type:passwd

■ Enter your current password when prompted, and then enter the new password.

2 Configure the time zone for your geographic location. The automated Autodesk installation sets thetime zone to North American Eastern Standard Time (EST) by default.

■ Log into the Linux Desktop as root.

■ Right-click the clock, and select Configure Clock from the context menu.

■ Click the Timezones tab, and select the city closest to you from the list of locations.

■ Click Apply to save the new settings, and then click OK to close the window.

3 Configure the network settings for your system to match the ones used in your facility. The automatedLinux installation sets a default IP address and hostname for your system, which may not be suitablefor your facility network. See Configuring Basic Network Settings on page 28.

4 Configure the IP address of the Autodesk Control Surface. See Assigning an IP Address to the AutodeskControl Surface on page 30.

5 Install the Discreet Kernel Utilities (DKU), and upgrade the firmware of your AJA OEM-2K card. SeeInstalling the DKU and the AJA OEM-2K Firmware on page 33.

Configuring Basic Network SettingsThis section provides instructions on configuring your system network settings to match those of yourfacility.

Before configuring your network settings, gather the following information from your network administrator:

■ An available IP address on your network, to assign to your system. The IP must not change over time,and must not be used by any other system on your network.

■ A unique host name for your system.

■ The IP address of the gateway system on your network.

■ The subnet mask of your network.

■ The IP addresses of one or more DNS servers.


The following files contain the network settings of your Linux system.

DescriptionNetworking Configuration File

Contains global networking settings, such as the system hostname, Gateway IP address, and NIS domain name, if applic-able.

/etc/sysconfig/network

Contains DNS server information./etc/resolv.conf

Contains IP/host name pairs for host name resolution./etc/hosts

Contains interface-specific configuration./etc/sysconfig/network-scripts/ifcfg-eth<x>, where <x>specifies the ethernet port number, usually 0 for the first on-board port.

The following procedures provide instructions on setting up each configuration file. Log is as root beforeediting these files. When you are done changing the network settings, restart your system for the changesto take effect.

To configure the system hostname and default Gateway:

1 Open the /etc/sysconfig/network file in a text editor.

2 Make sure the NETWORKING keyword is set to yes.

3 Configure the HOSTNAME keyword with the hostname you want to use for your system. For example:

HOSTNAME=workstation1

4 Configure the GATEWAY keyword with the IP address of the gateway system on your network. Forexample:

GATEWAY=192.168.0.1

This is the global default gateway that will be used by the system if no gateway is defined in a networkport’s individual configuration file.

5 Save and close the file.

To configure the system IP address and netmask:

1 Open the /etc/sysconfig/network-scripts/ifcfg-eth<x> file in a text editor, where <x> is the number of thenetwork port your system uses to connect to the facility network, typically 0.

NOTE In most cases, the network port eth0 is the first on-board port on the back of your workstation. Notehowever that, if your workstation has an add-on Ethernet card installed, the Linux operating system mayassign ports eth0 through eth3 to the add-on card. In such a case, the on-board Ethernet ports become eth4and eth5.

2 Make sure the BOOTPROTO keyword is set to static.

BOOTPROTO=static

3 Set the IPADDR keyword to the IP address you want to use. Make sure this IP is not used by any othersystem on your network. For example:

IPADDR=192.168.0.100

NOTE It is not recommended to change this IP address once you have installed your Autodesk software.

4 Set the NETMASK keyword to the netmask used by your network. For example:

Configuring Basic Network Settings | 29

NETMASK=255.255.255.0

5 Make sure the ONBOOT keyword is set to yes.

ONBOOT=yes

6 Optional: If you have not specified a global default gateway for your system, or if you want to use adifferent gateway for this particular network port, add a GATEWAY keyword in this file, and set it to theIP address of the gateway. For example:

GATEWAY=192.168.0.1

7 Save and close the configuration file.

To configure host name resolution:

1 Open the /etc/hosts file in a text editor.

2 Locate the loopback setting in the hosts file. By default, the loopback setting is identified by the IPaddress 127.0.0.1, for example:

127.0.0.1 vxfhost.localhost.localdomain localhost

3 Remove the host name preceding localhost.localdomain from the loopback setting.

For example, if you remove the host name vxfhost in the example above, the loopback setting shouldappear as follows:

127.0.0.1 localhost.localdomain localhost

4 On a new line, type the IP address of the system, press Tab, and then enter the explicit host name ofthe system.

The new line defines the network IP address and host name of the system. For example, if the IP addressis 192.168.0.100 and the host name is workstation1, your hosts file should be as follows:

127.0.0.1 localhost.localdomain localhost

192.168.0.100 workstation1

5 Optional: Add hostname / IP address pairs for other workstations on your network. For example:

192.168.0.150 flame1


To configure DNS server information:

1 Open the /etc/resolv.conf file in a text editor.

2 Add a line for each DNS server IP address you want to use. The syntax is:

nameserver <DNS_server_IP>

For example:

nameserver 22.10.50.101

nameserver 22.10.50.102

NOTE Be careful when editing the resolv.conf file. The syntax is very strict, and any extra spaces or carriagereturns can render the file unusable by the system.

Assigning an IP Address to the Autodesk Control SurfacePerform the following tasks to assign an IP address to the Autodesk Control Surface.


1 Open a terminal, and log in as root.

2 Open the configuration file for the network port to which the Control Surface is connected. For example,if the Control Surface is connected to Ethernet port 1, type:

vi /etc/sysconfig/network-scripts/ifcfg-eth1

3 Modify the IPADDR and NETMASK values to the IP address and Netmask you want to assign to theControl Surface. For example:

IPADDR=192.168.125.10

NETMASK=255.255.255.0

4 Press Shift+z+z to save and close the configuration file.

5 Restart the network services by typing:

/etc/init.d/network restart

6 After you have configured the IP address of the Control Surface, set the keywords in theControlSurface section of the Lustre software configuration file. See System Settings on page 74.

Assigning an IP Address to the Autodesk Control Surface | 31

Installing the DKU and theAJA OEM-2K Firmware


■ Installing the DKU on page 33■ Upgrading the AJA OEM-2K Firmware on page 34

Installing the DKUBefore installing your software, you must install the required version of the DKU. See the Release Notes forthe required DKU version for this version.

For major releases, the DKU is available on optical media or as a download from Autodesk. For extensionsand service packs, the DKU is only available for download. The download link is provided in the releaseannouncement you received from Autodesk.

To install the DKU:

1 Open a terminal and log in as root.

2 If you are upgrading an existing application, check the currently installed DKU version by typing:

head -n1 /etc/DKUversion

If the DKU version output by the command does not match the version required for the new applicationversion, perform the remaining steps in this procedure.

3 Access your DKU installation package:

■ If you are installing from an application disc, insert and mount the disc using the command:mount /dev/cdromThe disc mounts on the /mnt/cdrom directory. The DKU installation directory is located in the Linuxdirectory.

5

33

■ Otherwise, download the latest DKU tar file from the download link provided in the releaseannouncement, then go to the directory where the tar file was downloaded, and unpack it by typing:tar -zxvf DKU_<version_number>.tar.gzThe DKU tar file is unpacked into a new directory.

4 Go to the DKU installation directory (/mnt/cdrom/Linux/DKU-<version>, if you are installing from theapplication DVD) and launch the DKU installation script:

./INSTALL_DKU

WARNING If you attempt to install the DKU on an unsupported platform, the installation script only installsa generic configuration. Such a configuration can render your operating system unusable. Never attempt toinstall the current version of the DKU on unsupported platforms, including older Visual Effects and Finishingor Colour Grading systems that are no longer supported in the current version.

When the DKU installation script completes, a warning to update the AJA card firmware may appearand you are returned to the command prompt. See the following section for information on updatingyour AJA card firmware.

5 If you installed from a disc, return to the root directory, and eject the disc by typing:

eject

6 If storage devices (external disk arrays or internal storage) were previously disconnected or turned offas part of an operating system installation, reconnect them and power them up.

NOTE Power on the XE expansion enclosures first and the XR RAID controller units last. This ensures theRAID controllers detect the other units in the Stone Direct storage.

Wait for all the disks in the storage devices to fully power up before rebooting the system. The greenlight for each disk stops flashing once it is fully powered up.

7 Reboot the system. Type:

reboot

Upgrading the AJA OEM-2K FirmwareThe firmware on your AJA OEM-2K card must correspond to the certified version required by your applicationversion. Refer to the Release Notes for the required AJA OEM-2K firmware version.

The AJA firmware update utilities required to check your firmware version are included with the DKU versionfor your application.

The following procedure describes how to verify and update the firmware version of the AJA OEM-2K card.

To verify and upgrade the AJA OEM-2K firmware:

1 Open a terminal, log in as root, and type:

cat /proc/driver/aja

If the PCI version line in the output lists a different version than the required one, perform thefollowing steps to upgrade the firmware.

NOTE Before upgrading the AJA firmware, make sure you have upgraded the DKU, and that you haverestarted the system.

2 Go to the /usr/discreet/DKU/current/Utils/AJA_firmwareUpdate directory.

34 | Chapter 5 Installing the DKU and the AJA OEM-2K Firmware

3 Run the AJAfw_update utility to scan the AJA current firmware and, if required, update to the latestfirmware version. Type:

./AJAfw_update

If the utility detects that the firmware and drivers need to be updated, it prompts you to start the update.

4 Start the firmware update by typing Y and then pressing Enter.

While the AJA firmware and drivers are being updated, your workstation appears to be frozen and yourmouse and keyboard do not work. This is normal and indicates that the firmware is being updated.Once the firmware update is complete, you are returned to the terminal.

5 Shut down your workstation by typing:

shutdown -g0

If your workstation does not prompt you to power down, press the power button for 10 seconds toforce a power down.

6 Disconnect the power cord.

7 Wait 10 seconds, reconnect the power cord, then restart your workstation.

NOTE For more details about the AJA firmware procedures, consult the README file located in the currentdirectory.

Upgrading the AJA OEM-2K Firmware | 35

Configuring Storage


■ Overview on page 37■ Powering Up Your Storage on page 38■ Partitioning the Storage and Creating the XFS Filesystem on page 38

OverviewThis chapter describes how to configure a direct-attached storage array connected to the workstation.

If you are also configuring a Storage Area Network (SAN), it is recommended that you configure the SANprior to configuring a direct-attached storage.

Before you can configure the storage, the workstation must be up and running the custom Autodeskdistribution of Red Hat Enterprise Linux, as well as the version of the DKU required for your applicationversion.

WARNING When configuring a storage array, it is strongly recommended to disconnect any other storage device(DAS or SAN) connected to the workstation.

Do I Need to Perform these Procedures?If you are reinstalling your system from scratch, or adding new storage devices, refer to the procedures inthis section for information on partitioning the storage and setting up the XFS filesystem.

If you are only upgrading an existing application installation without adding new storage, skip to the nextchapter for instructions on installing the software.

6

37

Powering Up Your StoragePowering your system and storage up or down should be done in a proper sequence. This ensures that thesystem functions properly.

WARNING An incorrect power up sequence can mean your system does not recognize all drives.

NOTE If you are configuring a storage array with two sets of enclosures, connect only one set of enclosures atthis point, and then perform the filesystem creation procedures in the next section. Then disconnect the storage,and repeat the entire process for the second set of enclosures.

To power up your system:

1 Make sure your workstation is shut down.

2 Power up the XE expansion enclosures.

3 Power up the XR RAID controller enclosures.

4 Wait about 90 seconds for all the drives to spin up. Their lights are solid green when they are spun up.

5 Power up your workstation.

To power down your system, shut down your workstation first, then the XR RAID controller enclosures,and finally the XE expansion enclosures.

Partitioning the Storage and Creating the XFS FilesystemBefore you can use a new storage array, you need to create logical units (LUNs) on it, partition them, groupthe partitions into a logical volume, and then create the XFS filesystem on the logical volume.

All these operations can be easily performed using version 1.5 of the XR Configuration Utility from Autodesk.This version of the XR Configuration Utility is available in versions 4.5.1 and newer of the Discreet KernelUtilities (DKU).

If your workstation is using an older version of the DKU that does not have the latest XR Configuration Utility,or if you prefer to manually partition your storage array and configure the filesystem, refer to ManuallyConfiguring Media Storage on page 81.

Perform one of the following procedures to configure your storage using the XR Configuration Utility. Theprocedures are different for storage arrays with a single set of enclosure, and for arrays with two sets ofenclosures.

Note that the XR Configuration Utility exits without configuring your storage if any of the following issuesare detected:

■ The total number of disks is not a multiple of 12.

■ One of more of the enclosures do not have the correct firmware.

■ When using two sets of enclosures, the number of expansion chassis attached to each XR RAID enclosureis not the same.

■ An odd number of enclosures in a 4-loop configuration. Only even numbers of enclosures are supported.

To configure arrays with a single set of enclosure:


38 | Chapter 6 Configuring Storage

2 Go to the /usr/discreet/DKU/current/Utils/Storage/current/ directory, and run the XR Configuration Utilityby typing:

./XR_config.pl

The script displays information on the storage, such as: enclosure type, RAID controller firmware version,number of enclosures, number of loops.

3 If a LUN configuration already exists on the storage, you are prompted for confirmation to overwritethat configuration.

WARNING LUN configuration is destructive. Make sure you want to overwrite an existing configurationbefore you confirm.

4 After the utility detects the number of enclosures and drives, it presents you with a list of options.

5 Type 2 and press Enter.

This option instructs the configuration utility to create LUNs with a sector size of 512 bytes. This is theoptimal sector size for XFS DAS (direct-attached) storage of Visual Effects, Finishing and Colour Gradingapplications.

6 When asked if you have a 2-loop or a 4-loop configuration, select the option that applies to your storage.Note that 4-loop configurations are only supported for XR 6412 and XR 6500 storage.

The utility creates LUNs on your storage. This process might take a few minutes.

When the LUN creation process completes, the configuration utility asks you if you want to create theXFS filesystem on the storage array.

7 Type Y (the default answer).

The configuration utility partitions the storage array, groups the partitions into a logical volume, createsthe XFS filesystem on the volume, and mounts the volume to /mnt/StorageMedia on HP Z800 workstations,or /mnt/stoneMedia on older workstations.

NOTE If the storage driver does not reinitialize quickly enough after LUN creation, the filesystem creationstep may fail, and the XR Configuration Utility gives you an error message similar to the following:

Can't open /dev/sdb1 exclusively. Mounted filesystem?

In such cases, reboot your workstation, and perform the steps in Performing only the filesystem creationoperations on page 40.

8 Type x to exit the configuration utility.

NOTE Even though your storage array is usable at this point, the drives are still initializing following the LUNcreation. Your storage operates at reduced performance until the initialization process completes. This mighttake a few hours. To check the progress of the initialization type:

./XR_config.pl --arrayStatus

9 Once the initialization process completes, create a back-up of the storage configuration by typing:

./XR_config.pl --saveConfig

A back-up of the storage configuration is saved.

To configure arrays with two XR enclosures:


2 Make sure only one set of enclosures is connected to the workstation.

Partitioning the Storage and Creating the XFS Filesystem | 39

3 Go to the /usr/discreet/DKU/current/Utils/Storage/current/ directory, and run the XR Configuration Utilityby typing:

./XR_config.pl

The script displays information on the storage, such as: enclosure type, RAID controller firmware version,number of enclosures, number of loops.



5 After the utility detects the number of enclosures and drives, it presents you with a list of options.

6 Type 2 and press Enter.

This option instructs the configuration utility to create LUNs with a sector size of 512 bytes. This is theoptimal sector size for XFS DAS (direct-attached) storage of Visual Effects, Finishing and Colour Gradingapplications.

7 When asked if you have a 2-loop or a 4-loop configuration, select the option that applies to your storage.Note that 4-loop configurations are only supported for XR 6412 and XR 6500 series storage.

The utility creates LUNs on your storage. This process might take a few minutes.

When the LUN creation process completes, the configuration utility asks you if you want to create theXFS filesystem on the storage array.

8 Type N.

NOTE If you answered Y by mistake (the defalt answer), you get another chance to answer no after thesystem rescans the disks. It is very important that you do not create the filesystem at this point.

9 Type x to exit the configuration utility.

10 Once the initialization process completes, create a back-up of the configuration for this set of enclosuresby typing:


A back-up of the configuration is saved. Note that you can only save the configuration for one set ofenclosures at a time.

11 Power off the workstation, disconnect the storage enclosures, and connect the second set of enclosures.

12 Power the workstation back on.

13 Perform steps 3 through 10 in this procedure on the second set of enclosures.

14 Power off the workstation again, connect both sets of enclosures to the workstation.

15 Power the workstation back on and perform the tasks in the following procedure.

Use the following procedure if you need to perfrom just the partitioning and filesystem creation operationson a storage array where LUNs have already been created.

To perform only the filesystem creation operations:


2 Go to /usr/discreet/DKU/current/Utils/Storage/current/, and type:

./XR_config.pl --createFS

40 | Chapter 6 Configuring Storage

The configuration utility partitions the storage array, groups the partitions into a logical volume, createsthe XFS filesystem on the volume, and mounts the volume.

NOTE Using this parameter has the same effect as running the XR Configuration Utility with no parameter,and choosing option 4 from the main menu.

3 Create a back-up of the storage configuration by typing:


NOTE You can only back-up your storage configuration after the drives have finished initializing. This processmight take a few hours. To check the progress of the initialization type:

./XR_config.pl --arrayStatus

To get a complete list of the command-line parameters available for the XR_config.pl script, type:

./XR_config.pl --help

Partitioning the Storage and Creating the XFS Filesystem | 41

Installing Lustre on theLinux Workstation


■ Overview on page 43■ Installing Lustre on page 43

OverviewThis chapter describes the Lustre software installation process. If you received a new system with this release,the software is already installed, and you do not have to perform the procedures in this chapter. Use theseprocedures if you are upgrading from the previous release of Lustre, or if you must reinstall the software atany point.

Installing LustreUse the following procedure to install Lustre.

To install Lustre:


2 If you are not installing from an application disc, download the application tar file from Autodesk.

The download link is provided in the release announcement you received from Autodesk.

TIP After downloading the tar file, verify the its integrity using the Linux md5 checksum provided. In thedirectory where you saved the tar file and the checksum file, type md5sum <filename.tar.gz>, andmake sure the checksum displayed matches the Linux md5sum listed in the checksum file.

7

43

3 If you need to change your system date or time, do it before installing the application.

4 Access your installation package:

■ If you are installing from an application disc, mount the disc, then go to the Linux/Applicationsdirectory on the mounted disc:mount /mnt/cdromcd /mnt/cdrom/Linux/Applications/

■ If you are installing from a downloaded application tar file, unpack the tar file:tar -zxvf <filename.tar.gz>The file is uncompressed and an installation directory is created on your system.

5 Navigate to the installation directory and start the Lustre software installer by typing:

./INSTALL_LUSTRE

6 If prompted with a message asking if you would like to automatically run Backburner™ Server on thismachine, click Yes.

The Lustre application, as well as supporting software (Backburner, Wiretap, Wiretap® Gateway, theBrowseD server) are installed. A new user account is created for the version of Lustre you just installed.Read the following chapter for information on licensing and starting your application for the first time.

NOTE If you are upgrading to a service pack of the same release or extension, you do not need to re-licenseyour software.

44 | Chapter 7 Installing Lustre on the Linux Workstation

Licensing and Starting theApplication


■ Licensing Workflow on page 45■ Determining the Licenses You Require on page 46■ Obtaining the Host ID on page 46■ Requesting License Codes on page 47■ Entering License Codes on page 47■ Starting the Application for the First Time on page 48

Licensing WorkflowIf you have purchased subscription and are upgrading to a new release, your new license is sent to you bythe Autodesk Media and Entertainment department. After receiving your license, perform the followingtasks:

1 Install the new license. See Entering License Codes on page 47.

2 Start the application and accept the license agreement. See Starting the Application for the First Timeon page 48.

If you are installing the application for the first time, use the following steps to obtain and install licensecodes.

To obtain and install license codes for the application:

1 Determine which license codes you require. See Determining the Licenses You Require on page 46.

2 Obtain the host ID of the workstation. See Obtaining the Host ID on page 46.

8

45

3 Request temporary license codes. See Requesting License Codes on page 47.

4 Install the temporary license codes. See Entering License Codes on page 47.

5 Start the application and accept the license agreement. See Starting the Application for the First Timeon page 48.

6 When you receive permanent license codes, install those codes. See Entering License Codes on page47.

Determining the Licenses You RequireThere are two license type categories: main components and optional components.

The main component license types are as follows:

■ Lustre Master Station

■ Lustre HD Station

■ Lustre Station with Primary Grading

■ Lustre Station

■ Slave Renderer

■ Background Renderer

The optional component license types are as follows:

■ HD Video I/O

■ HD Dual Link and HDSL

■ BrowseD

NOTE For BrowseD, you can get a GigE license, or an InfiniBand license. The GigE license allows you to useBrowseD only over a GigE or 10 GigE network. The IB license allows you to use BrowseD over GigE, 10 GigEor InfiniBand.

License codes must be requested for each main and optional Lustre component.

Obtaining the Host IDTo request a license code, you must provide the unique host ID of your workstation. The host ID is used toauthenticate your registration.

To obtain the host ID:

1 Open a terminal and run the dlhostid script by typing:

dlhostid

A message similar to the following one appears, containing the host ID:

dlhostid — Copyright © 2005 by Autodesk, Inc./Autodesk Canada Co. Allrights reserved.

The lmhost ID of this machine is “00110910DA2E” (eth0)

46 | Chapter 8 Licensing and Starting the Application

The Discreet host ID of this machine is“DLHOST01=25231AEF83AD9D5E9B2FA270DF4F20B1”

2 Send the Discreet host ID to the Autodesk Licensing Department to receive your application licensecode. When you record the Discreet host ID, make sure you include the DLHOST01= string as well asthe code; for example, DLHOST01=25231AEF83AD9D5E9B2FA270DF4F20B1

NOTE Make sure you obtain a host ID for each workstation on which you install the application.

Requesting License CodesYou can obtain application license codes by registering the application with the Autodesk Media andEntertainment Licensing Department by e-mail or telephone.

NOTE For emergencies, you can acquire an immediate temporary emergency license using the emergency licensegenerator at http://melicensing.autodesk.com/templicensing/. A 4-day license code is e-mailed to the address youprovide.

To obtain license codes:

1 Select “No, request a License Code”, and click Next.

2 Enter your contact information in the license code request form. The host ID and system serial numberof your workstation are automatically filled in.

3 Click Next.

4 Gather the following information:

■ Company name

■ Contact name (with e-mail and phone contact information)

■ dlhostid for every workstation on which Lustre is installed

■ Required license type for every workstation (see Determining the Licenses You Require on page 46)

■ Requested term

5 Send the form by e-mail to [email protected].

You will receive your temporary license code within eight business hours.

To obtain license codes by telephone:

➤ Speak to a licensing representative by calling the Autodesk Licensing Department toll-free in NorthAmerica at 1-800-925-6442 between 8 AM and 8 PM eastern standard time (EST). Outside of NorthAmerica, call 1-514-954-7199.

Entering License CodesOnce you receive a license code, it needs to be installed and recognized by the application.

To install a license:

1 If the directory /usr/local/flexlm/licenses/ does not already exist, create it. Type:

mkdir -p /usr/local/flexlm/licenses/

Requesting License Codes | 47

http://melicensing.autodesk.com/templicensing/

2 Create a file called DL_license.dat in the /usr/local/flexlm/licenses/ and open it in a text editor, such asnedit:

nedit /usr/local/flexlm/licenses/DL_license.dat

NOTE The license directory and filename are case-sensitive and must be created and named exactly asspecified.

3 Copy the license code you received from Autodesk into the DL_license.dat file.

Starting the Application for the First TimeOnce you have installed Lustre and obtained your license codes, you are ready to start the software.

To start Lustre log into the application’s Linux user account and double-click the Lustre icon on the KDEdesktop.

Lustre starts. The license you installed determines the type of station you are using (Lustre Master Station,Lustre HD Station or Lustre Station).

When the Lustre UI appears, you can begin working. For a new project, this includes:

■ Creating the project and setting its parameters (such as logarithmic or linear colour space).

■ Specifying the location of footage.

■ Setting up user profiles.

NOTE For information on creating projects and users, see the chapter “Project Management” in the Lustre UserGuide.

48 | Chapter 8 Licensing and Starting the Application

Configuring SlaveRendering


■ Workflow for Configuring Slave Rendering on page 49■ Configuring the Slave Renderer Network Address on page 50■ Installing the Slave Renderer Software and License on page 50■ Configuring Read/Write Access to Storage from the Slave Renderer on page 51■ Mounting the Storage on the Slave Renderer on page 52■ Setting Up Lustre Projects to Use Slave Rendering on page 53

Workflow for Configuring Slave RenderingThe Slave Renderer renders modified frames when the artist moves to the next shot on the timeline fromthe Master Station or HD Station. With slave rendering, playback is enabled without compromising theinteractivity of the Master Station or HD Station during creative sessions.

Connect the Slave Renderer to a switch on your GigE or 10-GigE house network. You can configure it toaccess media through NFS mount points, or using the BrowseD service. Using BrowseD is the recommendedapproach, as it is much faster than NFS.

See the following table for a summary of the steps necessary to configure slave rendering.

Refer to:Step:

Installing Red Hat Enterprise Linux and In-stalling the DKU on page 33.

1. Install Linux and the Discreet Kernel Utility (DKU) on the Slave Renderer.

The Slave Renderer section in Setting Up YourWorkstation Hardware on page 7, or in theHardware Setup Guide for your workstation.

2. Connect the Slave Renderer to a switch on your house network.

9

49

Refer to:Step:

Configuring the Slave Renderer Network Ad-dress on page 50.

3. Configure the network address that the Slave Renderer uses to communic-ate to the workstation.

Installing the Slave Renderer Software andLicense on page 50.

4. Install the slave rendering software and license.

Configuring Read/Write Access to Storagefrom the Slave Renderer on page 51.

5. If you are not using BrowseD, configure read/write access to storage at-tached to the Master or HD Station from the Slave Renderer.

Mounting the Storage on the Slave Rendereron page 52.

6. If you are not using BrowseD, mount the storage attached to the Masteror HD Station on the Slave Renderer.

Setting Up Lustre Projects to Use Slave Ren-dering on page 53.

7. Set up the configuration file so that Lustre projects can use slave rendering.

The Autodesk Lustre User Guide.8. Render shots as you work.

Configuring the Slave Renderer Network AddressAfter installing Linux on the Slave Render, you must configure the IP of the ethernet port that connects theSlave Render to your house network.

NOTE The address you choose must not conflict with any of the other IP addresses on the network.

In a Lustre installation in which you have not altered any of the IP addresses used by default, you can use193.1.1.2 as the Slave Renderer IP address.

To configure the network address:

1 Start the Slave Renderer and log in as root.

2 Assign an IP address to the ethernet port that connects the Slave Renderer to the network switch. TheIP address must be in the same IP class as your network.

TIP Typically, your Linux workstation's TCP/IP settings are configured in the file/etc/sysconfig/network-scripts/ifcfg-eth<port#> , where <port#> is the port used to connect the SlaveRenderer to the network, or directly to the Master or HD Station. For example, if the connection is on port0 of the onboard network card, the file you would edit would be /etc/sysconfig/network-scripts/ifcfg-eth0.

Installing the Slave Renderer Software and LicenseUse the following procedures to install the Slave Renderer software and license.

To install the Slave Renderer software:

1 Start the Slave Renderer and log in as root.

2 If you are installing from a DVD, insert the DVD, and type the following commands to mount the disc,and to navigate to the Lustre installer directory:

mount /mnt/cdrom

cd /mnt/cdrom/Linux/Applications/

3 If you are installing from a downloaded tar file, unpack the tar file by typing:

50 | Chapter 9 Configuring Slave Rendering

tar zxvf <file_name>.tar.gz

The installation package is unpacked into a new directory. Navigate to the new directory.

4 Start the installation script by typing:

./INSTALL_LUSTRE_SLAVE

The Slave Renderer is installed.

To install the Slave Renderer license:

1 If you have not already done so, obtain a license for the Slave Renderer. You will need the dlhostid ofthe Slave Renderer. Refer to Obtaining the Host ID on page 46 and Requesting License Codes on page47.

2 Log in to the Slave Renderer as root.

3 Create the directory for the license file. Type:

mkdir -p /usr/local/flexlm/licenses/

4 Create a file called DL_license.dat using a text editor such as nedit, and save it to the new directory. Type:

nedit /usr/local/flexlm/licenses/DL_license.dat

NOTE The license directory and filename are case-sensitive and must be created and named exactly asspecified.

5 Copy the license code you received for the Slave Renderer from Autodesk to the DL_license.dat file.

Configuring Read/Write Access to Storage from the SlaveRendererThe storage must be exported from the Master or HD Station in order to allow read/write access. This, inturn, makes it possible for the Slave Renderer to remotely mount the storage system.

NOTE You do not need to perform the tasks in this section if you are using the BrowseD service with the SlaveRenderer. See Using BrowseD with the Slave Renderer on page 70.

To export the storage attached to the Master or HD Station:

1 Log in to the Master Station as root. The storage filesystem is mounted as /mnt/StorageMedia (for HPZ800 stations), or /mnt/md0 (for older systems).

2 Open the /etc/exports file in vi by typing:

vi /etc/exports

The contents of the exports file appears, listing the available network shares (filesystems mountable overthe network). Next, add a new line for the mount point of the storage filesystem.

3 Scroll to the end of the exports file using the arrow keys.

4 Press Insert to enter insert mode.

5 Add a new line for the mount point. For example:

/mnt/StorageMedia *(rw,no_subtree_check,async)

or

/mnt/md0 *(rw,no_subtree_check,async)

Configuring Read/Write Access to Storage from the Slave Renderer | 51

This line creates a network share for the mount point for the storage filesystem. Other users on thenetwork will access the storage devices by mounting its network share.

6 Press Esc to enter command mode.

7 Save and close the file by pressing Esc to enter command mode, then Shift + zz.

The file is saved and you are returned to the command prompt.

8 Activate the new network share for the storage device. Type:

exportfs -a

The list of network shares is refreshed from the exports file.

9 Confirm the storage devices are available to be mounted by typing:

exportfs

The network shares of the Lustre Frame server appears in a list similar to the following:

/mnt/StorageMedia <world>

...

Mounting the Storage on the Slave RendererAfter you configure read and write access on the storage filesystem, you create a mount point on the SlaveRenderer and configure the Slave Renderer to automatically mount that filesystem.

NOTE You do not need to perform the tasks in this section if you are using the BrowseD service with the SlaveRenderer. See Using BrowseD with the Slave Renderer on page 70.

To create a mount point on the Slave Renderer:

1 On the Slave Renderer, log in as root.

2 To go to the top level directory, in a terminal, type:

cd /

3 Create a directory for the mount point. For example, type:

mkdir /mnt/StorageMedia

4 Change the permissions on this directory to allow read/write access. For example, type:

chmod 666 /mnt/StorageMedia

5 Mount the storage exported from the Master Station. For example, if the storage on the Master Stationis mounted under /mnt/StorageMedia type:

mount <Master Station>:/mnt/StorageMedia/ /mnt/StorageMedia

To configure the Slave Renderer to automatically mount the storage filesystem:

1 In a terminal, type:

vi /etc/fstab

2 Press Insert on the keyboard, and then add a line for the mount point you just created:

<IP address>:/<exported filesystem> /<mount point> nfs rw,bg,hard,intr0 0

For example, type:

52 | Chapter 9 Configuring Slave Rendering

172.16.60.226:/mnt/StorageMedia /mnt/StorageMedia nfs rw,bg,hard,intr 00

NOTE Both examples are single lines.

3 Save and close the file by pressing Esc to enter command mode, then Shift + zz.


4 Restart the Slave Renderer machine.

When you restart your system, the storage filesystem mounts automatically.

Setting Up Lustre Projects to Use Slave RenderingAfter you have configured the Master or HD Station and the slave rendering machine to communicate, youmust:

■ Configure the “HostName string=” keyword with the slave rendering machine IP address in the SlaveRenderer section of the init.config file. See Software, Project, and User Configuration Files on page 73.

■ Enable slave rendering for the project. See the Project Management chapter in the user guide.

Setting Up Lustre Projects to Use Slave Rendering | 53

Configuring BackgroundRendering


■ About Background Rendering on page 55■ Background Rendering Components on page 55■ Workflow for Setting Up Background Rendering on page 57■ Sharing the Storage for Read/Write Access from Background Render Nodes on page 57■ Installing Backburner Manager and Backburner Web Monitor on page 58■ Setting Up Render Nodes on page 59■ Configuring Lustre to Detect Backburner Manager on page 65■ Specifying the Background Rendering Path in Lustre on page 65

About Background RenderingDuring background rendering, a shot on the timeline is rendered by a background rendering network. Thisis different from the Slave Renderer, which renders shots on a shot-by-shot basis as they are colour gradedto enable improved playback performance.

Background rendering in Lustre is performed using Burn™ for Lustre, also known as the Lustre BackgroundRenderer. This application is specific to Lustre and provides asynchronous background processing of Lustrerender jobs. By off-loading rendering activities to remote Linux® servers, Lustre stations are freed up forinteractive colour grading, while background rendering is sped up by splitting the task amongst multiplehosts.

Background Rendering ComponentsThe components of the basic background rendering package include Lustre, a background management andmonitoring application (such as Backburner™ Web Monitor, or the Backburner Monitor in Autodesk

10

55

WiretapCentral™), and several render nodes running on Linux servers. The Lustre system and all backgroundrendering nodes are connected over a dedicated background TCP/IP network. Render nodes can access mediathrough NFS mount points, or by using the faster BrowseD service. Using BrowseD is the recommendedapproach. See Configuring BrowseD on page 67.

The background rendering components are illustrated as follows.

Rendered frames are saved back toLustre Storage or SAN/NAS (Renders home)

Master or HD Station Backburner ManagerRender NodesBackburner ServerBurn for Lustre

Background renderingGigE or Infiniband infrastructure

SAN / NASFile server

Backburner Web Monitor

Jobs

Lustre Storage

Source frames are pulled from theLustre Storage or SAN/NAS (Scans home)

Jobs

Switch

Note - Render nodes can render back to the storage through:• NFS•• BrowseD server

Source Frames

Rendered Frames

NOTE You can have up to eight render nodes on the background rendering network.

The other background rendering components are described as follows.

Lustre application This is the client application. Running on a Linux workstation, Lustre rendering jobsare submitted for background rendering through the Render | Backburner menu.

Backburner Manager This is the hub of the background rendering workgroup. Backburner Manager canreside 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 submittedjob into tasks and distributes the tasks to the rendering servers on the network. To view the progress of thetasks, use Backburner Monitor.

Backburner Web Monitor This is the user interface for the Backburner rendering network. It is automaticallyinstalled with Backburner Manager, and can be accessed through a Web browser from any workstation onthe network. It allows you to view and control jobs currently being processed. You can stop, restart, reorderor remove jobs completely using the Monitor. You also use Backburner Web Monitor to identify any rendernodes that are not working and check the overall status of the rendering network.

Backburner Server This is a server that runs on render nodes, and is automatically installed with Burn forLustre. Backburner Server accepts commands from Backburner Manager to start and stop rendering tasks.Backburner Server communicates through a plug-in to execute rendering tasks.

NOTE Consult the latest Autodesk Backburner Installation Guide and Autodesk Backburner User Guide for detailedinformation on Backburner. Use the guides to obtain Backburner information that does not relate directly to Lustrebackground rendering, such as details on setting up Web monitoring and troubleshooting tips.

Burn for Lustre This is the Linux rendering engine that renders one or more frames from Lustre renderjobs.

Shared storage mount point This is the mount point on each Linux server that allows Burn for Lustre totransfer rendered frames/files to the Lustre storage system.

56 | Chapter 10 Configuring Background Rendering

NOTE The storage does not have to be mounted on the render nodes if you are using BrowseD for backgroundrendering. See Using BrowseD for Rendering with Burn for Lustre on page 70 .

Workflow for Setting Up Background RenderingThe following table outlines the general workflow for installing and configuring background rendering.

Refer to:Step:

Sharing the Storage for Read/Write Accessfrom Background Render Nodes on page 57.

1. If you are not using BrowseD, enable sharing on the system storing theLustre project and render files.

Installing Backburner Manager and Backburn-er Web Monitor on page 58.

2. Install and configure Backburner Manager and Backburner Web Monitor.

Configuring Lustre to Detect BackburnerManager on page 65.

3. Configure the Lustre workstation to connect to Backburner Manager.

Setting Up Render Nodes on page 59.4. Set up the background render nodes.

Specifying the Background Rendering Pathin Lustre on page 65.

5. Specify the mount point of the background render nodes in the Lustreapplication.

Sharing the Storage for Read/Write Access fromBackground Render NodesIn order to allow read and write access, the storage must be exported from the system to which it is connected.This makes it possible for the background rendering components on the network to remotely mount thestorage system.

NOTE Skip this section if you are using the BrowseD service.

To make the storage system visible over the network:

1 Log in to the Lustre system (or the central storage system) as root. The storage filesystem is mounted as/mnt/StorageMedia(on HP Z800 workstations) or /mnt/md0(on older workstations).

2 Open the /etc/exports file in a text editor, such as vi.

The contents of the exports file appears, listing the available network shares (filesystems mountable overthe network).

3 At the end of the file, add a new line for the mount point of the storage filesystem:

/mnt/StorageMedia *(rw,no_subtree_check,async)

or

/mnt/md0 *(rw,no_subtree_check,async)

This line creates a network share for the mount point of the storage filesystem. Other users on thenetwork will access the storage devices by mounting its network share.


5 Activate the new network share for the storage device. Type:

exportfs -a

The list of network shares is refreshed from the exports file.

Workflow for Setting Up Background Rendering | 57

6 Verify the storage devices are available to be mounted by typing:

exportfs

Make sure the storage filesystem mount points are listed in the command output.

Installing Backburner Manager and Backburner WebMonitorOn Lustre stations, Backburner components are automatically installed with the Lustre software. The installerasks you if you want to run Backburner components on the station.

To avoid performance degradation, it is recommended to avoid running Backburner components on yourLustre stations, and to relocate Backburner Manager on a dedicated Linux machine in your network. Renderjobs handled by Backburner can be viewed and managed in Backburner Web Monitor from any workstationon the network.

To install Backburner Manager and Backburner Web Monitor on a Linux system:


2 Access the Autodesk Lustre software installation package (from a downloaded tar file or on DVD).

3 Install Backburner by typing:

rpm -Uvh backburner*

The Backburner components (Server, Manager and Web Monitor) are installed on the system.

4 If the system on which you are installing Backburner runs Linux in graphical mode, you are asked ifyou want to automatically run Backburner Manager and Backburner Server on the machine. AnswerYes to the question about the Manager, and No to the question about the Server.

5 Run the Backburner Web Monitor configuration script:

/usr/discreet/backburner/backburnerConfigWeb

The script automatically configures Backburner Web Monitor.

To verify that Backburner components are running properly:

1 On the system on which you installed Backburner Manager, as root, type:

ps -ef | grep -i backburner

The output of the command should include a line containing the path to the Backburner Managerapplication, similar to the following:

root 14989 10 Nov29 ? 00:02:36/usr/discreet/backburner/backburnerManager

NOTE If Backburner Manager is not running, the Backburner log file/usr/discreet/backburner/Network/backburner.log may be a useful source of information for troubleshooting.

2 To test that Backburner Web Monitor is installed and configured properly, open a Web browser on theManager machine and point it to http://localhost/backburner.

Backburner Web Monitor opens. If you are asked for a user name and password, use backburner for both.

Refer to the Autodesk Backburner Installation Guide for detailed information on configuring Backburner.


http://localhost/backburner

Setting Up Render NodesYou can set up as many as eight render nodes for background rendering with Lustre. On each system intendedfor background rendering, you must do the following.

Refer to:Step:

Render Node Hardware and Software Require-ments on page 59.

1. Verify that the render nodes meet the minimum system requirements.

Installing Linux on Render Nodes on page59.

2. Install the appropriate Red Hat operating system.

Mounting the Storage on the Render Nodeson page 60.

3. If you are not using BrowseD, configure each node to mount the storagethat contains the project render files.

Installing Burn for Lustre on Render Nodeson page 62.

4. Install Burn for Lustre.

Configuring Backburner Server to DetectBackburner Manager on page 64.

5. Connect the render nodes to Backburner Manager.

Starting Backburner Server on page 64.6. Start the Backburner Server on each render node.

Render Node Hardware and Software RequirementsRender nodes purchased from Autodesk come with all the necessary hardware and software componentspreinstalled.

To use Burn for Lustre on nodes that were not purchased from Autodesk, the nodes must meet the minimumhardware and OS requirements listed in the following table.

1 or 2 Xeon® Intel® Processor DPProcessor:

2 GBMemory:

20 GBHard drive:

100/1000 MbpsEthernet:

Red Hat Enterprise Linux 5.3 with Workstation option, customized with the Autodeskkickstart file

OS:

Installing Linux on Render NodesAutodesk Burn for Lustre runs under the custom 64-bit Autodesk distribution of Red Hat Enterprise Linux.

Render nodes purchased from Autodesk ship with the correct Autodesk distribution of Red Hat EnterpriseLinux on DVD.

If you did not purchase your render node from Autodesk, you must get your own 64-bit distribution of RedHat Enterprise Linux Desktop 5.3 with Workstation option, and customize it using the Autodesk kickstartfile.

The kickstart is used to automatically install the packages required for Burn, some of which are not installedas part of a general installation.

This file is availabe in the Lustre installation directory. You must copy it to the DVD of your Linux distribution.

Setting Up Render Nodes | 59

TIP The kickstart file can be used to automate the Linux installation process for multiple render nodes.

To copy the Autodesk kickstart file to the DVD of your Linux distribution:

1 On a computer running Linux and with a DVD burner, log in as root.

2 Insert the DVD of your Linux distribution into the drive. You do not need to mount it at this time.

3 In a terminal, extract an ISO image of the disc by typing:

dd if=/dev/<optical_disc_device> of=/<destination path for the extractedISO image>

For example:

dd if=/dev/cdrom of=/tmp/RHEL5.3.iso

Depending on the speed of your disc drive, this command may take several minutes to complete.

4 Eject the disc.

5 Access the dist subdirectory of the Lustre installation package.

The directory contains a kickstart file, ks_centos5_rh5.cfg, as well as a script that adds the kickstart fileto an ISO image.

6 Run the build_kickstart_cd script to add the kickstart file to the ISO image of your Linux distributionDVD:

./build_kickstart_cd ks_centos5_rh5.cfg <original ISO image name> <newISO image name>

For example, if the ISO image you created is called /tmp/RHEL5.3.iso and you want the new ISO imageto be called /tmp/RHEL5.3_KS.iso, type:

./build_kickstart_cd ks_centos5_rh5.cfg /tmp/RHEL5.3.iso/tmp/RHEL5.3_KS.iso

7 Once the new ISO image of the Linux distribution DVD is created, burn it to a blank disc using a toolsuch as cdrecord.

NOTE Type man cdrecord for information about this utility.

The new disc that you burn contains the Autodesk kickstart file and replaces the DVD in the Linuxdistribution.

You are now ready to install Linux on the render node. See Linux Installation Workflow on page 26.

Mounting the Storage on the Render NodesAfter Red Hat Linux is installed, you must mount the media storage on each render node using an NFSmount point.

NOTE The BrowseD service can also be used to allow background render nodes to access the workstation's storage.BrowseD allows for fast access and requires a separate license. If you are using BrowseD for background rendering,skip this section. See Configuring BrowseD on page 67.

Mounting the storage involves identifying the IP address of the system that manages the storage and settinga mount point on each render node that points to the correct path on the storage. Also, for this mount pointto be available when you restart the system, you must add an entry in the fstab file.

If the system that stores the render files is different from the system that stores the Project Home directories,you need two (or more) mount points. For example, if, in the Project Setup menu, the Project Home path


is /mnt/md0/SCENES and the Renders Full Home path is /sanserver:/RENDERS, located on a central storagesystem, you must define a mount point for each path.

NOTE Make sure the storage is mounted to the same mount point on the system that manages the storage, aswell as on all render nodes.

To mount the storage on a render node:

1 Determine the IP address of the computer that manages the storage.

If you are using direct attached storage only, this is the IP address of the Lustre Master Station or LustreHD Station. You must also determine the IP address of your centralized file server if you are also usinga server area network (SAN) or network attached storage (NAS).

2 On the render node, log in as root.

3 Go to the root directory. In a terminal, type:

cd /

4 Create a directory for the mount point. For example, type:

mkdir /mnt/md0

NOTE The directory name must be the same for the mount point on each node. Also, the directory shouldnot be created in the /root directory, but in the /mnt directory.

5 Change the permissions on this directory to allow read/write access. For example, type:

chmod 666 /mnt/md0

6 Set up the mount point to access the Lustre system storage or the central system storage. You must usethe mount point as defined in the Project_home setting in the Lustre Project Setup menu. For example,if the Project Home is /mnt/md0/SCENES, and the Linux mount point directory is named /mnt/md0, themount command will be:

mount <hostname>:/mnt/md0/SCENES /mnt/md0

To add an entry in the fstab file:

1 Open the file /etc/fstab in a text editor and then add a line for your new mount point:

<IP address>:/<exported filesystem> /<mount point> nfsrw,bg,hard,intr,nfsvers=3 0 0

For example, type:

172.16.60.226:/mnt/md0 /mnt/md0 nfs rw,bg,hard,intr,nfsvers=3 0 0

NOTE The example is a single line.



3 Restart the render node.

When you restart your system, this remote location will mount automatically.

Mounting the Storage on the Render Nodes | 61

Installing and Configuring Burn for Lustre on Render NodesInstall and configure Burn for Lustre on each render node. To install and configure Burn for Lustre, youmust:

■ Install Burn for Lustre.

■ Add the IP address of the machine where Backburner Manager is installed to the manager.host file oneach render node.

■ Start the Backburner Server on each render node.

■ License Burn for Lustre.

Installing Burn for Lustre on Render Nodes

Perform the following procedure to install the Burn for Lustre software on each node.

NOTE When you install Burn for Lustre, the necessary Backburner components are also installed on the rendernode.

To install Burn for Lustre on a render node:

1 Open a terminal to the render node, and log in as root.

2 If you are installing from a Lustre DVD, insert the DVD, and type the following commands to mountthe disc, and to navigate to the Lustre installer directory:

mount /mnt/cdrom





4 Start the Burn installation script by typing:

./INSTALL_LUSTRE_BURN

The Burn for Lustre package is installed. For instructions on obtaining and installing a Burn license,see Licensing Burn for Lustre on page 62.

5 Repeat this procedure on all render nodes.

Licensing Burn for Lustre

You need a license for your render nodes. Burn uses a floating license scheme, which means that licensesare centralized on a license server.

The license server automatically provides a license to all registered machines.

The license server can be any of the render nodes on the rendering network.

Perform the following tasks to obtain a license code for background rendering, install the license server, andconfigure the license server to distribute licenses to burn nodes.

To license a Burn for Lustre network:

1 Open a terminal on the license server machine and log in as root.

2 Run the dlhostid utility to obtain the unique host ID of the machine. Type:

dlhostid


A message appears that includes a line indicating the dlhostid of the machine. For example:

The Discreet host ID of this machine is“DLHOST01=25231AEF83AD9D5E9B2FA270DF4F20B1”

3 Write down the dlhostid (including the “DLHOST01=” part).

4 Request license codes for background rendering from the Autodesk Media and Entertainment LicensingDepartment. See Requesting License Codes on page 47.

5 If you are installing from a Lustre DVD, insert the DVD, mount it, and navigate to the Lustre installerdirectory. Type:

mount /mnt/cdrom





7 Run the license server installation script by typing:

./INSTALL_LICSERV

The license server is installed.

8 Once you have received the license codes, go to the /usr/discreet/licserv/licenses/ directory, and open theDL_license.dat file in a text editor.

NOTE If the file does not exist, create it by typing:

touch /usr/discreet/licserv/licenses/DL_license.dat

9 In this file, enter all the information submitted to you by the Licensing Department upon yourregistration.


11 Start the license server by running the following command:

/etc/init.d/license_server start

NOTE The license server starts/stops automatically when the machine is booted/shut down. You can stopand restart the server manually by running one of the following commands:

/etc/init.d/license_server stop

/etc/init.d/license_server start

Now that the license server is set up, configure each node to contact the server and retrieve its license.Perform the following procedure on each node.

To enable render nodes to contact the license server:

1 Log in to each render node as root.

2 Navigate to the license directory. Type:

cd /usr/local/flexlm/licenses/

3 Open the DL_license.dat file in a text editor.

Installing and Configuring Burn for Lustre on Render Nodes | 63

4 In this file, copy the first three lines of the information submitted to you by the Autodesk LicensingDepartment upon your registration. For example:

SERVER burn-01 DLHOST01=25231AEF83AD9D5E9B2FA270DF4F20B1

VENDOR lustre

USE_SERVER


NOTE Each render node must be able to contact the license server. Use ping from each node to the licenseserver to confirm that the machines can communicate.

Configuring Backburner Server to Detect Backburner Manager

Backburner Server needs to be able to detect the location of Backburner Manager in order to provide statusinformation concerning the render jobs. Set the IP address of the Backburner Manager machine in the/usr/discreet/backburner/cfg/manager.host configuration file on each render node.

NOTE You can also use the hostname of the Backburner Manager machine, if it has been properly defined in the/etc/hosts file.

To configure Backburner Server to detect Backburner Manager:

1 On the Backburner Manager system, open a terminal and log in as root.

2 Determine which IP address the Backburner Manager workstation uses to connect to the network. Type:

ifconfig

Information about all the network adapters is displayed. The second line of the output for each adaptercontains the IP address (listed as “inet addr”). For example:

inet addr:172.16.129.152 Bcast:172.16.135.255 Mask:255.255.248.0

Write down the IP address of the network adapter. If the machine has several network adapters, makesure you write down the address of the one connected to your render network.

3 On each render node, open a terminal and log in as root.

4 Type:

cd /usr/discreet/backburner/cfg

5 Use a text editor to edit the manager.host file.

6 Enter the IP address of the Backburner Manager machine. For example:

10.10.10.1



Starting Backburner Server

You must start the Backburner Server daemon on each Linux system for the first time. Once it is started thefirst time, the daemon will start automatically.

To start Backburner Server:

1 Log in to your Linux system as root.

2 In a terminal, type:

service backburner_server start


3 You can verify that Backburner Server is properly configured by checking the log fileusr/discreet/backburner/Network/backburnerServer.log. Type:

tail -f /usr/discreet/backburner/Network/backburnerServer.log

The file should contain lines similar to the following:

<INF>: Loading plugin: Lustre renderer plugin

4 To stop viewing the file, press Ctrl+C.

5 Repeat these steps to start Backburner Server on each node in the background rendering network.

If you cannot start the Backburner Server, contact Autodesk Customer Support.

NOTE If you need to stop or restart Backburner Server, use one of these commands:

/etc/init.d/backburner_server stop

/etc/init.d/backburner_server restart

Configuring Lustre to Detect Backburner ManagerFor Backburner Manager to receive render jobs, you must set up the Lustre application to connect to thesystem on which Backburner Manager is running.

To configure new projects to use background rendering, you must set the IP address of the BackburnerManager workstation in the init.config file.

To configure the Lustre application to detect Backburner Manager:

1 Locate the Backburner keyword.

2 In the HostName line, set the string parameter to the hostname or IP address of the system whereBackburner Manager is installed. For example:

<HostName string=”172.19.23.161” />

NOTE Do not forget the quotes.

3 Save and close the configuration file.

For more information on the configuration file keywords, see Software, Project, and User Configuration Fileson page 73.

Specifying the Background Rendering Path in LustreThe last step in setting up background rendering is to specify the correct mount points in the settings ofeach project that uses background rendering.

To add the storage path in Lustre:

1 Start Lustre.

2 In the Setup menu, click Settings.

3 Select your project in the Project drop-down list, and click Edit.

The Project Settings menu appears.

4 Click Network Rendering, then click Backburner in the Configuration section.

Configuring Lustre to Detect Backburner Manager | 65

5 Type the location of the Project Home, Scans Full Home, Scans Half Home, Renders Full Home andRenders Half Home, as seen from the Linux render nodes. You only need to enter those locations thatare defined for the project in the local project setup, located in the Setup | Project menu.

The path required in these fields is comprised of the directory defined for the mount point and theactual storage folder. For example, if the Project Home on the Lustre workstation is /mnt/md0/SCENESin the Project Setup menu, and the mount point for the Lustre workstation storage on the Linux rendernodes is /mnt/Lustre_storage, the Project Home path to enter in this menu is:

/mnt/Lustre_storage/SCENES

6 Press Enter.

7 To verify that you have entered the proper path for each project, look at the project configuration filein /usr/autodesk/lustre<application_version>/project/<project name>/project.config. The valuein the burn_project_home line is sent to the render node. This value must match a mount pointon the background render nodes.

For help setting up and managing projects, refer to the Lustre Help.


Configuring BrowseD


■ About BrowseD on page 67■ Workflow for Configuring BrowseD on page 68■ Starting and Stopping the BrowseD Service on page 68■ Configuring Workstations to Use the BrowseD Server on page 68■ Making BrowseD Directories Accessible from the Lustre Browser on page 69■ Using BrowseD for Rendering with Burn for Lustre on page 70■ Using BrowseD with the Slave Renderer on page 70

About BrowseDBrowseD is a Lustre file server with its own high level protocols that optimize network transfers. BrowseDprovides Lustre workstations, Slave Renderers, and background render nodes with high-speed access tocentralized storage, especially if your network uses InfiniBand®.

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 thatis connected to the centralized storage and configure all workstations to use the BrowseD server to accessLustre project files.

The recommended Lustre configuration in a digital film or high-resolution workflow is to store thefull-resolution images on a SAN, NAS, or file server, and the proxies locally. For information on configuringyour projects, see the Autodesk Lustre User Guide.

NOTE You can run BrowseD on the Lustre Master Station or Lustre HD Station to provide render nodes or SlaveRenderers high-speed access to local storage for background rendering. However, this is not recommended. TheBrowseD 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 willnot function correctly when BrowseD is running on the Lustre workstation, and is serving client requests.

11

67

Workflow for Configuring BrowseDSee the following table for a summary of the steps necessary to configure BrowseD.

Refer to:Step:

Installing Lustre on the Linux Workstation onpage 43.

1. Install and license BrowseD on the computer that is connected to thestorage. BrowseD is automatically installed with the Lustre software.

Starting and Stopping the BrowseD Serviceon page 68.

2. Start the BrowseD server.

Configuring Workstations to Use the BrowseDServer on page 68.

3. On all machines (like the Lustre Master Station, the Lustre HD Station, theSlave Renderer, and background render nodes), configure the init.config fileto connect to the BrowseD server.

Making BrowseD Directories Accessible fromthe Lustre Browser on page 69.

4. Make the remote storage accessible from the file browser on the Lustreworkstations.

Using BrowseD for Rendering with Burn forLustre on page 70.

5. Configure background rendering to use the BrowseD server.

Using BrowseD with the Slave Renderer onpage 70.

6. Configure the Slave Renderer to use the BrowseD server.

Starting and Stopping the BrowseD ServiceThe BrowseD service starts automatically after you install it. You can manually start the service using thecommand line interface. The service starts automatically whenever the computer running BrowseD restarts.

For instructions on installing and licensing BrowseD, see Installing Lustre on the Linux Workstation on page43.

To start or stop BrowseD:

➤ In a terminal, type one of the following.

DescriptionCommand

Stops BrowseD./etc/init.d/browsed_<version> stop

Starts BrowseD./etc/init.d/browsed_<version> start

Restarts BrowseD if it is not currently running./etc/init.d/browsed_<version>restart

Restarts BrowseD if it is already running./etc/init.d/browsed_<version>condre-start

Configuring Workstations to Use the BrowseD ServerYou must configure the init.config file for all machines that will use the BrowseD server to access centralizedstorage, such as Lustre workstations, slave renderers, or Burn render nodes.

Use a text editor to edit the init.config file, located at /usr/autodesk/<version>.

68 | Chapter 11 Configuring BrowseD

Use the following table as a reference when configuring the init.config file.

Required valuesKeyword

Enter the administrative user on the BrowseD server, for example, root on Linux.Username

Enter the password for the administrative user as defined above.Password

All computers on the BrowseD network must use the same port to communicate. Set to1055, the default. If configuring a render node or a workstation running on a GigE network,

Port

set this as 1044. If configuring a render node or a workstation running on a high-speed In-finiBand network, set this as 1055.

Defines the IP address or DNS host name for a specific BrowseD Server.BrowsedServer

Enable this option if the networking procotol to use with BrowseD is InfiniBand.UseInfi

Making BrowseD Directories Accessible from the LustreBrowserWhen using centralized storage, you must make the directories on the BrowseD server accessible to all Lustreworkstations through the browser. You do this by configuring the BrowsedServerGroup keyword in theinit.config file.

The mapped directory will appear in the Lustre browser.

Making BrowseD Directories Accessible from the Lustre Browser | 69

Using BrowseD for Rendering with Burn for LustreYou must configure the Lustre Render Backburner paths with the IP address of the BrowseD server to useBrowseD to render with Burn for Lustre.

For information on configuring background rendering for Lustre, see Configuring Background Renderingon page 55.

To use BrowseD for rendering with Burn for Lustre:

1 In Lustre, open the Setup menu, and select Settings.

2 Select your project from the Project list, and click Edit.

3 Click Project, and set the local project paths. For information on configuring your projects, see theAutodesk Lustre User Guide.

4 Click Network Rendering, and then click the Backburner tab.

5 Enter the IP address of the BrowseD server to each path, or click the ellipsis button to browse to theBrowseD path you want to use.

For example, if your Project_Home is set to the bernice directory on mount point /mnt/StorageMedia ofa station that has an IP address of 172.17.20.146, the Project_Home path in the Render > Backburnermenu should read 172.17.20.146:/mnt/StorageMedia/project/bernice.

NOTE These path examples are specific to the Linux environment, and imply that the media frames arelocated on either a Lustre workstation, or on a file server which is running the Linux operating system. If youare configuring the BrowseD path to connect to a Windows system, the paths are different.

Using BrowseD with the Slave RendererYou must configure the Lustre Slave Render paths with the IP address of the BrowseD server in order to useBrowseD with the Slave Renderer.

To use BrowseD with the Slave Renderer:

1 In Lustre, open the Setup menu, and select Settings.

2 Select your project from the Project list, and click Edit.

3 Click Project, and set the local project paths. For information on configuring your projects, see theAutodesk Lustre User Guide.

4 Click Network Rendering, and then click the Slave Render tab.

5 Enter the IP address of the BrowseD server to each path, or click the ellipsis button to browse to theBrowseD path you want to use.

For example, if your Project_Home is set to the bernice directory on mount point /mnt/StorageMedia ofa station that has an IP address of 172.17.20.146, the Project_Home path in the Render > Backburnermenu should read 172.17.20.146:/mnt/StorageMedia/project/bernice.

NOTE These path examples are specific to the Linux environment, and imply that the media frames arelocated on either a Lustre workstation, or on a file server which is running the Linux operating system. If youare configuring the BrowseD path to connect to a Windows system, the paths are different.

70 | Chapter 11 Configuring BrowseD

Uninstalling theApplication


■ Uninstalling your Application on page 71

Uninstalling your ApplicationThe Autodesk Software Remover utility enables you to easily uninstall Autodesk Visual Effects, Finishing andGrading applications from your workstation.

To uninstall your application:

1 If you are logged in as the application user in KDE, log out and log back into KDE as root.

2 Open a terminal, and type:

rmsoft

The user interface appears.

A

71

d

a b c

e

3 Select the packages you want to uninstall in the RPM list on the left (click Select All to select all the

packages), then click to move them to the RPM uninstall list on the right.

4 Click Next.

5 Click Uninstall & Remove to confirm the removal of the selected packages and directories.

The uninstallation starts and displays details on the process.

6 When the operation completes, click Exit to close the Autodesk Software Remover utility.

7 Optional: You can also delete the log files associated with a given application version in the /var/log/directory.

72 | Appendix A Uninstalling the Application

Software, Project, and UserConfiguration Files


■ Configuration File Overview on page 73■ System Settings on page 74

Configuration File OverviewThe configuration files define all the necessary settings Lustre needs to recognize various hardware andsoftware settings on the Master Station or Lustre HD Station, and on the dedicated render station.

Before doing any colour correction in Lustre, you must first log into a project with a valid user profile. Seethe “Project Management” chapter in the Autodesk Lustre User Guide. When you create a user profile andproject in Lustre, you are indirectly creating the user.config, project.config, and <user>Context.config files.However, aside from the initial system configuration in the init.config file that you must set before you beginworking, there is no need for you to manually create or modify any of the other configuration files. All ofthe configuration settings are set within Lustre's user interface (refer to “System Settings” in the “ProjectManagement” chapter of the Autodesk Lustre User Guide).

When you log into a particular project in Lustre for the first time, Lustre creates the <user>Context.config file,where <user> represents the user name associated with the user profile. The context file is found in the.../projects/<project>/ directory. The context keywords include some attributes not defined in the Project orUser configuration settings. They are saved and reloaded each time the context (same user and project)applies. The context settings include:

■ Last scene

■ Last shot

■ Resolution

B

73

■ Crop value

■ Viewing Options

■ Assemble frame rate/drop frame mode

■ State of the surface control

■ Audio file

The following is a list of the Lustre configuration files.

DescriptionDefault LocationConfiguration file

This file stores system settings as well asWiretap servers, Slave Renderer settings, andfilm stock information.

/usr/autodesk/lustre2011/init.config

This file records the last user and last projectused so at the next session, the user andproject login defaults will reflect these values.

/usr/autodesk/lustre2011/login.config

This file stores project-level information includ-ing project settings, calibration, rendering,

/usr/autodesk/projects/<project>/project.configproject.config

engineering, and Backburner and Wiretapsettings specific to the project.

This file stores user settings specific to a par-ticular user, such as Autosave, printer light,GUI background/gain/gamma.

/usr/autodesk/users/<user>/user.configuser.config

This file stores several settings relevant to thecontext of a particular user working on a

/usr/autodesk/projects/<project>/<user>Context.config<user>Context.config

particular project. The purpose of storingcontext-specific information is that there aresome parameter settings that, by their nature,are more likely to be needed in the next ses-sion, but that are not configurable in theProject Management pages.

System SettingsBefore you first log into Lustre, you must configure the system settings in the init.config file (refer to“Configuring System Settings” in the “Project Management” chapter of the Autodesk Lustre User Guide). Ifthese system settings are not configured, Lustre uses the default system settings. The following table describesthe relevant system settings that should be configured before the first login.

NOTE All keyword values are case-sensitive.

FunctionDefaultData typeParameter

<Locations>

Location of the Project configuration set-tings folder.

String<MainProjectHome>

74 | Appendix B Software, Project, and User Configuration Files


Location of the User configuration set-tings folder.

String<MainUserHome>

Defines the location of the global Gradebin.

String<GlobalGradeBinHome>

Defines the location of the LUTs.

NOTE If you a re configuring a SlaveRenderer system, and [LUSTRE_HOME] islocated on a mounted network drive,make sure you use the full UNC path ofthe network folder instead of the mappeddrive letter.

[LUSTRE_HOME]/lutString<LutHome>

Defines the location of the presets.


[LUSTRE_HOME]/presetsString<PresetsHome>

Defines the location of the plug-ins.


[LUSTRE_HOME]/pluginsString<PluginsHome>

Defines the location of the templates.


[LUSTRE_HOME]/tem-plates

String<TemplatesHome>

<Browser>

Hides the degrain cache, original, matte,marry_grade, and 128x96 folders fromthe file browser.

NOTE You can hide any additional folderby adding the folder name to the list.

degrain_cache,original,matte,marry_grade, and128x96

String<HideFolder>(within <MediaBrowseHideFolder-sGroup>)

<Wiretap>

Specifies whether Lustre automaticallyscans for Wiretap servers.

OnState<ServerAuto>

System Settings | 75


The IP address or DNS host name for aspecific Wiretap server. If one or more

0.0.0.0String<WiretapServer>(within <WiretapServer Group>)

<WiretapServer> keywords are set to validWiretap server addresses, Lustre lists thecontent of these servers in the browserbefore the results of the auto scan. If<ServerAuto> is set to OFF, only the spe-cified Wiretap servers are listed in thebrowser.

The IP address or DNS host name for aspecific Wiretap Gateway server.

0.0.0.0String<WiretapGatewayServer>(within <WiretapGatewayServerGroup>)

Allows you to map hostnames to IP ad-dresses, as well as to define path transla-tion rules.

0.0.0.0String<PathTranslation>(within <PathTranslationTable>)

Applies the correct aspect ration to NTSCresolution footage rendered to the

1.3333333333333Float<NTSCImageAspectRatio>

Wiretap server, but not imported fromthe Wiretap server.

Applies the correct aspect ratio to PALresolution footage rendered to the

1.3333333333333Float<PALImageAsepectRatio>

Wiretap server, but not imported fromthe Wiretap server.

<MonitoringAndCalibration>

Specifies the monitor display type (e.g.,LCD or CRT).

LCDEnumerated(abstract data)

<DisplayType>

Specifies the number of monitor calibra-tion steps performed.

10Integer<Calibration_Steps>

<ControlSurface>

When ON, this keyword enables theAutodesk Control Surface (ACS). When

OnState<AutodeskPanels>

OFF, Lustre enables the Tangent CP100control surface (if applicable).You must also set the path for the controlsurface rules file in the Panel Setup Filefield (refer to “System & Menu Settings”in the “Project Management” chapter ofthe Autodesk Lustre User Guide).

The ID numbers for the Function, Navig-ation, and Grading panels of the ACS.

function=”0”grading=”0”

<PanelIDs>

You must manually configure thesekeywords.If your control surface is a TangentCP100, Lustre does not use thesekeywords.

navigation=”0”



function=”101”grading=”100”

<PanelIPTags>

navigation=”102”

<Browsed>

All computers on the BrowseD networkmust use the same port to communicate.

NOTE For Linux over IP, set the portvalue to 1044.

1055Integer<Port>

Administrative user on the BrowseD server.rootString<Username>

Password for the administrative user.

NOTE To encrypt the password, set theattribute toEncrypt to yes. The nexttime the application starts, the passwordstring is encrypted in the configurationfile.

xxxString<Password>

Switch to ON if the networking protocolto use with BrowseD is the InfiniBand.

OffState<UseInfi>

0Integer<ReadCacheBuffer Num>

0Integer<ReadCacheThread Num>

Defines the IP address or DNS host namefor a specific BrowseD server.

0.0.0.0String<BrowsedServer>(within <BrowsedServer Group>)

<SlaveRenderer>

The IP address or DNS host name for aspecific Slave Renderer machine.

String<HostName>

Sets the timeout duration (in milli-seconds) of the automatic Slave Rendererdetection.

5000Integer<Timeout>

<Backburner>

The IP address or DNS host name for aspecific Backburner Manager machine.

String<Hostname>

<MatchCustomGroup>

Specifies the XML metadata field to beused by the Custom match option selec-ted from the Browse menu.“s” represents string.

“AliasName” type=”s”Name<MatchCustom>

“tc” represents timecode.“DPXTimeCode”type=”tc”

Name<MatchCustom>

“kk” represents keycode.“DPXkeycode” type=”kk”Name<MatchCustom>



“s” represents string.“DPXTapeNAME”type=”s”

Name<MatchCustom>

“s” represents string.“EDLReelName” type=”s”Name<MatchCustom>

“s” represents string.“DL_EDLClip_ name”type=”s”

Name<MatchCustom>

“i” represents integer.“DL_edlFrameID”type=”i”

Name<MatchCustom>

“tc” represents timecode.“DLEDL_startTC”type=”tc”

Name<MatchCustom>

<AVIO>

When OFF, it refreshes the Player as youare performing a playout. When ON, the

OffState<PlayoutHighSpeed>

Player is no longer refreshed and there-fore the performance of the playout im-proves.

Sets the delay for the SD first lead-in.1Integer<WTTFirstSDLeadIn Correction>

Delays all the lead-ins following the SDfirst shot.

2Integer<WTTSubsequentSD LeadInCor-rection>

Corrects the delay after the SD third shot.0Integer<WTTSDLeadIn Increment>

Sets the delay for the HD first lead-in.0Integer<WTTFirstHDLeadIn Correction>

Delays all the lead-ins following the HDfirst shot.

0Integer<WTTSubsequentHD LeadInCor-rection>

Corrects the delay after the HD third shot.0Integer<WTTHDLeadIn Increment>

The TimeCode Transition Delay specifiesthe number of milliseconds the applica-

10Integer<VtrTCTD>

tion waits before asking for timecodefrom the VTR. The default value of 10 msworks for most decks. For HDCAM-SRdecks use the following values:

■ 14, for 1080/59i/60 or 720/50/59/60

■ 21 for other timings

<Miscellaneous>

When this keyword is enabled, Lustre

reads the DPX / Cineon® file header of

OnState<DPXHeaderOffsetCheck>

each frame in a sequence. This is usefulwhen using DPX/Cineon files that have adifferent media offset within the samesequence of files. When disabled, Lustrereads only the first frame header of a se-quence.



WARNING Turning this keyword on canalter playback performance.

OnState<DisablePanScan Frame>

OffState<NVidiaSDISync>

0Integer<NVidiaPlayoutDelay>

2048Integer<BlockSize>

-1Float<AudioResyncTime>

0Integer<LoadingSetup>

OffEnumerated(abstract data)

<EnableKeykode Sending>

1.0Float<LoginGUIGain>

1.0Float<LoginGUIGamma>

Available for Incinerator® only.0Integer<ClusterPlayDelay>

Available for Incinerator only.OffState<ClusterSmooth Playback>

Allows the change cut or match gradefeature to preserve the keyframe anima-

OnState<ChangeCutOffset>

tions based on therecord timecodewhenever a shothas been replaced ormoved withina timeline.

NOTE Be sure to enable only the Recordbutton within the Match Option whenperforming a change cut or match grade.

OnState<AnimCopy_UsingTrimOff-set_Off>

Allows Burn rendering from a LustreWindows workstation to use CXFS SANpreallocation.

OffState<PreallocEnable>

OnInteger<FirstFrameNumber>

OnInteger<StartShotFrameNumber>

Possible values are:FastEnumerated(abstract data)

<DefaultDelivrablePanScanFilter>

■ Fast (Lanczos2 filter)

■ Quality (Lanczos2 filter)

■ Custom (BSpline filter)

<Debug>



Path to place the contents of a DLEDLwhen it is loaded in the timeline or Shotbin.

String<DumpDLEDLPath>

When ON, the attributes of a Wiretap clipare placed into a log file each time a clip

OffState<DumpWiretapCreate Clip>

is created on a Wiretap server. The fileWiretapClipDump.log is located in theLustre home folder. Use this keyword fordebugging only.

<FilmTypeGroup>

Various film types for AGFA, Kodak™,Eastman, and Fuji emulsions. It defines

Name<FilmType>

the relationship between the DPX filmemulsion code and the DPX film codenumber.


Manually ConfiguringMedia Storage


■ Overview on page 81■ Creating Hardware LUNs on page 81■ Partitioning Disks or LUN devices as Primary Partitions on page 82■ Assembling the Disk or LUN Devices into a Logical Volume on page 84■ Creating the XFS Filesystem on the Logical Volume on page 86■ Manually Creating a Mount Point and Mounting the Storage on page 87

OverviewThis section provides advanced instructions for manually configuring a storage array. Normally, you do notneed to perform any of these tasks, as they are all automatically performed by the XR Configuration Utility.

Creating Hardware LUNsLUNs, also referred to as Logical Units or Logical Drives, are groups of disk drives that are striped togetherto provide optimal performance and RAID protection. Once configured, LUNs are seen by the Linux operatingsystem as if they were single disk drives.

To create the LUNs on your XR-series storage, use the XR Configuration Utility supplied by Autodesk. Thisutility is installed with the DKU and automates the LUN creation process.

NOTE For systems having two sets of enclosures, you have to configure one set at a time with the XR ConfigurationUtility. Connect the first set of enclosures, and use the utility to configure it. When done, disconnect the first setand connect the second set. When the second set of enclosures is configured, re-connect both sets.

C

81

To configure LUNs on XR-series storage:


2 Go to the directory /usr/discreet/DKU/current/Utils/Storage/current/, and run the XR Configuration Utilityby typing:

./XR_config.pl

The utility detects whether a LUN configuration exists on the storage attached to that workstation.



4 After the script detects the number of enclosures and drives, it prompts you to indicate the filesystemyour storage uses.

Type 2.

5 When asked if you have a 2-loop or a 4-loop configuration, select the option that applies to your storage.

The XR Configuration Utility configures your storage.

6 Type x to exit the XR Configuration Utility.

7 Reboot your workstation, so that the newly-created LUNs are rescanned by the operating system.

Note that the XR Configuration Utility exits without configuring your storage if any of the following issuesare detected:

■ An incorrect number of disks. The total number of disks must be a multiple of 12.

■ One or more of the enclosures do not have the correct firmware.

■ In a dual RAID enclosure environment, the number of expansion chassis on each RAID enclosure is notthe same.

■ An odd number of enclosures in a 4-loop configuration. Only even numbers of enclosures are supported.

Partitioning Disks or LUN devices as Primary PartitionsTo achieve optimal performance, each disk or LUN in the array should be partitioned as a single primarypartition.

On storage arrays with 450 GB drives, use the parted utility to create GPT (GUID Partition Table) typepartitions. On arrays with smaller drives, use the fdisk utility to create Linux LVM type partitions.

NOTE Make sure you do not re-partition the system drive or any other disks that you want to preserve as theyare. Partitioning destroys all data on the disks.

To partition disk or LUN devices with 450 GB drives or larger:

1 Reboot your system to reload the fibre channel adapter drivers.


3 View a list of disks or LUN devices detected by the operating system, using the following command:

fdisk -l | grep dev

82 | Appendix C Manually Configuring Media Storage

Identify the disk or LUN devices that are part of the storage array to be configured with a standardfilesystem. These devices will be re-partitioned.

4 Use the parted command to re-partition each disk device identified in the previous step. Type:

/sbin/parted -s -- <disk name> mklabel gpt mkpart primary 0 -1

where <disk name> is the name of a disk device identified in step 1, without a partition number,such as /dev/sdb. For example:

/sbin/parted -s -- /dev/sdb mklabel gpt mkpart primary 0 -1

5 Repeat the command for each disk.

To partition disk or LUN devices with drives smaller than 450 GB:

1 Reboot your system to reload the fibre channel adapter drivers.


3 View a list of disks or LUN devices detected by the operating system, using the following command:

fdisk -l | grep dev

Identify the disk or LUN devices that are part of the storage array to be configured with a standardfilesystem. These devices will be re-partitioned.

4 If you plan to configure a standard filesystem on a former Stone FS storage array, delete the volumelabel and volume table on each LUN device that is part of the storage array. Type the following commandfor each LUN device:

dd if=/dev/zero of=<LUN device> count=4096

Where <LUN device> is the device name of a LUN in your storage array, such as /dev/sdc.

WARNING When using the dd command, be very careful to not delete your system drive (usually /dev/sda)or any other drive aside from the LUNs in your storage array.

5 Use the fdisk command to re-partition each disk device identified in the previous step.

Start the fdisk utility for the LUN. Type:

fdisk <disk name>

where <disk name> is a disk device name without a partition number, such as /dev/sdf.

The fdisk utility starts, checks the disk device, and then displays its prompt.

NOTE When fdisk starts, a warning about the number of disk cylinders may appear. You can disregard thiswarning.

6 Type n to display the New partition creation menu.

fdisk displays the type of partitions you can create (primary or extended).

7 Create a primary partition on the disk device by typing p at the prompt.

8 When prompted to enter a partition number, type 1 to make the primary partition the first one on theLUN.

NOTE You may have to delete pre-existing partitions by entering d when prompted, and repeating step 3.

9 When prompted to set the starting cylinder number, press Enter twice to accept the defaults, which arethe first and last cylinder on the device.

The fdisk prompt reappears.

Partitioning Disks or LUN devices as Primary Partitions | 83

10 Type t to set the partition type.

You are prompted to enter the hexadecimal code of the partition type to be created on the LUN.

11 Type 8e to set the partition type to Linux LVM.

fdisk sets the partition as Linux LVM and the following output appears:

Changed system type of partition 1 to 8e (Linux LVM)

12 Type w to save the new partition table.

13 Repeat steps 2 through 9 for each disk or LUN device identified in step 1.

Assembling the Disk or LUN Devices into a Logical VolumeAfter you have formatted each disk or LUN device as a partition, you must assemble the LUNs into a singlelogical volume on which you create the XFS filesystem.

This procedure does not cover creating fault-tolerance and assumes that the LUNs are RAID-protected, as isthe case with Stone Direct XR-series arrays.

To assemble a logical volume:

1 Verify that the disk or LUN devices are detected by the operating system. Type:

fdisk -l | grep dev

All devices appear in a list similar to the following example (your values may vary):

/dev/sdb1 1 180482 1449713663+ ee EFI GPT

/dev/sdc1 1 180482 1449713663+ ee EFI GPT

/dev/sdd1 1 180482 1449713663+ ee EFI GPT

/dev/sde1 1 180482 1449713663+ ee EFI GPT

Partitions created with the parted command for arrays with 450 GB disks are marked “EFI GPT”.

Partitions created in fdisk for arrays with smaller capacity disks are marked “Linux LVM”.

NOTE Other devices of different types may be listed before and after the GPT or LVM devices.

2 Create a physical volume on each of the devices using the following command:

pvcreate <list of devices>

where <list of devices> is a list of all the devices in the storage array. For example, if you havefour devices, ranging from /dev/sdb1 to /dev/sde1, you would type:

pvcreate /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1

The physical volumes are created, and the command output should be similar to the following example:

Physical volume "/dev/sdb1" successfully created

Physical volume "/dev/sdc1" successfully created

Physical volume "/dev/sdd1" successfully created

Physical volume "/dev/sde1" successfully created

TIP You can use the command pvremove to delete any erroneously entered devices.

3 Verify that the physical volumes were initialized correctly. Type:

pvscan -v


A list of all of the physical volumes you created appears. The following sample output is for the previousexample of 4 physical volumes created on devices /dev/sdb1 through /dev/sde1:

Walking through all physical volumes

PV /dev/sdb1 lvm2 [2.03 TB / 2.03 TB free]

PV /dev/sdc1 lvm2 [2.03 TB / 2.03 TB free]

PV /dev/sdd1 lvm2 [2.03 TB / 2.03 TB free]

PV /dev/sde1 lvm2 [2.03 TB / 2.03 TB free]

Total: 4 [8.10 TB] / in use: 0 [0 ] / in no VG: 4 [8.10 TB]

4 Create the volume group “vg00” from the physical volumes you created in the preceding step, usingthe following command:

vgcreate vg00 <list of volumes>

where <list of volumes> is the list of physical volumes you created in the preceding step. Forexample:

vgcreate vg00 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1

TIP You can use the command vgremove to delete any erroneously entered volume.

5 Verify the volume was created and obtain the value of the “Free PE / Size” field. Type:

vgdisplay -v

In the output, find the line that contains the “Free PE / Size” field and write down the value of the “FreePE”. For example, in the following example output the “Free PE” value is 2124556.

Free PE / Size 2124556 / 8.10 TB

6 Create a new logical volume on “vg00”, using the following command:

lvcreate -l <Free_PE_value> -i <#_of_physical_volumes> -I 32 -n lvol1vg00

where <Free_PE_value> is the “Free PE” value you noted in the preceding step and<#_of_physical_volumes> is the number of physical volumes. If we continue with the exampleused in the previous steps, you would type:

lvcreate -l 2124556 -i 4 -I 32 -n lvol1 vg00

The output confirms the creation of the logical volume:

Logical volume “lvol1” created

NOTE If the command outputs several lines about a file descriptor leaked on lvdisplay invocation, ignorethem.

7 Check if the adsk_lvm startup script has been installed by the DKU to enable automatic logical volumereassembly upon reboot:

chkconfig --list | grep adsk_lvm

If the script is properly configured, the command output is the following:

adsk_lvm 0:off 1:off 2:on 3:on 4:on 5:on 6:off

If the command output is different, enable the script by typing:

chkconfig --add adsk_lvm

chkconfig adsk_lvm on

Assembling the Disk or LUN Devices into a Logical Volume | 85

Creating the XFS Filesystem on the Logical VolumeAfter having created the logical volume, you are now ready to create and mount the XFS filesystem.

To create and mount an XFS filesystem:

1 Identify the optimal agsize value for your array by running the mkfs.xfs command. Type:

mkfs.xfs -d agcount=128 -f /dev/vg00/lvol1

This command displays diagnostics information similar to the following (your values may differ):

meta-data=/dev/vg00/lvol1 agcount=128, agsize=1066667 blks

= sectsz=512 attr=0

data = bsize=4096 blocks=134400000, imaxpct=25

= sunit=16 swidth=64 blks, unwritten=1...

2 From the diagnostic information printed in the previous step, note the following values:

■ agsize on the first line

■ sunit and swidth on the fourth line

3 Depending on the values of sunit and swidth, calculate a new agsize value using one of the followingthree methods:

■ If the values of sunit and swidth are both equal to 0, multiply the agsize value by 4096. For example(your values will differ):1066667 * 4096 = 4369068032

Proceed to step 4 using the value calculated above as the new agsize value.

■ If the command displays a warning message about the agsize being a multiple of the stripe width,multiply the agsize value by 4096, and subtract the sunit value multiplied by 4096. For example(your values will differ):1066667 * 4096 = 4369068032

16 * 4096= 65536

4369068032 - 65536 = 4369002496

Proceed to step 4 using the value calculated above as the new agsize value.

■ If the values of sunit and swidth are not equal to 0, and no warning message appears, proceed to step4 using the agsize value displayed by the mkfs.xfs command in step 1.

4 Run the mkfs.xfs command again to create the XFS filesystem on the device /dev/vg00/lvol1 using thevalue calculated in one of the previous steps. Type:

mkfs.xfs -d agsize=<new agsize> -f /dev/vg00/lvol1

For example (your values will vary):

mkfs.xfs -d agsize=4369068032 -f /dev/vg00/lvol1

The filesystem is created on the storage array.

NOTE If the command fails, redo your calculations starting from step 1.

5 Verify that the storage can be mounted by typing one of the following commands:

■ For HP Z800 systems: mount /mnt/StorageMedia

■ For older systems: mount /mnt/stoneMedia


The storage should mount, as the DKU installation script should have created the mount point directoryfor your storage (/mnt/StorageMedia on HP Z800 workstations, or /mnt/stoneMedia on older workstations),as well as the corresponding entry in the /etc/fstab file.

If you receive an error message and the storage does not mount, follow the instructions in the nextsection to manually mount the storage.

Manually Creating a Mount Point and Mounting the StorageIf the mount point directory for your storage was not created automatically by the DKU, or if the storagedoes not mount, perform the following procedure to create the mount point and mount the storage manually.

To create a mount point and mount the storage:

1 Create the directory that will serve as the mount point for the filesystem, if it does not exist. For example:

mkdir /mnt/StorageMedia

WARNING Do not use the word “stonefs” as the name for your mount point directory. “Stonefs” is a reservedword, and can cause issues if used as the mount point directory name.

2 Mount the XFS filesystem from the logical volume /dev/vg00/lvol1 on the directory you created in theprevious step. For example:

mount -av -t xfs -o rw,noatime,inode64 /dev/vg00/lvol1 /mnt/StorageMedia

The filesystem is mounted as /mnt/StorageMedia.

3 Confirm that the storage is now mounted. Type:

df -h

The output should list /dev/mapper/vg00-lvol1 mounted on your mount point directory. For example:

/dev/mapper/vg00-lvol1

814G 547G 267G 68% /mnt/StorageMedia

4 Using a text editor, add an entry in the /etc/fstab file so that the filesystem gets mounted automaticallyat startup. For example:

/dev/vg00/lvol1 /mnt/StorageMedia xfs rw,noatime,inode64

5 Optional: Confirm that the filesystem can mount automatically by rebooting the workstation andusing the command df -h again.

Manually Creating a Mount Point and Mounting the Storage | 87

Index

A

applicationlicensing 45uninstalling 71

audioDiscreet Native Audio 13hardware components 13wiring workflow 13

audio converter 14Autodesk Control Surface

configuration file 30connecting 11

B

Backburner Managerconfiguring 58detecting in Lustre 65detecting with Backburner Server 64installing 58overview 56

Backburner Monitorinstalling 58overview 56

Backburner Serverdetecting Backburner Manager 64overview 56starting 64

background renderingcomponents 55configuring in Lustre 65overview 55setting up render nodes 59setup, workflow 57storage, mounting 60with BrowseD 70

broadcast monitor, wiring 13BrowseD

accessing directories from Lustre 69configuring, workflow 68overview 67remote rendering 70starting and stopping 68using 68

browsed.configconfiguring 68

Burn for Lustrehardware and software requirements 59installing and configuring 62

license 62overview 56

C

configuration fileoverview 73

configuringAutodesk control surface (Lustre) 30Backburner Manager 58browsed.config 68Burn for Lustre 62

connectingaudio 13video I/O components 13video I/O devices 13workstation peripherals (illustration) 11

control surfaceAutodesk Control Surface, connecting 11

customer supportcontacting 2

D

Discreet Kernel Utility version 33Discreet Native Audio 13DKU version 33documentation

about this guide 1conventions 2

F

floating licensesbackground rendering 62

H

hardwarerequirements, Burn for Lustre 59

hardware configuration guidelines 7host ID, obtaining 46

I

installationoverview 8

89 | Index

installingBackburner Manager 58Backburner Monitor 58Burn for Lustre 62Lustre (Linux) 43

L

licensebackground rendering, floating 62Burn for Lustre 62

license codesrequesting 47

license serverbackground rendering 62

Linux version 25Lucid ADA 88192.See audio converterLustre

accessing BrowseD directories 69detecting Backburner Manager 65installing (Linux) 43starting 48

M

mount pointsoverview 56

multicastingLinux 28

N

NASusing BrowseD 67

networkingmulticasting, Linux 28

O

operating system requirements 25

P

PDF documentation, accessing 2powering on or off, sequence for 38projects

setting up slave rendering 53

R

Red Hat Linux version 25

render nodessetting up 59

renderingwith BrowseD 70

requirementsDKU 33operating system 25Red Hat Linux version 25

S

SANusing BrowseD 67

shutdown sequence 38slave rendering

configuring, workflow 49setting up Lustre projects 53

softwarerequirements for Burn for Lustre 59

storageworkflow for configuring 37

supportcontacting 2

T

tar file, uncompressing 44

U

uninstalling the application 71

V

video I/O, wiring 13video wiring 13VTR

connecting 13

W

wiring video I/O and broadcast monitor 13workflow

configuring BrowseD 68configuring slave rendering 49licensing 45setting up background rendering 57storage configuration 37

workflowsaudio wiring workflow 13

90 | Index

installation and conﬁ guration guide for linux...

Documents