Search
Page 26 of 107. Showing 1,065 results (0.011 seconds)
Qube Components
There are three main components to Qube: The Worker, which is a program that runs on every computer (also called a "host") on which you want to execute your jobs. The Supervisor, which runs on a dedicated machine, and keeps track of all everything. It dec…Job Layout Overview
Let's get oriented by looking at the labeled section of the interface: worddavb8d4aea0a81abb37f71889946287f984.png Main Menu The standard menu. Filter Bar Use the Filter Bar to filter down the Job Layout to include only those jobs you are interested in. T…Running Processes Layout Overview
Clicking on the "Running Layout" switches the interface to a process-centric view of all job processes running on the RenderFarm. It will also pull information from the Worker, job, and frame to give a consolidated bank of useful information for monitorin…OSX Quickstart Notes
Execution Environment
Job Environment Qube by default will execute the job within the Worker's environment. The Worker can also be instructed to use the current environment to execute the job as well. Example % qbsub --flags export_environment sleep 10 Drive Mounting (Windows…Linux Quickstart Notes
Below is a reference built around centos as the host operating system and presumes a general knowledge of Linux. Small substitution could be applied for other Linux distributions.…Job Archive File
The job archive is a file format used by Qube's tools both to store template information and to record a job's initial state. The Supervisor automatically creates such an archive file when the job is submitted. However users are also allowed to create the…Qube WranglerView Interface
Below is an introduction to Qube WranglerView menu items and panes…Basic Job Submission
See also there are a range of example files you can use for testing the farm see below Testing Migrated to Confluence 5.3…Job Requirements
reserving all job slots) job.kind = 'test' (or any other value, your choice...) not(job.kind in host.duty.kind) (see How to restrict a host to only one instance of a given kind of job…