Date: Fri, 29 Mar 2024 08:51:02 +0000 (UTC) Message-ID: <1527258629.555.1711702262830@ip-10-0-0-233.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_554_1567209583.1711702262805" ------=_Part_554_1567209583.1711702262805 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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 contai= ning all of the various Tractor components: Engine, Blade, Dashboard, Spool= er, Nimby, the Tractor Query utilities, as well as the compatible prebuilt = subsystems such as the job database server, Python and Tcl interpreters, an= d supporting modules and frameworks. Some components have slightly differen= t 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 bro= wse the new structure, you may need to revise paths or tool names in your o= wn site-developed scripts to make use of the new scheme.
The job queue database has been upgraded from a simp= le system of flat JSON files to a fully integrated PostgreSQL database. Thi= s change enables several important features in Tractor 2.0, but may be disr= uptive to sites that were relying on direct filesystem access to job data f= or 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 representati= on -- 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 with= in the Tractor-2.0 install area. This "private" installation of the databas= e 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 se= rver that may already be available at your site (details in db.config). Note however that there may be so= me performance, compatibility, and data safety concerns when taking this ap= proach. Please contact RenderMan Customer Support&n= bsp;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 sh= ould 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 t= o 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 als= o 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 fo= und in the "--configdir" location. Furthermore, for the specific files "tra= ctor.config" and "db.config", your copies can contain only overrides for th= e specific values that you want to change, you do not need to copy the enti= re file. This approach allows potentially important settings in new release= s to still be found in the stock tractor.config while still applying your d= esired overrides.
Engine command line options: many of the 1.x tractor= -engine command line options can now be specified in tractor.config. Some p= arameters, such as the location of the job data directory must now be specified in tractor.config where other Tractor helper applic= ations can find them.