Setup guide

2 In a terminal, as root. Stop Stone and Wire with the command: /etc/init.d/stone+wire stop.
3 Create one or more Managed Media Cache directories:
■ If a mount point for your storage does not exist, create one, for example: mkdir -p /mnt/SAN1. Do
not use the reserved word “stonefs” as the name for your mount point directory. Mount the
filesystem to the newly-created directory. To mount it at boot, update /etc/fstab.
■ Create the Managed Media Cache directory on the mounted filesystem, in a directory named after
the workstation hostname. The Managed Media Cache directory should be named after the partition
name (by default, partition 7, or p7). For example, if the filesystem mount point is /mnt/SAN1, your
workstation hostname is flare1, and the partition name is p7, type: mkdir -p /mnt/SAN1/flare1/p7
■ Set the ownership for the directory to the root user. For example: chown -R root:users
/mnt/SAN1/flare1/p7. Set permissions for the directory to be readable, writable, and searchable by
the owner and its group, and readable and searchable by all. For example: chmod -R 775
/mnt/SAN1/flare1/p7
4 To make your application aware of the standard filesystem volumes, define the Managed Media Cache
of each volume as a partition in the Stone and Wire configuration file, and set its preferences in
/usr/discreet/sw/cfg/stone+wire.cfg. Update the keywords: Name, Path, Shared, and
SymlinkAcrossFilesystems.
5 If this is the first filesystem you are configuring for this workstation:
■ From /usr/discreet/sw/cfg/sw_framestore_map file get the FRAMESTORE value and use it to update
/usr/discreet/sw/cfg/sw_storage.cfg.
6 Restart Stone and Wire by typing: /etc/init.d/stone+wire restart.
7 Ensure the filesystem is mounted: /usr/discreet/sw/sw_df. Any project created in your application
after this point has the new standard filesystem partition as its primary partition. Any pre-existing
projects are unaffected by this setting and remain associated to their respective partitions.
Connecting Remotely to the Storage of a Flame or Inferno Workstation
The Stone Direct storage arrays of Flame and Inferno workstations are tuned for the high performance I/O
needs of a local creative application. Stone Direct storage can also provide a basic level of interactivity for
remote Flare workstations when performing light to medium I/O tasks, such as working with Batch setups
to perform operations like tracking and retouching.
Remote Flare workstations can use any unused bandwidth.
Stone FS and standard filesystems connected to a Flame or Inferno workstation perform differently in shared
workflows. Both will perform adequately for remote Flare activity with light I/O requirements.
The Stone FS filesystem incorporates a bandwidth reservation service that protects the Flame and Inferno
Player and Input/Output clip module from losing bandwidth, but is not capable of providing protection for
general interactivity when the storage is stressed by high-bandwidth remote operations, such as playback,
Wire transfers, or import/export.
It is therefore recommended to use a standard filesystem for the Flame or Inferno workstation to which Flare
remotely connects. The advanced standard filesystem Bandwidth Manager (automatically installed with
Creative Finishing applications) manages I/O requests to your storage, and provides greater protection in
all Flame or Inferno workflows.
Even when the standard filesystem Bandwidth Manager is managing I/O requests, factors such as I/O
operations from third-party applications, filesystem fragmentation, partition fill rate, concurrent
reading/writing, and mixed I/O sizes can still decrease the performance of your storage. Periodic filesystem
maintenance and workflow changes may be required to achieve optimal performance.
70 | Chapter 2 Install and configure a Flare workstation