Autodesk Flame ® ® Premium 2013 Extension 2 A Discreet® creative finishing products 20th Anniversary Edition Installation and Configuration Guide for Linux Workstations ®
© 2012 Autodesk, Inc. All rights reserved. Except as otherwise permitted by Autodesk, Inc., this publication, or parts 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. Portions related to MD5 Copyright © 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.
Editing, Navisworks, ObjectARX, ObjectDBX, Opticore, Pipeplus, Pixlr, Pixlr-o-matic, PolarSnap, PortfolioWall, Powered with Autodesk Technology, Productstream, ProMaterials, RasterDWG, RealDWG, Real-time Roto, Recognize, Render Queue, Retimer, Reveal, Revit, RiverCAD, Robot, Scaleform, Scaleform GFx, Showcase, Show Me, ShowMotion, SketchBook, Smoke, Softimage, Softimage|XSI (design/logo), Sparks, SteeringWheels, Stitcher, Stone, StormNET, Tinkerbox, ToolClip, Topobase, Toxik, TrustedDWG, T-Splines, U-Vis, V
Contents Chapter 1 Installation workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 2 System Chapter 3 Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Typical configuration overview for Creative Finishing applications . . . . . . . . . . . . . . . . . . . . 6 Typical Configuration Overview for Lustre . . . . . . . .
Configure Lustre slave rendering . . . . . . . . Lustre background rendering . . . . . . . . . . Configure Lustre BrowseD . . . . . . . . . . . . Advanced Configuration and Troubleshooting . Chapter 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 . 48 . 55 . 56 Licensing and Starting . . . . . . .
Installation workflows 1 This guide covers the following: ■ Flame Premium ■ Flame ■ Smoke for Linux ■ Lustre ■ Inferno ■ Flint ■ Backdraft User prerequisties for installation ■ Knowledge of Linux, preferably Red Hat. ■ Familiarity with computer hardware, storage and networking in a professional video/film production environment. ■ Root access to your system. The default root account password on an Autodesk workstation is password.
■ Audio hardware for your workstation. ■ Storage arrays to the workstation, but do not power them on before having installed Linux, to prevent the Linux installer from attempting to format the arrays and use them as system drives. 2 Configure BIOS (page 23). 3 Install Linux (page 27). 4 Install the DKU and the AJA OEM-2K firmware (page 29) 5 If you are using a new Stone Direct storage array, Configure storage (page 30) 6 Install Flame Premium (page 39) 7 Configure Creative Finishing Software (page 43).
2 System requirements Hardware requirements Supported Workstations Workstation Supported Software Supported BIOS Versions Operating System HP Z820 All Creative Finishing software 2.08 Red Hat Enterprise Linux Desktop 6.2 with Workstation Option (64-bit) HP Z820 shipped before 15 Jan. 2013 All Creative Finishing software 1.14 Red Hat Enterprise Linux Desktop 6.2 with Workstation Option (64-bit) HP Z800 All Creative Finishing software 3.07 Red Hat Enterprise Linux Desktop 5.
OS & software requirements Nodes purchased from Autodesk ship with the correct Autodesk distribution of Red Hat Enterprise installed and configured. You should only need to install Linux in the following situations: ■ You are setting up a render node that was not purchased from Autodesk, in which case you need CentOS 5.3. If you have older nodes running Fedora Core or CentOS 4.6, you do not need to upgrade them to CentOS 5.3.
Hardware configuration 3 If you are only upgrading an existing application, you do not need to reconfigure your hardware. This section contains wiring diagrams for HP Z800 workstation with the NVIDIA 6000 graphics card and the AJA KONA 3G. It does not contain information and diagrams for the older workstations supported in this version. If you have an HP Z800 with an NVIDIA 5800 graphics card, see the HP Z800 Workstation Hardware Setup Guide PDF.
Typical configuration overview for Creative Finishing applications Typical configuration Typical Configuration Overview for Lustre 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 the components in your installation.
There are two kinds of Lustre workstations: ■ The Master Station is designed for GPU-accelerated sessions where the colorist works together with the cinematographer. It includes a toolset for visual design and grading, using up to 4K resolution and 16-bit files and for completing tasks like dust busting, conforming, rotoscoping, and capture/playout.
A typical Lustre workgroup configuration built around a Master Station.
Peripheral connections overview The Z820 with the optional NVIDIA SDI2, AJA KONA 3G and 2-port GigE adapters. Optionally, your workstation can be set up with a second ATTO Fibre Channel adapter in slot 1.
The Z800 with a 2-port GigE adapter in slot 1 (top to bottom), and a Mellanox QDR InfiniBand / 10-GigE adapter in slot 7. Optionally, your workstation can be set up with a second ATTO Fibre Channel adapter in slot 1.
Connect video components HP Z820 Video I/O The only video hardware you must provide are a sync generator, VTR, HD/SDI-ready broadcast monitor and patch panel (if desired). Some of the following steps might not be necessary depending on your hardware configuration. Connection procedure: 1 Connect the output of the sync generator to the top Ref Loop port of the AJA K3G-Box. 2 Connect the Input port of the NVIDIA SDI card (the one next to the DVI port) to the bottom Ref Loop port of the AJA K3G-Box.
The only video hardware you must provide are a sync generator, VTR, HD/SDI-ready broadcast monitor and patch panel (if desired). 1 Connect the output of the sync generator to the top Ref Loop port of the AJA K3G-Box. 2 Connect the Input port of the NVIDIA SDI card (the one next to the DVI port) to the bottom Ref Loop port of the AJA K3G-Box. 3 Connect the Fill (outer) port of the NVIDIA SDI card to the Input port of the AJA HD5DA distribution amplifier.
Connect the Discreet Native Audio hardware components to the AJA breakout box Connect media storage Do not power on your storage before installing Linux. If you do, the Linux installer might attempt to format the storage array and use it as the system disk. The workstation can be connected to two types of media storage: ■ Stone Direct disk arrays: Autodesk's high-performance direct-attached storage (DAS) for individual workstations.
Connecting the Fibre Channel Adapter On HP Z800 workstations, connections to media storage are made using the ATTO Celerity FC84-EN fibre channel adapter, located in slot five (top to bottom). The fibre channel adapter is equipped with four ports, called loops. You can connect your storage enclosure to the fibre channel cards using either 2 loops or 4 loops. A 2-loop device can be connected to either the inner pair of ports or the outer pair of ports.
The storage can be connected to the workstation through either 2 FC loops or 4 loops. 2-loop configuration: On ATTOcards 2 micro chips handle fiber traffic to the four ports: chip A handles ports 1 and 2 and chip B handles ports 3 and 4. To get maximum storage performance in a 2 loop configuration, the fiber loops should be distributed across the two chips.
Connecting XR 6500 Storage The 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. A XR 6500 RAID enclosure supports a maximum of seven XE expansion enclosures. Configurations with two XR RAID enclosures are not supported.
Connect media storage | 17
Notes: ■ In a 4-loop configuration, you need a minimum of one XE expansion enclosure attached to the XR 6500 RAID enclosure.
■ The total number of enlcosures must be an even number. Connecting XR 6412 Storage The 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 with two XR RAID enclosures are not supported.
NOTE In a 4-loop configuration with a XR 6412 RAID enclosure, you need a minimum of one XE expansion enclosure attached to the XR RAID enclosure. Connecting XR 5402 and XR 5412 Storage The following digrams illustrate 2-loop and 4-loop connections for XR 5402 and XR 5412 series storage assemblies. 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.
NOTE The XR 5402 and XR 5412 RAID enclosures support a maximum of four XE expansion enclosures.
NOTE In a configuration with two XR RAID enclosures, the number of XE extension enclosures per XR RAID enclosure must be the same. The total number of enclosures in the storage assembly must be an even number. Connect Archive Storage (not Lustre) Archiving to USB 2.0, FireWire (IEEE 1394) and fibre channel devices is supported. This includes filesystems, tape drives, and VTRs. For information on connecting a VTR, see Connect video components (page 11). Filesystem Devices USB 2.
While Autodesk Media and Entertainment makes no certification statement about any tape drive device, you can use the “Tape Drive Test” plug-in in Autodesk SystemCentral to test SCSI tape drives for compatibility. For more information, see the Autodesk SystemCentral User Guide. Configure BIOS Z820 If BIOS settings are not set up correctly before installing Linux, you will need to reinstall the OS.
BIOS Menu Submenu Item Value Slot 7 Option ROM Download Disable Z800 The BIOS of your workstation is correctly configured prior to shipping, so you normally do not need to perform the procedures in this section. This section contains information on the certified BIOS settings for the HP Z800 workstation, as well as instructions on updating your BIOS and restoring it to the default factory settings.
Storage Storage Options SATA Emulation RAID+AHCI NUMA Split Mode Disable S5 Wake on LAN Disable Internal Speaker Disable NIC PXE Option ROM Download Disable Slot 1 PCIe2 x8(4) Option ROM Download Disable Slot 3 PCIe2 x8(4) Option ROM Download Disable Slot 4 PCIe2 x16(8) Option ROM Download Disable Slot 6 PCI32 Option ROM Download Disable Device Options Configure BIOS | 25
26
Install Linux 4 To prepare your system and perform a fresh install of Red Hat Enterprise Linux. 1 If reinstalling Linux on an existing system, back up all user settings, project settings, and media from the system disk to other media. The Linux installation formats the system disk, resulting in total data loss.
6 If prompted, initialize the system disk. The test of the installation is automatic. 7 When the installation has completed, eject the disc and reboot the system. After the system reboots, you may be prompted by the Kudzu hardware setup utility to set up new hardware detected for your system. You can ignore these prompts and allow the utility's count-down to expire since the hardware for the system is unchanged.
/etc/sysconfig/network-scripts/ifcfg-ethn Edit /etc/sysconfig/network-scripts/ifcfg-ethn, where n specifies the ethernet port number, usually 0 for the first on-board port. If your workstation has an add-on ethernet card installed, the Linux operating system may assign ports eth0 through eth3 to the add-on card. In such a case, the on-board Ethernet ports become eth4 and eth5. Optionally set the GATEWAY if not set in /etc/sysconfig/network.
Install the DKU WARNING Do not attempt to install the current version of the DKU on unsupported platforms, including older Creative Finishing systems. This will result in the installation script only installing a generic configuration which can render your operating system unusable. To install the DKU: 1 Prepare the installation media (page 39). 2 3 Run the install script (for example from the USB device): /mnt/usbdisk/DKU-/INSTALL_DKU.
The workstation must be running the custom Autodesk distribution of Red Hat Enterprise Linux, and the correct DKU. If you are configuring an XR storage array with two sets of enclosures, connect only one set of enclosures, 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. Workflow 1 Set up any Storage Area Network (SAN), before setting up a DAS.
Configure XR storage Create LUNs 1 In a terminal, as root, run /usr/discreet/DKU/current/Utils/Storage/XR/XR_config.pl. The XR Configuration Utility exits without configuring your storage if any of the following is true: ■ The total number of disks is not a multiple of 12. ■ One of more of the enclosures does not have the correct firmware. ■ When using two sets of enclosures, the number of expansion chassis attached to each XR RAID enclosure is not the same.
2 Create the LUNs. 3 Power off the workstation again, connect both sets of enclosures to the workstation. 4 Power the workstation back on and Create the XFS filesystem. To perform only the filesystem creation operations: 1 In a terminal, as root, run /usr/discreet/DKU/current/Utils/Storage/current/XR_config.pl --createFS. The configuration utility partitions the storage array, groups the partitions into a logical volume, creates the XFS filesystem on the volume, and mounts the volume.
Creating Hardware LUNs LUNs, also referred to as Logical Units or Logical Drives, are groups of disk drives that are striped together to provide optimal performance and RAID protection. Once configured, LUNs are seen by the Linux operating system as if they were single disk drives. For systems with two sets of enclosures, you have to configure one set at a time with the XR Configuration Utility. Connect the first set of enclosures, and use the utility to configure it.
4 Repeat 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. 2 Open a terminal, and log in as root and view a list of disks or LUN devices detected by the operating system: fdisk -l | grep dev. Identify the disk or LUN devices that are part of the storage array to be configured with a standard filesystem. These devices will be re-partitioned.
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”. 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: pvcreate where is a list of all the devices in the storage array.
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: 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 following three methods: ■ If the values of sunit and swidth are both equal to 0, multiply the agsize value by 4096.
4 Append a line to /etc/fstab so the filesystem is mounted at 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 and using the command df -h again.
Installing Your Software 5 Prepare the installation media Check the release announcement to find out on what media the installers are available. Major releases are distributed on a USB device. To mount a USB device: ■ Attach the device. Log in to the terminal as root. On Red Hat 6, change directory to the USB mount point at /media/AUTODESK/. If you're using Red Hat 5, continue with the following steps. ■ Use the dmesg command to output something like sdf: sdf1 to list a recent device connected.
Install the software: 1 Log in to your workstation as root and open a terminal. Go to the application installation directory. Start the application installation script. Use with the command ./INSTALL_APPLICATION, where SOFTWARE is the name of the software to be installed, e.g. ./INSTALL_FLAMEPREMIUM. If installing an educational version, add the switch --edu, e.g. ./INSTALL_FLAMEPREMIUM --edu.
■ To use the new configuration file without adding the settings from the old configuration file, just close the program. 6 If you modified the xorg.conf file, you are prompted to restart the X server. When the installation script completes, log out of the Linux desktop and then log in again to restart the X server. The application, as well as additional components (WiretapCentral, Wiretap Gateway, Backburner Server, Backburner Manager, Backburner Media I/O Adapter) are installed on your workstation.
42
Software configuration 6 Configure Creative Finishing Software This is necessary for new installations. For an upgrade you do not need to repeat these procedures, unless adding new media storage devices. The only task you might need to perform when upgrading from a previous version is upgrading projects to the current version and transferring clip libraries.
■ On the mounted filesystem create the Managed Media Cache directory. The name should include the partition name and the hostname. Set permissions for the directory to be readable, writable, and searchable by the owner and its group, and readable and searchable by all: 1 mkdir -p /mnt/StorageMedia/smoke1/p7 2 chown -R root:users /mnt/StorageMedia/smoke1/p7 3 chmod -R 775 /mnt/StorageMedia/smoke1/p7 ■ Optionally create separate mount points and Managed Media Cache directories for each additional volume.
4 To enable remote access to clip libraries, in /etc/exports specify all directories you want remote hosts to be able to access. You can export the entire/usr/discreet directory to enable remote access to all clip libraries, projects, user preferences and setups. Or you can export only certain subdirectories, such as/usr/discreet/clip or /usr/discreet/project.
Backburner Server and Backburner Manager are installed with the Autodesk Creative Finishing application, and are set to run automatically when the workstation starts. By default, the Backburner Server installed on the workstation communicates with the locally installed Backburner Manager. Use the following procedure to configure Backburner services on your workstation. To configure Backburner services: 1 Make sure Backburner Server is set to run automatically on your workstation.
Configure Lustre slave rendering The Slave Renderer renders modified frames when the artist moves to the next shot on the timeline from the Master Station. With slave rendering, playback is enabled without compromising the interactivity of the Master Station during creative sessions. Prerequisites 1 Install Linux (page 27) and the DKU. 2 Connect the Slave Renderer to a switch on your house network.
7 Render shots as you work. See Autodesk Lustre User Guide Lustre background rendering During background rendering, a shot on the timeline is rendered by a background rendering network. This is different from the Slave Renderer, which renders shots on a shot-by-shot basis as they are colour graded to enable improved playback performance. Background rendering in Lustre is performed using Burn for Lustre, also known as the Lustre Background Renderer.
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 jobs are submitted for background rendering through the Render | Backburner menu. Backburner Manager This is the hub of the background rendering workgroup.
Burn for Lustre This is the Linux rendering engine that renders one or more frames from Lustre render jobs. NOTE Burn for Lustre is a different software than Burn for Creative Finishing software. While they can co-exist on the same node, the installation and configuration procedures are different. For information about how to set up Burn for Creative Finishing software, consult the Autodesk Burn Installation and User Guide.
3 If the system on which you are installing Backburner runs Linux in graphical mode, you are asked if you want to automatically run Backburner Manager and Backburner Server on the machine. Answer Yes to the question about the Manager, and No to the question about the Server. 4 Run the Backburner Web Monitor configuration script: /usr/discreet/backburner/backburnerConfigWeb.
2 Insert the first installation disc of your Linux distribution into the drive. You do not need to mount it at this time. 3 Extract an ISO image of the disc: dd if=/dev/ of=/ 4 Eject the disc. 5 In the Lustre installation package run dist/build_kickstart_cd the kickstart file is at dist/ks_centos5_rh5.cfg. This script adds the kickstart file dist/ks_centos5_rh5.cfg to the ISO image of your Linux distribution DVD: .
Install Burn for Lustre on render nodes When you install Burn for Lustre, the necessary Backburner components are also installed on the render node. Perform the following procedure to install the Burn for Lustre software on each node. 1 Open a terminal to the render node, and log in as root. 2 If you are installing from a USB key, insert the key navigate to the Lustre install directory. 3 If you are installing from a downloaded tar file, unpack the tar file by typing: tar zxvf .tar.gz.
Configure backburner server to detect Backburner Manager Backburner Server needs to be able to detect the location of Backburner Manager to provide status information concerning the render jobs: 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. You can also use the hostname of the machine, if it has been properly defined in the /etc/hosts file.
required in these fields is comprised of the directory defined for the mount point and the actual storage folder. For example, if the Project Home on the Lustre workstation is E:\SCENES/mnt/md0/SCENES in the Project Setup menu, and the mount point for the Lustre workstation storage on the Linux render nodes is /mnt/Lustre_storage, the Project Home path to enter in this menu is: /mnt/Lustre_storage/SCENES 5 Press Enter.
Port All computers on the BrowseD network must use the same port to communicate. Set to 1055, the default. If configuring a render node or a workstation running on a GigE network, set this as 1044. If configuring a render node or a workstation running on a high-speed InfiniBand network, set this as 1055. BrowsedServer Defines the IP address or DNS host name for a specific BrowseD Server. UseInfi Enable this option if the networking procotol to use with BrowseD is InfiniBand.
are referred to as “hooks”. You can enter Python commands directly inside these functions, or use the functions to call an external script or executable. NOTE To be able to run shell commands or external script using the os.system Python statement, add the following line in the hook.py script, before the definition of the first hook: import os Note the following about hook functions: ■ Functions in hook.py receive certain predefined parameters from the application.
description A string that describes the video preview timing, as listed in the init.cfg file. For example, 1920x1080@5994i_free. width An integer that specifies the width of the preview timing. For example, 1920. height An integer that specifies the width of the preview timing. For example, 1080. bitDepth An integer that specifies the bit depth of the preview timing. For example, 12. rateString A string that specifies the refresh rate of the preview timing. For example, 6000i.
return Value A new exportPath. Empty strings or non-string return values are ignored, while invalid paths cause the export to fail with a path error. void batchExportEnd( string nodeName, string exportPath, string resolvedPattern, int firstFrame, int lastFrame, string gatewayClipPath, int versionNum, bool aborted ) This hook is called when an export ends. This function is a complements the batchExportBegin function described above.
To configure the path translation database: 1 Consider your network environment and how you can organize hosts to simplify the path translation process. Do you have many hosts accessing the same storage device? Do they mount the central storage using the same syntax and drive names? Are these hosts running the same application? Are they running the same operating system? 2 Open /usr/discreet/wiretap/cfg/sw_wiretap_path_translation_db.xml in a text editor. 3 Create the rules for translating the file path.
Attribute Description dst_host The host name or IP address of the client that mounts the same storage referred to by the source, using a different syntax. If you create a group rule for destination workstations, the value of this attribute can be the group name. dst_path The path to the remote storage as referred to by the destination host (or hosts, when mapping a group).
After you have defined a group, you can use the host/path rule to map all the hosts in the group to the same path by using the group name for either the src_host or dst_host attribute value.
Attribute Description src_path The path to the remote storage as referred to by all hosts using the same operating system dst_os The operating system of the client that mounts the same storage referred to by the source dst_path The path to the remote storage as referred to by the hosts running the destination operating system Example:
For example, suppose you have a SAN mounted as “/CXFS1” on your Flame workstation (flame1). A Windows PC (windows1) will mount the SAN as “N:\”. The path translation file contains the following entries:
■ Separate your media and metadata partitions. The worst contributors to fragmentation on a media storage device are the files used to store metadata. These include clip libraries, setup files, and databases. It is recommended to keep all metadata on a separate partition. NOTE You may keep the audio data on the same partition as the frames. This has no significant impact on performance or filesystem fragmentation. ■ Use the defragmentation tools provided by your filesystem vendor on a regular basis.
Each partition managed by the Bandwidth Manager must have a [Device] section associated to it in the /usr/discreet/sw/cfg/sw_bwmgr.cfg file. To add a new device to the Bandwidth Manager: 1 Open the /usr/discreet/sw/cfg/sw_bwmgr.cfg file in a text editor. 2 Add a new [Device] section at the end of the file, using the following syntax: TIP You may also copy and paste an existing [Device] section, and change its parameters.
Reserving Bandwidth for an Application You may define a bandwidth reservation for each Creative Finishing application or tool that uses a certain partition. By default, a group reservation for the major Creative Finishing applications (Inferno, Flame, Flint, Smoke, and Backdraft Conform) running locally is already defined. Remote applications are identified by application-specific tokens, workstation host name, as well as the user name under which the application is executed.
In the following example, low-bandwidth values are configured for each process (300 MB/s for Flame, 100 MB/s for Flare, 10 MB/s for Wiretap and 10 MB/s for Wire). The diagram illustrates the way the Bandwidth Manger redistributes device bandwidth as the total available bandwidth decreases from 800 MB/s to 420 MB/s and then to 320 MB/s. Note how the Bandwidth Manager keeps the bandwidth for each application at the low bandwidth watermark.
Perform the steps in the procedure below to set up an optimal bandwidth reservation for the local application, as well as for remote workstations, based on your system configuration. To set up bandwidth reservation: 1 Open a terminal and log in as root. 2 Open the /usr/discreet/sw/cfg/sw_bwmgr.cfg file in a text editor. 3 Locate the [Device] section that corresponds to the standard filesystem partition (by default [Device0]), and uncomment it if it is commented out.
Reservation= [] [@] [()] [][))] where: ■ is the ID of the reservation, starting at 1 for each device. ■ represents the name of the application that needs the reserved bandwidth.
By default, the configuration file already contains a definition for the “IFFFS” group, which includes the “inferno”, “flame”, “flint”, and “smoke” application tokens. To set up bandwidth reservation for a group of applications: 1 Open the /usr/discreet/sw/cfg/sw_bwmgr.cfg file in a text editor. 2 In the [Groups] section, add a line for each group of applications you want to define.
5 Save and close the configuration file. 6 Restart Stone and Wire: /etc/init.d/stone+wire restart. Use multi-threaded direct input output Most filesystems perform best when the I/O is parallelised across multiple threads/processes and sent asynchronously. This allows the device to buffer I/O operations and reorganize requests for optimal performance. Some applications perform better than others on the same storage device, based on how they perform their I/O.
NOTE If you are using XFS and unwritten extent flagging was disabled when creating the filesystem, the RESERVE pre-allocation method is not available for it. For more information about unwritten extent flagging, consult the Man page for mkfs.xfs. Type man mkfs.xfs in a terminal. Test filesystem performance Each standard filesystem comes with its own set of tools to measure performance.
Killing an application If a Creative Finishing application hangs, but you can still interact with the operating system, you can terminate it using either a custom command alias for your application, or the generic Linux kill command in conjunction with the application’s process ID. WARNING These procedures should only be used if the application is hung or otherwise not responding. Killing processes can cause system problems.
Testing Wire Using sw_framestore_dump Use sw_framestore_dump to identify the Wire hosts that are reachable from one workstation. You should do this if you are having any problems with Wire or after you configure Wire for the first time. You must have at least two Wire hosts set up to test Wire connectivity: 1 Run: /usr/discreet/sw/tools/sw_framestore_dump. A list of all the available framestores appears in the terminal.
Ping successful. Buffer size = 9043968 Sending data to tunisia, filesystem id 186 MB/sec: 111.516597 Ping successful. Minimum MB/sec: 111.460127 Maximum MB/sec: 111.516597 Average MB/sec: 111.496590 ■ If an sw_ping from machine 1 to machine 2 is successful and you still cannot access the remote framestore through your Creative Finishing application, check that the remote system has exported its directories so that the local system has read/write access.
3 If error messages appear, verify the permissions in /etc/exports on the server machine. Read and write permission must be given to the hosts. The appropriate line should look similar to the following: /usr/discreet/clip *(rw,sync,no_root_squash Verifying that NFS and Automounting Daemons are Running These daemons are installed and running by default. Use the following procedures to verify that these daemons are running.
As root, open a terminal on your workstation and run /sbin/iba_capture . A GZIP file is generated that includes a number of log files from your system. The help for this command incorrectly indicates that the output is a TAR file, when it is in fact a GZIP file. Viewing Port Statistics for a Mellanox IS5030 Switch The Mellanox IS5030 switch is the recommended switch model for QDR InfiniBand networks.
Verifying that Stone and Wire Processes Are Running There are five processes that must be running for Stone and Wire to work: ■ sw_serverd ■ sw_probed ■ sw_dbd ■ sw_bwmgr ■ ifffsWiretapServer. This process is started by the sw_wiretapd script. To verify that Stone and Wire processes are running: 1 Run: ps -ef | grep sw_.
You can also use the terminal to list the most recent version of the log files. Type the following in a terminal: ls -altr Enabling Verbose Stone and Wire Driver Error Reporting Use the swr_set_debug utility to enable verbose reporting of Stone and Wire driver errors. When you turn on error reporting, Stone and Wire outputs error messages in the following locations: ■ /var/log/messages ■ Console window NOTE You must disable verbose error reporting after you have finished troubleshooting.
2 Depending on the result of the previous command, do one of the following: ■ For clips with frames listed as missing, contact your local Autodesk support representative for help on resolving this issue. ■ For clips with frames listed as remote, perform the following procedure. To recover remote frames: 1 Archive all clip libraries that are reported as containing remote frames. In the previous example, the fourth library (from_caplan) contains remote frames.
3 Reload the Stone and Wire driver: /etc/init.d/stone+wire reload. Your filesystem should now be mounted. Verifying Disk Usage You cannot write to storage partitions that are completely full. To see if the filesystem is full, run /usr/discreet/sw/sw_df. If your filesystem is full or almost full, consider deleting or archiving older material from clip libraries to free disk space.
6 If you continue to get error messages, contact Customer Support. Solving a Partition ID Conflict Each partition must have a different partition ID. If there are multiple partitions using the same ID, you will receive an error message. To solve a Partition ID conflict: 1 Note the ID listed in the error message. 2 Stop Stone and Wire: /etc/init.d/stone+wire stop 3 Open the /usr/discreet/sw/cfg/stone+wire.cfg file in a text editor.
84
Licensing and Starting 7 Node-locked licensing Node-locked licenses are locked to one computer. ■ All customers receive a temporary node-locked license when they purchase their software. ■ Subscription customers receive a temporary node-locked license when they receive their extension software. All customers must request permanent licenses: ■ Subscription customers have the choice of requesting permanent node-locked or network licenses.
3 Select Node-Locked License and click Next. 4 Paste the license codes you received from Autodesk in the next window. Be very careful to paste the license codes exactly as you have received them. Any incorrect or missing characters will prevent your application from recognizing the license. 5 Click Install to install the license code. Your application is now licensed. License codes are unique for each workstation, and are tied to the system hardware.
Workflow for Configuring a License Server 1 Select a license server. You can install a license server on your Creative Finishing workstation or any other machine on your network. To see if you already have a license server running on a machine, open a Terminal, login as root, and type: chkconfig --list | grep lic. For redundant license servers, select three machines. All must be set to the same date and time. 2 Install the license server software (page 87) on all machines that will be servers.
2 Log in to support portal: https://edge.autodesk.com/LicenseAssignment. 3 Follow the links to set up your license server assets and select the software that you want to access using a network license. Your license codes are emailed to you. License the workstation with a local or single remote license server Create license files ■ For a redundant network license server configuration, you must create the license files for the workstation and license server manually.
The license information contains keywords that identify the license server, as well as the license strings for products or features. Keyword Description SERVER Specifies the hostname of the license server from which to obtain the license, followed by its dlhostid. VENDOR Specifies the daemon that is serving the license. USE_SERVER Indicates whether the system should obtain its license from a license server. FEATURE License strings for the software and feature entitlements.
Change the default port used by the license server To avoid conflicts with other applications or license servers in your facility, you may need to change the default port setting used by the license server, or license servers in the case of a redundant configuration. This requires a minor change to the DL_license.dat file on your license server(s), as well as on every Creative Finishing Softwareworkstation.
Start the software You must license Inferno, Flame Premium, Flame, Flint, Smoke Advanced, Smoke and Backdraft Conform, and where applicable, Lustre, before you can start. If you use the pen and tablet while the application is starting, the tablet will fail to initialise. Press Shift+T+Insert to initialise the tablet if it does not function during a work session.
B Prevent the broadcast monitor from blanking when an image viewer or Player is not displayed. The broadcast monitor then displays the screen content that is displayed in the corresponding region. This is hardware dependent and may not work on all hardware configurations. c Use a configuration file other than the default, where is the name of the file. The specified file supersedes the default configuration file.
Index A AMD starting daemon 77 application entering license codes 85 installing 39 licensing 85 starting 91 uninstalling 41 audio Discreet Native Audio 12 hardware components 12 wiring workflow 12 audio converter 12 Audiodevice keyword 39 AutoFS starting daemon 77 B Backburner Manager configuring 50 detecting in Lustre 54 detecting with Backburner Server 54 installing 50 overview 49 Backburner Monitor installing 50 overview 49 Backburner Server detecting Backburner Manager 54 overview 49 starting 54 Backbu
error logs 79 error reporting errors logs 79 verbose 80 BackburnerManagerPriority DVIRamp 39 TabletDriver 39 Video 39 VTR 39 Kill process command 74 F L filesystem disk usage 82 problems 78 filesystems CXFS 43 NFS 43 floating licenses background rendering 53 fonts installing 92 framestore ID mismatch, resolving 82 license background rendering, floating 53 Burn for Lustre 53 license codes editing the license file 85 entering application 85 requesting 85 license server background rendering 53 creating th
sw_framestore_dump testing Wire 75 sw_ping network performance 76 testing Wire 75 swr_set_debug 80 system freezes, what to do 74 O operating system rule Wiretap path translation 62 P path translation database XML syntax 60 ping 75 platforms in this release 1 port statistics, InfiniBand 77, 78 powering on or off, sequence for 33 problems filesystem 78 Wire 74 processes displaying, Stone and Wire 79 starting, Stone and Wire 79 processes, stopping 74 products in this release 1 projects setting up slave rend
host/path rule 60 operating system rule 62 sharing the database 63 testing 63 wiring video I/O and broadcast monitor 12 workflow configuring BrowseD 55 configuring slave rendering 47 licensing 85 setting up background rendering 48 storage configuration 30 96 | Index workflows audio wiring workflow 12 X X server configuring 39 restarting 39 XML syntax path translation database xxdiff, using 39 60
