Page tree


  • Transition Summary

    • Back-up your existing Tractor 1.x job and configuration data.
    • Create a new directory to hold your 2.x configuration overrides.
    • Become familiar with new Engine+Blade installed product layout.
    • Review tractor.config settings, especially the EngineOwner setting.
  • Tractor-2.0 is packaged as a single installer containing all of the various Tractor components: Engine, Blade, Dashboard, Spooler, Nimby, the Tractor Query utilities, as well as the compatible prebuilt subsystems such as the job database server, Python and Tcl interpreters, and supporting modules and frameworks. Some components have slightly different names or are now accessed through wrapper scripts, most of which are now located in the Tractor-2.0/bin directory. Once you have had a chance to browse the new structure, you may need to revise paths or tool names in your own site-developed scripts to make use of the new scheme.

  • The job queue database has been upgraded from a simple system of flat JSON files to a fully integrated PostgreSQL database. This change enables several important features in Tractor 2.0, but may be disruptive to sites that were relying on direct filesystem access to job data for some reason. It is better to rely on the various job access APIs instead so that you are insulated from changes to the underlying data representation -- and that is still true for 2.0 since the representation details will continue to evolve.

  • Given the need for a PostgreSQL server, the Tractor 2.0 installer provides a Tractor-compatible prebuilt PostgreSQL server within the Tractor-2.0 install area. This "private" installation of the database components, relative to the matching Tractor release, allows the tractor-engine to reliably start and stop the PostgreSQL server as it needs. It is also technically possible to configure Tractor to use another PostgreSQL server that may already be available at your site (details in db.config). Note however that there may be some performance, compatibility, and data safety concerns when taking this approach. Please contact RenderMan Customer Support for more information.

  • Configuration file handling: Several subtle changes have been made to the way in which configuration values are loaded from the various Tractor configuration files. Different directories should be used to hold 1.x and 2.x engine configuration files. There is still a "stock" config directory at the top level of the installed Tractor-2.0 directory. You can, and should, copy the files that you wish to modify from there to a directory of your own outside the install area. A copy protects your changes if the product is reinstalled, and they will also be applied to new versions as you install them. Tractor 2.0 differs from 1.x in that you no longer need to copy unchanged files. The engine will now look in your designated "--configdir" location for files (as before), but will now fallback to looking in the stock install location for files not found in the "--configdir" location. Furthermore, for the specific files "tractor.config" and "db.config", your copies can contain only overrides for the specific values that you want to change, you do not need to copy the entire file. This approach allows potentially important settings in new releases to still be found in the stock tractor.config while still applying your desired overrides.

  • Engine command line options: many of the 1.x tractor-engine command line options can now be specified in tractor.config. Some parameters, such as the location of the job data directory must now be specified in tractor.config where other Tractor helper applications can find them.