Rush Render Queue - 103 Features V 103.07b 05/11/16 (C) Copyright 2008, 2016 Seriss Corporation. All rights reserved. (C) Copyright 1995,2000 Greg Ercolano. All rights reserved.

Web Submit Forms Using Python Submit Scripts

The python submit scripts (submit_maya.py, submit_nuke.py, etc) can also be used as cgi-bin scripts to allow submitting jobs via URLs to an Apache webserver.

See details in the rush/examples/python/README-web-submit.html file for info on how to configure.



Black color theme for Irush and Submit forms (103.03)

For all you night owls and color timing folks who like their rooms and interfaces as dark as possible:

Irush using new black color theme. Here's how to enable it.


Submit forms using new black color theme.
Works for both perl and python submits.
Here's how to enable it.

Enhanced Column Headers + Customizable Columns For Irush Reports

The column headers in all the reports have been improved to look a bit nicer and more consistent with other applications.


You can click on the headings to sort by that column as usual; cycles through sorting ascending/descending/no sort.
To resize columns, click on the separators between columns in the heading area to make them wider or smaller.

If you Right Click on columns of Jobs and All Jobs reports, you can add/remove column headers, making it to be easy to create custom Job reports:

(1) First right click on a heading you want to add a field to the right of, then (2) choose 'Add Field' to find the new field heading you want to add..

(3) The new field will now appear in the report. You can add as many fields as you want this way to define custom reports. Later you can use 'Remove Field' to get rid of fields, or 'Default fields' to reset the report to defaults. These field settings are saved in your home directory's "~/.irush-fmt" file, which you can also manually edit to make changes.

New Job Report Default Fields

New fields have been added to the default Jobs and All Jobs reports to help render wranglers and artists better manage jobs.


Right Click Context Menus

New right click menus offer an alternate way to do operations in irush on selected lines in reports.

Jobs report's context menu	Frames report's context menu

Automatic "Frames" report by holding Alt while double-clicking a job

When viewing a Jobs or All Jobs report, double-clicking a job makes it the current job, and if you hold down the Alt key, it will also automatically show the Frames report for that job. (Saves the extra step of having to hit the "Frames" button)

Job Edit Command Input Fields

Makes long job commands easier to read and manage.


IRUSH_JOBS & IRUSH_FRAMES Environment Variables

These environment variables are passed from irush to any custom Hotkey scripts so that they can determine which jobs/frames are selected in either the "Jobs" or "Frames" reports of irush at the time the Hotkey script is invoked.

The scripts can then operate on the selected jobs/frames accordingly.

Column Truncation Indicators

Truncation indicators appear when a column's size is too small to show data, and the data is being truncated. This helps prevent any confusion about whether a field is being cropped.

Rushtop

In Rush 103.05, Rushtop got some attention to improve its interface useability.

Network I/O Added to Rushtop (103.05)

A new bar has been added to rushtop that shows network I/O of each machine in bytes per second in and out of the machine.

Shows in/out network interface traffic relative to peak traffic.

Enable/Disable Rushtop Columns (103.05)

You can enable/disable any of the columns of data using the popup menu's new "View" submenu.

The new 'View' submenu in rushtop.

These can also be changed from the rushtop command line with the new '-view' parameter.

Interface Font Size Adjustment (103.05)

People with large hi-def screens will want this feature; lets you enlarge the interface's fonts to be easier to read on large screens with tiny pixels.

To enlarge/shrink the rushtop font:
For Windows and Linux use: Ctrl + / Ctrl -
For Mac use: Command + / Command -

Improved Rushtop Host selection

If there are columns of information in rushtop you don't want to see, you can turn them off using the popup menu's new "Hosts.." dialog, which lets you pick the hosts you want to see. You can do 'swipe' selections, use ^A to select all, and use Ctrl to toggle items.

The right-click popup menu's new 'Hosts..' option brings up a dialog to let you choose which hosts to monitor.

This feature has actually always been available from the rushtop command line; you can simply specify hostnames or +hostgroups on the rushtop command line to set which machines to view, but now the feature is available from the GUI's popup menu as well.

Rushtop Shows Hostname Lookup Errors

In cases where machines don't have IP lookups, rushtop shows these errors in the bar for that host, making it easy for admins to see hostname lookup problems.

Hostname lookup errors show up within rushtop.

Submit Scripts

Python Submit Scripts with Shotgun Support

There are now separate Python submit scripts that include optional Shotgun Software ® support. These scripts can either be run as standalone apps, or import'ed directly into Maya, Nuke, and other renderers that support Python internally.

There is also a growing Python API modules for Rush so that your own scripts can import these modules to load job/frame reports and manipulate jobs.

Python Submit Scripts
submit_maya.py with the Shotgun option enabled	submit_nuke.py with the Shotgun option enabled

Added submit-xsi, submit-redline Submit Script

These two scripts had been floating around for years via email support, but was never added to the mainstream release until now.

The submit-xsi script supports all versions of Xsi to date, and the submit-redline script supports the Red camera's R3D file conversions.

Added Submit Scripts
submit-xsi.pl	submit-redline.pl converts r3d files

"Task" vs. "Advanced" Shotgun Workflows

Your Shotgun administrator controls whether Rush (and shotgun) uses Shotgun's "Task" workflow, or the more generalized "Advanced" workflow via the shotgun_io.conf file (typically located in the same directory tree as the shotgun_io.py script).

Here's a comparison of the two different workflow modes in the Rush submit forms:


Shotgun's simpler 'task' workflow, compared to the more generalized 'advanced' workflow

Rush

Large 'All Jobs' Reports

There was a network packet size limitation that affected large 'rush -laj' reports caused by some network switch/OS combinations which has been fixed by implementing fragmentation size control via the rush.conf file, allowing for much larger reports.

WaitForDependency

Added this field to the 'rush -ljf' report, allowing symmetry for resolving the WaitFor dependency tree both forward and reverse. (PAWEL/FUELVFX)

Easy Multi-job Priority Increase/Decrease

Both irush and 'rush -cp' support relative priority adjustment, so that one can increase/decrease priorities without flattening priority staircasing. Examples:

	    rush -cp '*' @+5           -- increase priority by +5
	    rush -cp '*' @-5           -- decrease priority by -5
	    rush -cp +any=50@100 @+10  -- increase priority from 100 to 110
	

Irush also makes use of this feature in the 'Jobs' and 'All Jobs' report
so that one can easily raise/lower the priority of multiple selected jobs at once:

Processor Affinity Support for Linux

Rush has already supported affinity for several years for Windows, and now linux support has been added.

So now both windows and linux can have 'affinity=x' in the hosts file. (Still no affinity support for OSX: Apple's operating system does not support it)

Cpu Specifications Augmented

New cpu specifications allow one to index hosts from hostgroups using parenthesis. e.g. '+maya(1-4)=5@100' picks hosts 1 thru 4 from the +maya host group. (ROMEY/ZOIC)

List Job Counters (rush -ljc) Enables GUI Applications To Easily Detect Job Changes

Every rush job now maintains 'change counters' which are incremented whenever an aspect of the job has changed.

GUI applications can view these counters for all jobs quickly with a single low load/low bandwidth 'rush -ljc' command to see which jobs have changed, preventing the need to poll ALL data about jobs.

This feature can be used by 'watcher scripts' as well, to easily see which jobs have changed for custom load balancing, so that it can know if that job's info needs to be reloaded to update the watcher's cache.

Loopback Enabling

In certain situations it's useful to run Rush on a standalone system that is not attached to a network, ie. only has a loopback IP address assigned to it. In such cases, the new allowloopback 1 command can be used to allow rush to not complain about loopback addresses. [COLORFRONT]

Bootcheck and Mountcheck Scripts

The sysadmin can configure a bootcheck script for the daemon to run during startup to check if the machine is suitable for rendering during boot. This can verify the machine's networking is fully 'up', DNS is operative, and mounts are in place. The command can simply wait for resources to appear, and when it returns, rushd will being starting renders. (BSGVFX)

Also, a mountcheck script to run BEFORE rush runs a render, to check if the machine is suitable for rendering. This can check server mounts so it can either fix the problem before starting the render or simply take the machine offline and tell the frame to requeue elsewhere. (LOOKFX, et al)

The scripts can be written in any scripting language (Perl, Python, Bash, ..), with perl examples are included, and the scripts disabled by default. (LOOKFX, etc.)

Centralized Cpu Accounting Logs

The sysadmin can configure the new cpuacct.dbasedir rush.conf command to tell Rush the path to a file server where all the Rush daemons can append cpu accounting logs. e.g.

	   cpuacct.dbasedir "/server/somewhere" 0755 0644
	

..which will cause the rush cpu.acct data to be appended to the file server at regular intervals using a date stamped pathname of the form:

	       /server/somewhere/[YYYY]/[MM]/[DD]/[HOSTNAME]-cpu.acct
				 ---------------------------
				 |
				 Automatically generated dirs
				 and filename
	

This feature can be used by custom scripts, and will also be used by future web based scripts included with Rush that can easily provide network wide utilization report graphs in realtime, e.g.


New Submit Commands Added

The 'rush -submit': Added the following submit commands:

	 commandflags           <flags> -- adjusts attributes of job's command
	 jobstartcommandflags   <flags> -- adjusts attributes of job's jobstartcommand
	 jobrestartcommandflags <flags> -- adjusts attributes of job's jobrestartcommand
	 jobdonecommandflags    <flags> -- adjusts attributes of job's jobdonecommand
	 jobdumpcommandflags    <flags> -- adjusts attributes of job's jobdumpcommand
      

..and the following 'rush' command line flags to control those same flags while jobs are running:

	 rush -commandflags            <flags>
	 rush -jobstartcommandflags    <flags>
	 rush -jobrestartcommandflags  <flags>
	 rush -jobdonecommandflags     <flags>
	 rush -jobdumpcommandflags     <flags>
      

..and these are the list of 'flags' options for all the above:

	 quote      -- Handle quoting
	 expandvars -- Expand environment variables of the form ${VARNAME} at runtime
	 escape     -- Handle escape character (\)
	 useshell   -- Use a native shell to run the command (unix:use bash, windows: use DOS)
	 nolog      -- (jobdonecommand only) disables creating jobdonecommand.log
	 done       -- (jobdonecommand only) runs command only if all frames are "Done"
	 fail       -- (jobdonecommand only) runs command only if any frames are "Fail" and rest are "Done"
	 donefail   -- (jobdonecommand only) runs command only if all frames are "Done" or "Fail"
	 always     -- (jobdonecommand only) always runs command when job is done (default)
	 off        -- turns off all the above flags
      

New Customizable Reports

With the new "-fmt" flag, 'rush -lj' and 'rush -laj' reports can be easily customized from the command line to include any of the job data visible in the -ljf and -lfi reports. Example:


See 'rush -lj -fmt help' for the large list of all the possible field names.

The field names for reports can be specified in several ways, either with a list of field names passed to the new '-fmt' flag directly, or via an environment variable, or via defaults configured in the rush.conf file's new commands:


rush.lj.fmt (for -lj reports),
rush.laj.fmt (for -laj reports),
rush.lj_x.fmt (for the irush "Jobs" and "All Jobs" reports)

(More Features TBD)

Older Features Pages

102.42a9c Features
102.42 Features
102.41 Features
102.41f Features
102.40 Features
102.31m Features